This topic is locked

Publishing files to production

1/25/2012 9:46:03 AM
PHPRunner General questions
mcebula author

Hi, I have a basic question on deployment of output files and best practices. I'm a little new to deploying web software since I'm not a programmer. I'm on PHPR 6, build 9948.
I always build all files in my project, it just seems easier to me to always to build all and upload the entire output directory when it's time to go to production. My app has about a dozen update users and few dozen read-only users. Only a handful might be in at any given minute.
My question is this- do I need to be concerned about users being in the software when I'm uploading a new set of files to production? I use external FTP tool (Filezilla) to upload files to production server. So far I've done it a few times successfully but I suspect no one was using software at the time but usage may rise over time so I'm a little concerned.
Since this is a department level app I do have ability to email all users if I need to. If seeing who's online is something I need to worry about then I will need build something into my app track users so I have some view of who is online at any time (that might be a nice idea for a future built-in feature of PHPR, some kind of who's online page). Another alternative I guess would be defining a maintennace time window for updates.

Sergey Kornilov admin 1/25/2012

As a rule of thumb - software updates are recommended to perform overnight or on weekends when number of users is minimal.
Depending on what sort of changes being applied existing application users may or may not be affected. If database structure changes and users were filling Add or Edit form they may not be able to save data and may lose their work.
If this is your internal department app simply email users about downtime/update timeframe and run the update at the end of the day.
PS. Who is online feature can be definitely added however it won't be much help in this situation.