Moonshine

In addition, `ll` tells me that shadow_puppet is present on all servers (the rest of the error

Good news, cap deploy:setup went fine for deploying a new server today . However, on cap deploy with

I upgraded it last night. It's working smoothly. For my site, the page load time in Passenger 4

I have custom fonts in app/assets/fonts directory in my Rails 4.2.5 app. I see configuration[:apache]

Yup. I kept the old one. No idea if I should let it upgrade. The diff shown was root=UUID=xxxx

Looks like I solved this. Since I last created Ubuntu images on Rackspace, they've changed the

Getting rake --version -bash: /usr/local/bin/rake: /usr/bin/ruby2.1: bad interpreter: No such file or

Hey Bryan, That did the trick! Thanks a lot for your help. Jose On Saturday, 7 February 2015 13:30:59

When can we expect Moonshine support for Ruby 2.2? I would be glad to help if there is some

I'm also still unclear on how to resolve the timing issues when deploying to multiple nodes, and

The nodejs plugin listed here https://github.com/railsmachine/moonshine/wiki/Moonshine-plugins does

I'm in the middle of an upgrade. Looks like a few things have changed. One good thing is that

Hey Kevin, Please note that the Configuration page https://github.com/railsmachine/moonshine/wiki/

It worked. I have also updated the wiki : https://github.com/railsmachine/moonshine/wiki/Adding-an-

The archive post on Heartbleed vulnerability answers my questions. I was confused by the output of :

Check out the dotenv and dotenv-deployment gems. The other option is to have moonshine manage a file

I know that I have to add the following code for Rails 4 : rakefile("resque_tasks.rake") do

You can, but Rails isn't going to be initialized during a shadow puppet run, so you need to find

Yep, that'll do it. On Jul 15, 2014, at 12:58 AM, bparanj <bpa...@gmail.com> wrote: So, I

You were right. I used the following syntax checker stolen from stackoverflow: cat yaml_checker.rb

Moonshine doesn't support Capistrano 3. Cap 3 is a complete rewrite and it's going to take us

That's fine, you just need to make sure you have the latest moonshine. On May 27, 2014, at 9:36

It helped. I documented my steps to fix this problem: http://bparanj.blogspot.com/2014/05/migrating-

I haven't put it into production yet, but I've tested it with Vagrant and Moonshine seems to

Hi Judy, Based on the app name and the server name, I think you actually inherited this project from

You can just do `cap aptget:upgrade` to apply all of the updates. If you only want to apply security

It looks like configuration[:deploy_to] isn't set. You should have something in config/moonshine.

Thanks. I was going nuts wondering why it wasn't installing, but it was. Cheers! Jamie On Apr 8,

Here's my (working) solution: Manifest code: configure :mongodb => build_mongodb_configuration

Thanks for the follow-up, Jamie! On Mar 6, 2014, at 12:40 PM, Jamie Orchard-Hays <jamieorc@gmail.