Skip to content
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

Closed
jbrooksuk opened this issue Dec 20, 2014 · 9 comments
Closed

Heroku deployment is no longer working #77

jbrooksuk opened this issue Dec 20, 2014 · 9 comments
Labels
Bug Bugs with Cachet Help Wanted Issues that need more help
Milestone

Comments

@jbrooksuk
Copy link
Member

The redirection to setup results with:

Whoops, looks like something went wrong.

Not particularly useful.

Interestingly setup works locally, so it must be something specific to the Heroku environment.

@jbrooksuk jbrooksuk added Bug Bugs with Cachet Help Wanted Issues that need more help labels Dec 20, 2014
@jbrooksuk
Copy link
Member Author

After removing BUILDPACK_URL from the env vars, this now happens:

screenshot 2014-12-20 18 08 35

@demlasjr
Copy link
Contributor

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
remote: {"error":{"type":"ErrorException","message":"Undefined index: DB_DRIVER","file":"/tmp/build_34471ae955189f1be529f5f6205c9079/app/config/database.php","line":29}}{"error":{"type":"ErrorException","message":"Undefined index: DB_DRIVER","file":"/tmp/build_34471ae955189f1be529f5f6205c9079/app/config/database.php","line":29}}-----> Preparing runtime environment...
remote: -----> Discovering process types

It seems to be a db connection problem

@jbrooksuk
Copy link
Member Author

Oooh. Ok, that may be something @Ehesp is interested in? If not I can take a look.

@jbrooksuk
Copy link
Member Author

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?

@GrahamCampbell
Copy link
Contributor

@jbrooksuk Yeh. use the --env flag.

@jbrooksuk
Copy link
Member Author

Well I've told it to migrate as the heroku environment, but that's not fixed it.

@GrahamCampbell any other ideas? The postdeploy script is this:

"postdeploy": "php artisan migrate --env=heroku; php artisan key:generate"

@jbrooksuk
Copy link
Member Author

We can't actually run php artisan optimize with the env at that point because it's set within composer.json and could be running on any environment. What we could do is add those scripts to app.json and just ignore the errors it'll produce?

@demlasjr
Copy link
Contributor

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

@jbrooksuk
Copy link
Member Author

Heroku deployment still isn't 100%. http://cachet-dev.herokuapp.com/

@GrahamCampbell GrahamCampbell modified the milestone: V0.1.0 Alpha Jul 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Bugs with Cachet Help Wanted Issues that need more help
Projects
None yet
Development

No branches or pull requests

3 participants