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

A few updates that might be worth considering? #30

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

gordonbisnor
Copy link

Ben - I want to thank you for the awesome RailsConf talk – I was at RailsConf but missed it, then later stumbled upon it in Confreaks and it exactly addressed recent pain I've had with questions of Heroku (cost) vs WebFaction (meh) vs Linode (setup) etc. Wanted a better way of quickly setting up stable Linodes for clients without using apt and Googling my way through it each time. Checked out your tutorials, template repos, and bought the book. Super helpful.

I had to make a few changes to get this working on my machine thought they might be worth considering...

  • Had an issue with bundle command not being found, I added to Capfile
  • Had to update capistrano and capistrano-rails gems, some conflict there
  • Had to update rbenv ruby to 2.1.2 as per your rails server template
  • Had to add secrets.yml - This was causing site to load only HTML, unicorn.log debugging led to secrets file

From the blog post tutorials I had a few other little stumbling blocks:

  • ssh-copy-id did not work for me, I ended up using ssh-copy-id -i myKeyLocation
  • Had to chown secrets.yml and database.yml to deploy user to avoid permission issues

Other than that this worked great. Hoping I will now be able to refer to the book if I need to customize the chef install for various clients, etc.

Thanks for the great work.

Signed-off-by: Gordon B. Isnor <[email protected]>
- TalkingQuickly/rails-server-template uses rbenv 2.1.2, but capistrano-3-rails-template is specifying 2.1.1  - discrepancy was an issue;
- lack of secrets.yml caused an issue
@gordonbisnor
Copy link
Author

Working through the book, I noticed that the intention is that you would log in through deploy user, and hence the chown not necessary for secrets.yml and database.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant