-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Heroku deployment is no longer working #77
Comments
Hello, The bug seems to be related to the database connection. I added back BUILDPACK_URL, otherwise there is no way to install to heroku. After the instalation, I tried to edit some files and when I pushed the files I've seen: remote: Generating optimized autoload files It seems to be a db connection problem |
Oooh. Ok, that may be something @Ehesp is interested in? If not I can take a look. |
I think I know what this is about. Everything runs in production, but at that point (on Heroku) there are no constants. @GrahamCampbell is it possible to run the Generating optimized autoload files as a different environment? |
@jbrooksuk Yeh. use the |
Well I've told it to migrate as the @GrahamCampbell any other ideas? The "postdeploy": "php artisan migrate --env=heroku; php artisan key:generate" |
We can't actually run |
Just about time...I fixed it, not sure how it worked before since the DB connection code and the $_ENV variables were pretty messed up. I sent the fix to approval #84 |
Heroku deployment still isn't 100%. http://cachet-dev.herokuapp.com/ |
The redirection to setup results with:
Not particularly useful.
Interestingly setup works locally, so it must be something specific to the Heroku environment.
The text was updated successfully, but these errors were encountered: