Skip to content
This repository has been archived by the owner on Oct 13, 2021. It is now read-only.

Document deployment to Heroku #347

Open
paulcsmith opened this issue Jun 17, 2016 · 3 comments
Open

Document deployment to Heroku #347

paulcsmith opened this issue Jun 17, 2016 · 3 comments
Labels
documentation Issues/PRs related to documentation

Comments

@paulcsmith
Copy link
Contributor

paulcsmith commented Jun 17, 2016

What ENV vars are necessary, how to get Google setup, Mandrill, what mix tasks to run etc.

@paulcsmith paulcsmith added this to the Open Source milestone Jun 17, 2016
@tjmw tjmw self-assigned this Jul 29, 2016
@tjmw
Copy link
Contributor

tjmw commented Jul 29, 2016

I can take a look at this - I had to go through most of these questions when setting up review apps #293. I'll add instructions to DEPLOYMENT.md at the root of the repo.

@tjmw
Copy link
Contributor

tjmw commented Jul 29, 2016

Another idea - how about providing a "Deploy to Heroku" button as described here. We already have the app.json manifest for review app configuration. There's one tb specific piece in there (the redirector config) but hopefully we can work around that.

@paulcsmith paulcsmith assigned paulcsmith and unassigned tjmw Sep 2, 2016
@paulcsmith
Copy link
Contributor Author

@tjmw Great idea! I'm working on this today. It looks like we can provide default ENV vars in the deploy button. I'll try some stuff out and see if I can make it work for the button and our review apps

@WilHall WilHall added the documentation Issues/PRs related to documentation label Aug 23, 2019
@WilHall WilHall removed this from the Open Source milestone Aug 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Issues/PRs related to documentation
Projects
None yet
Development

No branches or pull requests

3 participants