Re: [Catalyst] From Development to Production.

On Wed, Mar 9, 2016 at 7:35 AM, Dermot wrote: I want to caution you, in the nicest possible way. Writing software > requires a number of skills and a lot of research and learning. You can't > avoid the latter. What may seem like a lot of unnecessary aggravation > (testing and

Re: [Catalyst] From Development to Production.

I'd suggest these files are the Model part of MVC and you should have a Class that you use to interact with files. This Class is independent of you Catalyst App and should be able to run in it's own right. Page 135 of the book discussing Database model because that's the common model but

Re: [Catalyst] From Development to Production.

META: my reply including the list but was bounced because my default email address was not the one I subscribed with. I'd suggest these files are the Model part of MVC and you should have a Class that you use to interact with files. This Class is independent of you Catalyst App and should be

Re: [Catalyst] From Development to Production.

It sounds to me like you should treat these text files as the data model ---> Are you suggesting I do something to them, or is this just a linguistic point about what to call or refer to the data as? I'm new to Catalyst and previously coded in procedural perl, where I always used a

Re: [Catalyst] From Development to Production.

Does anyone have any advice? Looking for the best way to handle permissions. My web app stores data to text files, in a directory. While it makes sense to have a development server, and a production server, when it comes to updating the scripts in the lib folder it doesn't make much

Re: [Catalyst] From Development to Production.

.co.uk> Subject: Re: [Catalyst] From Development to Production. This is not exact. If you upgrade system libs (provided it's an upgrade for the same release of your distribution), you should not need to recompile anything. Binary API is guaranteed to remain compatible between upgrades of

Re: [Catalyst] From Development to Production.

--- > >From: Jorge Gonzalez <mailto:jorge.gonza...@daikon.es> > >Sent: ‎3/‎3/‎2016 10:34 > >To: catalyst@lists.scsys.co.uk <mailto:catalyst@lists.scsys.co.uk> > >Subject: Re: [Catalyst] From Development to Production. > > > >This is not exac

Re: [Catalyst] From Development to Production.

.co.uk <mailto:catalyst@lists.scsys.co.uk> Subject: Re: [Catalyst] From Development to Production. This is not exact. If you upgrade system libs (provided it's an upgrade for the same release of your distribution), you should not need to recompile anything. Binary API is guaranteed to remain compat

Re: [Catalyst] From Development to Production.

Yours, Andrew. - Original Message - From: "Trevor Leffler" <tleff...@uw.edu> To: "The elegant MVC web framework" <catalyst@lists.scsys.co.uk> Sent: Wednesday, March 02, 2016 6:54 PM Subject: Re: [Catalyst] From Development to Production. Yes, that. But to

Re: [Catalyst] From Development to Production.

Message - From: "Trevor Leffler" <tleff...@uw.edu> To: "The elegant MVC web framework" <catalyst@lists.scsys.co.uk> Sent: Wednesday, March 02, 2016 6:54 PM Subject: Re: [Catalyst] From Development to Production. Yes, that. But to be a tad verbose about i

Re: [Catalyst] From Development to Production.

n auto deployment, and you're not copying > > folders > > > and files, how are you checking out your code from the production server? > > > > > > Grateful for all the insights, > > > > > > Yours, > > > Andrew. > > > > > > > &g

Re: [Catalyst] From Development to Production.

t; If you're not doing an auto deployment, and you're not copying > > folders > > > and files, how are you checking out your code from the production server? > > > > > > Grateful for all the insights, > > > > > > Yours, > > > Andrew.

Re: [Catalyst] From Development to Production.

.co.uk> Sent: Wednesday, March 02, 2016 8:40 PM Subject: Re: [Catalyst] From Development to Production. +1 for Carton for managing perl application dependencies. Also perlbrew or plenv for using your own perl / separating your app from the system perl. I agree whole-heartedly with James re

Re: [Catalyst] From Development to Production.

- From: "James Leu" <j...@mindspring.com> To: "The elegant MVC web framework" <catalyst@lists.scsys.co.uk> Sent: Wednesday, March 02, 2016 8:23 PM Subject: Re: [Catalyst] From Development to Production. It all comes down to the apps 'environment`. Do you remember

Re: [Catalyst] From Development to Production.

checking out your code from the production server? > > > > Grateful for all the insights, > > > > Yours, > > Andrew. > > > > > > > > - Original Message - > > From: "Trevor Leffler" <tleff...@uw.edu> > > To: "The elega

Re: [Catalyst] From Development to Production.

e keywords and will likely be busy for the next few weeks ;-) it's a pretty wide and interesting reading From: Andrew <mailto:catalystgr...@unitedgames.co.uk> Sent: ‎3/‎2/‎2016 20:17 To: The elegant MVC web framework <mailto:catalyst@lists.scsys

Re: [Catalyst] From Development to Production.

depending on how far you want/can take it. > > > > Cheers, > > --Trevor > > > > > > On 03/02/2016 10:32 AM, Toomas Pelberg wrote: > > > Go learn about version control and deployment automation, you can > google > > > these keywords and will likely

Re: [Catalyst] From Development to Production.

> > To: "The elegant MVC web framework" <catalyst@lists.scsys.co.uk> > Sent: Wednesday, March 02, 2016 6:54 PM > Subject: Re: [Catalyst] From Development to Production. > > > Yes, that. But to be a tad verbose about it... > > Use version control and

Re: [Catalyst] From Development to Production.

l the insights, Yours, Andrew. - Original Message - From: "Trevor Leffler" <tleff...@uw.edu> To: "The elegant MVC web framework" <catalyst@lists.scsys.co.uk> Sent: Wednesday, March 02, 2016 6:54 PM Subject: Re: [Catalyst] From Development to Production. Yes, t

Re: [Catalyst] From Development to Production.

ours, Andrew. - Original Message - From: "Trevor Leffler" <tleff...@uw.edu> To: "The elegant MVC web framework" <catalyst@lists.scsys.co.uk> Sent: Wednesday, March 02, 2016 6:54 PM Subject: Re: [Catalyst] From Development to Production. Yes, that. But

Re: [Catalyst] From Development to Production.

's a pretty wide and interesting reading From: Andrew <mailto:catalystgr...@unitedgames.co.uk> Sent: ‎3/‎2/‎2016 20:17 To: The elegant MVC web framework <mailto:catalyst@lists.scsys.co.uk> Subject: [Catalyst] From Development to Production.

Re: [Catalyst] From Development to Production.

3/‎2/‎2016 20:17 To: "The elegant MVC web framework" <catalyst@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