Please be aware that repo-apocalyse is considered deprecated, as the bulk of its use case is covered by Github's archiving functionality.
A time to be born, and a time to die
Archive old Github repositories to S3.
repo-apocalypse is built using API Gateway
and Lambda, but can be run locally as a standard
web-app. From the SBT prompt, run ~local/re-start
and the app will be started
attached to port 8080 and will be recompiled and restarted on each save using
sbt-revolver.
It is configured via a number of environment variables which will need to be set to run successfully.
- Download the .zip from S3 and unzip locally. This gives you the 'bare' repo.
- Create a new repo in github. Important - if there's any possiblity the repo contains secrets, make it private. You can always switch to public later on.
- From the directory that you unzipped the bare repo to, check that the remote is set up correctly with:
my-app$ git remote -v
origin git@github.com:guardian/my-app.git (fetch)
origin git@github.com:guardian/my-app.git (push)
- If the origin urls above match that of your new repo, skip to step 6.
- If the origin urls are not correct then set it to the new github repo with:
git remote set-url origin git@github.com:[org]/[app].git
. - Run
git push origin master
, and you should now see the code in github. - Use
git clone
as usual, from wherever you normally put projects locally.