-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Heroku deployment guide lacks instructions for configuring a database #7814
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
I would also like to see instructions for forcing SSL. I used this StackOverflow answer to achieve that. |
Would mentioning doctrine commands in http://symfony.com/doc/current/deployment/heroku.html#custom-compile-steps be enough? |
I don't think so. As described in the blog post I linked to, there's a lot more to it than doctrine commands. But I may be misunderstanding what you mean by "mentioning doctrine commands". Why, exactly, do you think that would be enough? |
I suggest that could be enough (I'm not a Heroku user), because the hook I linked could be where I don't get why a db clearer add-on as mentioned in the blog article you linked is needed in the first place (when creating a project). |
MySQL isn't included as a core offering in Heroku, so you need an add-on in order to use it.
Unfortunately, I don't think that's enough. For example, you need to get the database credentials from the environment variable |
We must close this as "won't fix" because as part of our efforts to simplify things, in #8721 we've removed all deployment articles. |
I recently followed the instructions on Deploying to Heroku Cloud to deploy a MySQL-driven app to Heroku.
Once deployed, the app didn't work as expected because I didn't configure a database. I wrongly assumed that this was done automatically because the instructions didn't mention anything about a database.
I managed to make it work by following this guide.
To improve the developer experience, I think the deployment instructions should contain an optional section on configuring a database.
As a plan B, they should at least mention that they don't cover database configuration.
Please let me know if you'd like such an expansion of the article covering Heroku deployment. If you do, I can make a pull request.
The text was updated successfully, but these errors were encountered: