Rails - May 2013 - remove rails application safely and neatly on debian server

Hi all, maybe it will be a strange question but as a sysadmin  , I have to 
move a rails application with his environnement from a server to 
another(vps) . I would like know how can I clean correctly  and safely the 
old server (the application is using bundle and erbenv and stuff). i would 
like to know how I can remove all code and library  safely.

Thanks
Aina Anjary Fenomamy

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/977dec47-7d76-4edc-8b93-04de68e4476a%40googlegroups.com?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.

On Wed, May 29, 2013 at 7:25 AM, Anjania Catus
<anja1catus-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> Hi all, maybe it will be a strange question but as a sysadmin  , I have to
> move a rails application with his environnement from a server to
> another(vps) . I would like know how can I clean correctly  and safely the
> old server (the application is using bundle and erbenv and stuff). i would
> like to know how I can remove all code and library  safely.
>
> Thanks
> Aina Anjary Fenomamy
Hi, Aina,

I *wish* this had a nice, straight-forward answer, but sadly, the
answer is "It Depends".

*If* the app developers followed the standard conventions, all the
code, assets, and other such non-database things should be under the
root of the application. That you can tar up and move over.

The next bit is the database itself. Depending on database chosen,
you''d use the appropriate tools to fully backup the database schema
and data and move that to the new server, create the database, and
load up the schema and data.

Thirdly is the actual web server configuration, and this is where it
really gets into the "It depends" thicket.

None of these is really how I would go about this, but then for
deployments I would have firstly gone the route of using a deployment
tool like capistrano, parrot, chef and the like. *IF* your application
developers and devops have already set this up, then it should be a
more straight-forward operation, with really oly the copy and
migration of the database data to worry about.

Sadly, without some real direct knowledge of your setup and situation,
it''s hard to give very useful or good advice.

If the developer or devops of the original system aren''t available for
consultation, it will probably involve learning a lot more about
deployment of rails apps in general, and then looking at the specifics
you have at hand.

Best of luck!

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/CAHUC_t_3a%3DSseW%2BcvzLg_gTVf8tGdNLQqygwvyf80hCesEcayQ%40mail.gmail.com?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.