bobrock

I'm thinking about how sites have to be restarted after a little time. It takes a little while for them to spin back up on Tommy. Is that true of Morty, as well?

Sorry about that. I didn't realize the app had to be there first. It is there, now.

From the Ruby control panel I can run Rake tasks, one of which is `assets:precompile`! If only I could run that after I Git pull and before I Deploy! Is there a way?

I see. The Rails Way is to run a redeployment script on the server. In this case, I'll have to run that script locally and then commit, push, and pull the result. That can still work.

Thanks, Krydos! That was exactly the clue I needed. It turned out that my site was missing the `master.key` file, which, of course, was not uploaded as part of my GitHub repo because it's not there for security. Once I manually uploaded that file the site appears to be working now in production mode.

I have a Rails app running at https://bobrock.heliohost.us/home that does just fine in development mode. But when I switch to production mode the site will no longer load. Of course, in production mode, I can't see whatever error is causing the problem. On my local machine, I can switch between development and production without any problems, but I had to add config.hosts << "localhost" to the `production.rb` local environment file to make it work. I added config.hosts << "bobrock.heliohost.us" to the `production.rb` remote environment file, but that didn't clear the error. What else should I try to get things running in production mode?

Thanks!

Would laravel.bobrock.heliohost.us work? If so, then that.

I have a Rails app running now on Tommy. Is it possible to run a Laravel app on my account as well without the two interfering? Or can I deactivate Ruby without losing that app and then install Laravel?

So it's just more self-induced problems. I was under the impression that it was Passenger that needed to be in development mode, not my Ruby app. With that error message, I was able to get things running again. Hopefully I will not screw it up again! Thanks for the help.

This is painful to debug without knowing how to view the Passenger log file. Are node.js apps likely to be easier to deploy than Ruby on Rails apps?

Well, it's not fixed anymore. I deployed a few changes, re-started Rails, the Passenger error is back, and I can't see the log file in either 'production' or 'development' mode. Error ID: 3a194af7 Details: Web application could not be started by the Phusion Passenger(R) application server. Please read the Passenger log file (search for the Error ID) to find the details of the error. You can also get a detailed report to appear directly on this page, but for security reasons it is only provided if Phusion Passenger(R) is run with environment set to development and/or with the friendly error pages option set to on. For more information about configuring environment and friendly error pages, see: Nginx integration mode Apache integration mode Standalone mode

Hmmm. Now, whether in 'production' or 'development', after an app restart, no Passenger errors are thrown! It's confusing but fixed. Thanks, again!

I switched Ruby to 'development' but I still get only the error number, not the Passenger log file. Is there something else I've missed?

Thanks! And I'm sorry, again, for wasting your time with such a rookie mistake. It's working now. Onward!

Oops! I'm sorry. I'll try it again, here, on the forum. I almost have it working. After waiting a bit more than 2 hours I'm getting this error: This seems odd because that config.hosts is already in the environment.rb file: Maybe I have something else messed up?