GIT Deployment

Navigation
0

Work in a site factory and among one of the actions of this semester is the implementation of GIT.

Today we work as follows:

We request a server, we install Joomla and we develop the sites in homologation environment before releasing for public access.

Some of our actions are taken after the site has been released and, incredible as it may seem, until my arrival on the team, the changes were made in the production environment. Hence the idea of implementing the GIT.

We do not have access to SSH from the server, so I thought about deploying via FTP.

I'd like suggestions on how to adapt our development routine to using GIT.

  • Create an approval environment on the same server, make edits and then a merge?
  • Create a local development environment?
  • What would be the ideal scenario?
asked by anonymous 11.06.2018 / 20:11

2 answers

1

It's really an open-ended question.

But my contribution, today I work with only 2 environments, homologation and production, then you would have a homolog branch and the other would be the master . If you are unable to access via SSH , continue deploying via FTP . But at least you'll have both a deployment validation and a client validation before making production changes.

There is no perfect scenario, because each customer is different from the other. I believe that with validation and quick delivery, everyone wins.

Your idea of creating the homologation environment is great!

    
11.06.2018 / 20:34
0

I recommend a branch for you to give checkout for each developer or by request.

    
11.06.2018 / 20:58
how to make a progress bar that goes from 0 to 70 and do not come back from the beginning? How to put two forms side by side?