-
Notifications
You must be signed in to change notification settings - Fork 39
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
Deploy to Heroku broken #8
Comments
I tried to change the MM v to 3.8.2, but still no go. |
I ran into the same issue today, too. Following along in case a solution appears |
same problem faced |
@PandaWhoCodes @jamesfacts @kristofer Looks like the link on chrisdecairos' blog is set on using an older branch and i'm guessing that branch isn't up-to-snuff with the current heroku deploy. https://dashboard.heroku.com/new?template=https%3A%2F%2Fgithub.com%2Fmozilla%2Fmattermost-heroku |
thanks |
You can also click the link on this repo with the correct branch checked out However, even though using either the latest official version or master builds and deploys on Heroku, trying to view the app gives me a 502 Bad Gateway error. Anyone know how to fix this? Is there a setup required in Heroku? |
ping |
with the commit to "add nginx-heroku-16"
I get this when I try to run the deploy to heroku page at https://dashboard.heroku.com/new?button-url=https%3A%2F%2Fchrisdecairos.ca%2Fdeploying-mattermost-to-heroku%2F&template=https%3A%2F%2Fgithub.com%2Fmozilla%2Fmattermost-heroku%2Ftree%2F1.0.3
anything I can do to fix?
The text was updated successfully, but these errors were encountered: