-
-
Notifications
You must be signed in to change notification settings - Fork 115
Setup CD deploys of this app #67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@Gaurav0 if you could replace https://github.com/ember-learn/ember-api-docs/blob/master/.travis.yml#L43 with a new app that you own and update the API key in the travis docs, then we'll have successful deploys on merge to the master and production branches.
|
I've added my keys temporarily, which should get replaced with an API key of an official account that has access to both staging & production app. It can be done by running The current config can deploy to a staging environment on merges to master and to production on merges to production branch. After deployment it restarts the app and flushes redis. |
@sivakumar-kailasam we now also want to change the deployment of this app to S3, similar to what we do with https://github.com/ember-learn/builds |
@acorncom mentioned that he has the api keys and such, if you don't have them already |
I would hold off of an S3 deploy of the app for now, as doing that would be dooming fastboot as I understand. Which would be fine if there is a good SEO alternative (open to suggestions). We still need to figure out what the long term hosting of the app will be. |
Current situation is we are going to deploy the app to heroku. Data to be copied to S3 (worked on as part of ember-jsonapi-doc ember-learn/ember-jsonapi-docs#17 ) |
The heroku section of the travis file seems to be broken. https://travis-ci.org/ember-learn/ember-api-docs/builds/211546164 |
This is now operational. Merging to master & production deploy to staging & production heroku instances. |
No description provided.
The text was updated successfully, but these errors were encountered: