Closed anamariamv closed 7 years ago
Also let's map this to a subdomain and use the subdomain in all configs related to that test.9c.io
or whatever makes sense in case we want to easily port users to other hostings beside Heroku down the road if we have to.
Fork log to provision stage environment
raulraja@raulraja-MacBookPro ~ heroku fork --from nine-cards --to nine-cards-stage
Forking nine-cards... done. Forked to nine-cards-stage
Setting buildpacks... done
Adding newrelic:wayne to nine-cards-stage as NEW_RELIC... done
Adding adminium:petproject to nine-cards-stage as ADMINIUM... done
Adding loaderio:basic to nine-cards-stage as LOADERIO... done
Adding heroku-postgresql:hobby-basic to nine-cards-stage as DATABASE... done
Attaching HEROKU_POSTGRESQL_PUCE from nine-cards-stage to nine-cards-stage as HEROKU_POSTGRESQL_PUCE... done
Transferring nine-cards:DATABASE to nine-cards-stage:DATABASE...
Progress: done
Adding heroku-postgresql:hobby-dev to nine-cards-stage as HEROKU_POSTGRESQL_MAUVE... done
Transferring nine-cards:HEROKU_POSTGRESQL_MAUVE to nine-cards-stage:HEROKU_POSTGRESQL_MAUVE...
Progress: done
Adding heroku-redis:premium-0 to nine-cards-stage as REDIS... done
Adding logentries:le_tryit to nine-cards-stage as LOGENTRIES... done
Copying config vars:
ANALYTICS_SERVICE_ACCOUNT_CLIENTEMAIL
ANALYTICS_SERVICE_ACCOUNT_CLIENTID
ANALYTICS_SERVICE_ACCOUNT_PRIVATEKEY
ANALYTICS_SERVICE_ACCOUNT_PRIVATEKEYID
ANALYTICS_SERVICE_ACCOUNT_TOKENURI
DB_DEFAULT_DRIVER
DB_DEFAULT_PASSWORD
DB_DEFAULT_URL
DB_DEFAULT_USER
DB_HIKARI_POOL_SIZE
HOST
LOADERIO_VERIFICATION_TOKEN
NCB_GOOGLE_PLAY_HOST
NCB_GOOGLE_PLAY_PORT
NCB_GOOGLE_PLAY_PROTOCOL
NINECARDS_FIREBASE_AUTH_KEY
NINECARDS_WEBPAGE
RANKINGS_ACTOR_INTERVAL
RANKINGS_COUNTRIES_PER_REQUEST
RANKINGS_MAX_APPS_PER_CATEGORY
RANKINGS_RANKING_PERIOD
REDIS_HOST
REDIS_PORT
REDIS_SECRET
REDIS_URL
RESOLVE_ACTOR_BATCHSIZE
RESOLVE_ACTOR_INTERVAL
... done
Deploying f452805 to nine-cards-stage... done
Fork complete. View it at https://nine-cards-stage.herokuapp.com/
Here is the status about this ticket
Heroku provides a feature, called pipelines, that allow connecting several Heroku apps, related to a same code-base (the .git
repository), that may represent testing, stage, and production phases for a given version. We have created one such pipeline for the backend, with a stage environment called nine-cards-stage
, and now every push to the master
branch in the backend repo is automatically deployed in this stage. We have added test.9c.io
as a custom domain for this stage app.
As pending work, we have to add in the pipeline some review apps, in which we may deploy automatically any Pull Request opened against the master
branch.
Description
We need to generate a new Heroku backend for testing.
Name: https://nine-cards-testing.herokuapp.com
We should change the automatic deploy in master to this new backend instead of production backend. From now, we are going to deploy the production backend manually.