disabling moonshine temporarily

[Andrew Roth]

Hello,

I have several sites that I want to deploy to one server.  The problem I'm running in to is that I need to deploy:setup each site to get the directories set up, but each deploy:setup is compiling ruby EE, which takes a while.  Is there a way to access the moonshine-less deploy:setup that cap provides?

-Andrew Roth

[Jesse Newland]

Ideally, the deploy:setup process would work like this:

* Run a quick shell script that Ruby is setup as configured (via apt, ree, or source, as configuration[:ruby] dictates)

** If this fails (either by the version being different or ruby not being present), re-run the ruby setup process

* Then run the SetupManifest to create directories as needed

For now, if you want to turn the setup process off in an app, you'll need to comment out this:

http://github.com/railsmachine/moonshine/blob/master/recipes/moonshine_cap.rb#L175-189

That should let you get the Cap default setup process back

Regards -

Jesse Newland
---
je...@railsmachine.com
404.216.1093

[Kevin Elliott]

I'd love to see this implemented, as I use moonshine to deploy several applications on a server.

-Kevin

--
Kevin Elliott

Mused in the Apple iTunes App Store

[Jesse Newland]

That's not a pattern that we really use that often at RailsMachine, so I haven't run into this. So, patches would be appreciated :).

Regards -

Jesse Newland
---
je...@railsmachine.com
404.216.1093

[Andrew Roth]

You have one virtual machine per web site?

[Andrew Roth]

What about making a manifest with only the rails tasks?  We who want that rails only deploy would make a cap task that specifies that manifest (ie not in core repo).

-Andrew Roth

[Jesse Newland]

Generally, we do only have one application per virtual server.

Adding support to the generator to create 'alternate' manifests - one for a secondary application, one for a non-Ubuntu server that just wants to manage gems, etc - would be excellent and the ideal way to implement this in my mind.

Regards -

Jesse Newland
---
je...@railsmachine.com
404.216.1093

[Andrew Roth]

Would you suggest adding options to the default generator, or making new generators?  ie. --with-rails-only, or a script/generate moonshine_rails_only

-Andrew Roth

[Andrew Roth]

What about something like this?

http://github.com/andrewroth/moonshine/commit/adce95a5f9dac9c8fd216206a6f422b44b6e6c30

I tried the alternate manifest route but it seems the manifest itself isn't what sets up the directories.  With that change I can do moonshine:bootstrap_rails_only which sets up the directories, then a deploy will install the stack (which is fairly fast when there's no updates).

-Andrew

[Jesse Newland]

If you edit that to make the task be named 'setup_directories' and change the inline docs to indicate that it applies this manifest - http://github.com/andrewroth/moonshine/blob/adce95a5f9dac9c8fd216206a6f422b44b6e6c30/lib/moonshine_setup_manifest.rb - which replicates the old deploy:setup behavior, I'll merge that in. Good compromise.

Regards -

Jesse Newland
---
je...@railsmachine.com
404.216.1093

[Andrew Roth]

Ok - http://github.com/andrewroth/moonshine/commit/9fd19dc77252b6f313b745ad4553963b764c1327