Tag Info

Hot answers tagged

3

I just became aware of this question, so I thought I'd chime in. I'm an engineer with Chef who has looked into this issue. The accepted answer on this is the correct way you can get around this issue. Note that following the accepted answer will also allow you to reconfigures and keep the setting the same, since that is an issue in another one of the ...


3

Capistrano is setup to use the production environment, but whatever command/script/etc you are using to actually start the Rails app on the box is likely in development mode. export RAILS_ENV=production bin/rails s


1

The issue has been resolved. Turns out nginx was not properly restarting, so the changes to the nginx config file were not being pulled in. Running "sudo stop nginx", killing all the lingering nginx processes, and then restarting nginx fixed the issue.


1

you do not need to use sudo, it should be enough to be in rvm group, just make sure you are in it with id. as for the bundle command, I assume you do not rvm use 2.0.0-p481 before running the bundle, so instead of the bin/bundle you should be running wrapper which takes care of loading proper ruby environment for you: ...


1

Your Apache configuration is broken. Specifically you have a file /etc/apache2/pf.conf which is trying to use directives provided by Phusion Passenger, which you haven't yet installed! Move this file somewhere else temporarily, then run the installation. Once the installation is complete, you can move it back if necessary.


1

Instead of 'copytruncate', these lines worked for me in the logrotate file for my rails app: postrotate touch /your-rails-directory/tmp/restart.txt endscript


1

server { listen x.x.x.x:80; server_name domain.tld; server_name www.domian.tld; server_name ipv4.domain.tld; rewrite ^ https://$server_name$request_uri? permanent; } This works better i think. x.x.x.x refers to your server's IP. If you are working with Plesk 12, you can do that by changing the "nginx.conf" file in the directory ...


1

It absolutely is, I'm deploying this way. I wrote an article about git hooks some time ago. It is about automatically testing your codebase before commiting anything into your SCM. But you can easily rewrite it to run your Capistrano tasks (or custom deployment script), for example when you commit to or merge into your master branch. Maybe it helps you as ...



Only top voted, non community-wiki answers of a minimum length are eligible