[Catalyst] From Development to Production.
igavus at gmail.com
Wed Mar 2 18:32:44 GMT 2016
Go learn about version control and deployment automation, you can google these keywords and will likely be busy for the next few weeks ;-) it's a pretty wide and interesting reading
From: "Andrew" <catalystgroup at unitedgames.co.uk>
Sent: 3/2/2016 20:17
To: "The elegant MVC web framework" <catalyst at lists.scsys.co.uk>
Subject: [Catalyst] From Development to Production.
So, I'm trying to learn Modern Perl workflows,
and I heard it's best to do all your development on a development server,
rather than mess around with code live, on the production server.
So let's say I've coded my Catalyst app on a dev server, and it's in a folder called MyApp....
Do I just copy the MyApp folder to the Production Server?
[Am likely to copy and paste the folder using Cyberduck].
I mean, assuming the production server is setup to run it, and so forth...
Let's for example say, I'd already published Version 1.0 of my website on the production server.
And it's running from a MyApp directory on the production server.
Then I code a version 2.0 on my development server, in a folder called MyApp, and I want to publish that....
...do I just again, copy MyApp from my development server, over to my production server?
Obviously, new files would overwrite old ones.
What about if version 2.0 saw me delete some old unused stuff, do I have to make a note of what they were,
and go through the folder on the production server and delete them?
Or is there some graceful way to sync the development and production versions of my code?
What are other people doing?
Grateful for any insights.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Catalyst