I'll second this setup with a few caveats... Development environment - Developers have non-root access but have freedom to do most anything with their app. Often have extra sudo tools they can use (chmod for example) Test environment - Developers "release" to the test environment to allow for correct construction of the release and for testers to work on a "stable" platform while developers are still fixing bugs and making changes. QA Environment - Nothing but a "lets test the release process itself" environment along with a final functionality test environment. Production - Production, no one but the admin crew have root or elevated privileges in this environment. The application support team has elevated, but not root, privileges.
Code versioning system like SVN or GIT should be used to manage the code. Build and deployment process should be automated use some tool like Jenkins. Automated tests should be built and be part of the normal deployment process to any environment. If you have a good Build system setup (SVN/GIT + Jenkins + Automated Testing) you can often do without the QA environment. Andy On Tue, Sep 23, 2014 at 3:58 PM, Jack Coats <j...@coats.org> wrote: > Sounds like you need a 'real test' or development server ALSO. > > I use to recommend production, staging, and a development or test > server for each group doing testing or development. > > Production was just that. Developers were not allowed to log in with > other than standard user permissions. Staging was often 'recovered' > from a backup of the production so developers could install their 'new > and improved' there so it could be tested by others before being > deemed production worthy. > > But that was in the dark days when I got a paycheck. That has been > several years ago now. > > I can say the system works, even if it is more overhead. Other ways > of dealing with upgrading software and systems may work, but this > method worked well for me. It also kept developers from doing 'just > one little thing that won't change anything' on the production > servers. And yes, I even imposed it on myself, after having brought > down servers inadvertently several times over years, that was a good > thing too. > > -- > -- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To post to this group, send email to nlug-talk@googlegroups.com > To unsubscribe from this group, send email to > nlug-talk+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to nlug-talk+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to nlug-talk@googlegroups.com To unsubscribe from this group, send email to nlug-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to nlug-talk+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
