I've settled on this workflow for Linux host testing. It treats the backend-examplar-2018
as a template, which simplified the git
manipulations.
- Log into GitHub
- Press the
+
button at the upper left and select "Import repository". - Import from this repository with a new name.
- Clone the repository you created above and
cd
into it. - Copy your database backup into
Backups
. If the backup contains database ownership, you'll need to setDEVELOPMENT_DATABASE_OWNER
in.env
to the database owner. - Copy
env.sample
to.env
and edit.env
:- Change PROJECT_NAME
- Change DEVELOPMENT_POSTGRES_NAME
- Change DEVELOPMENT_DATABASE_OWNER
- Change STAGING_POSTGRES_NAME
- Change the passwords and secret keys
- Type
bin/create-api-project.sh
. This will build a database image with your backup restored, and an API image. The project scaffolding from the API image will be stored in the repository. - When the run completes, examine
db_container.log
to verify that the restore worked. - Check your remote -
git remote -v
. Make sure you'll be pushing to the new repository, not the template! git add .; git commit; git push
.