We're using Heroku for hosting the system, from test to production environments.
You can develop and test locally as described in the CONTRIBUTING guide, but if you need to deploy changes to a test environment, look later in this document to get access.
Note: This requires that you have been added to the https://dashboard.heroku.com/teams/codingpirates team. Reach out in #medlemssystem_dev Slack channel if you need access. Typically it's only reviewers who needs this access though.
-
Open the Heroku medlemssystem pipeline
-
Click the
Create review app
for the pull request you want to test -
In the screenshot above, PR
#699
has already been deployed. Click theOpen app
button to open the running site, in this case https://medlemssystem-pr-699.herokuapp.com/ (will be a unique url for each pull request) -
In order to get data populated, we need to populate the database, so open
More -> Run console
-
Run
./manage.py get_live_data
to get the public live data populated -
Run
./manage.py shell
to create members in the system. When the shell prompt is ready, type infrom members.tests.factories import MemberFactory MemberFactory.create_batch(20)
-
If you need to use the admin interface, run
./manage.py createsuperuser
and follow instructions for creating an admin account. Now you can log into https://medlemssystem-pr-699.herokuapp.com/admin/
Staging environment allows us to verify changes on production data before going live, and is available at https://medlemssystem-staging.herokuapp.com
All merges to master
branch automatically gets deployed to the staging environment.
This is the site available at https://members.codingpirates.dk and is deployed by clicking the Promote to production
button on the Medlemssystem pipeline in Heroku