[chef] Re: Re: Rails Recommendations

[Angus Buchanan < >]

Hi Vladimir,

On Mon, Sep 1, 2014 at 11:16 AM, Vladimir Skubriev < " target="_blank"> > wrote:

You can use them. But you need to remember that you will spend a decent amount of time with testing and learning this cookbooks. Other case - use chef and write you own recipe based on default HOW_TO to setup rails application and what you need. Everywhere when you use chef cookbook's - add time to their study and testing. Automating needed in those places where it is absolutely necessary and can save a time.

Most of the how-to docs I see are very much focussed on a development setup, rather than something in production.  But it seems pretty straightforward.  One question would be whether to have a deploy user if using capistrano, or just to deploy as the user created for running the app.  Any suggestions?

 

That's good approach, but you should learn packaging system policy's documents. This is not easy way. But it's is you right.

I think with Omnibus I can just shove everything in /opt, and update the vhost... this also solves Ruby problems.  I'm quite convinced this is a good idea, but I couldn't find any article or example of packaging Ruby, and some Gems, and the app itself.  I guess I could try to make Jenkins build the package too.... this seems quite a nice approach.  What do you think? 

3) What's the recommended way to get Ruby on the system?  I am not very keen on the idea of using rvm on servers, but system packages tend to lag too.  What is recommended?

 

You don't have a another way except using rvm or rbenv. Better to use rvm and install them for the user. Why better - because rvm more elegant way to use ruby on the system. There are a good cookbook chef-rvm to do it.

Well... in Omnibus the Ruby is built for me... problem solved!

Passenger is a default app server (Should be enough).

See passenger cookbook if you wish to install them with chef. But in simple approach I recommend to install them manually with chef bash scripts. You can see a redmine cookbook for example.

OK cool.  What about unicorn and puma?  Why are these so popular if passenger is so simple?  I prefer the simple approach, I think.

 

5) What about database stuff?  I see there's a database cookbook with some powerful tools, and a mysql cookbook, but should I try to seed the database with Chef or do that manually?

You can use database cookbook, but you pay for that you time. In a simple production  case just create a db manually and connect to it from you application. If you need to create a test environment then use database cookbook (recipe) for complete deploy test environment in vagrant machine with kitchen.ci for example. I think this is a very simple use case.

I don't really understand this... but never mind.

-aob