DEV Community

Cover image for Current State-of-the-Art for LAMP Workflows?

Current State-of-the-Art for LAMP Workflows?

Benny Powers 🇮🇱🇨🇦 on November 15, 2018

Hey There, Dev! What's the current state-of-the-art for LAMP workflows? My client has a small team, and they're currently just uploading files via...
Collapse
 
david_j_eddy profile image
David J Eddy

Before you do ANYTHING, you MUST have buy in from both the business operators and the dev team. If anyone doubts the the positive impact this updating will do, the effort will sour. This is the part of 'DevOps' that is often overlooked. Culture and faith are just as important as tools and process.

As the Agile Manifesto states it:

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

That being said. I have done exactly what you are talking about. I would take it a step further and deploy the application images to DEV, then Stage, then Production. I am a big supporter of environmental parity. Deployment to Dev is the same as Stage is the same as Prod.

Also, 100% agree with @goyo ; the team has to understand what the tech is doing being using fancy GUI's. Learn the tool, master the tool, abstract the tool.

If you would like any assistance, I am looking for some gig work ;).

Collapse
 
goyo profile image
Grzegorz Ziemonski

In my experience, Docker is a great way to enhance your local development workflow, but... you need a strong understanding of the basics. Hence, I'd opt for starting without any GUI wrappers and advanced tools (e.g. docker-compose), at least until the team understands Docker well enough to know what these tools are doing for them, other than "magically making it work".

Can't say anything clever about the other points, so I'll end here ;)

Some comments have been hidden by the post's author - find out more