Deployment of GIT

Asked

Viewed 100 times

1

I work in a site factory and among the actions of this semester is the deployment of GIT.

Today we work as follows:

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

Some of our actions are done after the site was released and, amazingly, until my arrival at the team, the changes were made in a production environment. Hence the idea of implementing GIT.

We don’t have access to SSH server, so I thought deploy via FTP.

I would like suggestions on how to adapt our development routine to the use of GIT.

  • Create an approval environment on the same server, make edits and then a merge?
  • Creating a local development environment?
  • What would be the ideal scenario?
web-application git versioning

  • His question is entirely based on opinions and is therefore impossible to elaborate a canonical answer. When you get a minimum of 20 reputation points, you can discuss it there in our chat.

  • The workflow who will decide are you, recommend the course: Git Complete: From Basic to Advanced. Once you get a better sense of Git you’ll know how to deploy it.

  • Thanks for the suggestion.

3 answers

3


It really is a question open to discussion.

But there is my contribution, today I work with only 2 environments, homologation and production, so you would have a branch Homolog and the other would be master. In case you cannot get clearance for access via SSH, continue deploying via FTP. But at least you will have a validation of deployment and also of the customer, before making changes in production.

There is no perfect scenario, because each client is different from the other. I believe that if there is a validation and a fast delivery, everyone wins.

Your idea of creating the approval environment is great!

2

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

1

Good morning, Thiago!

I agree with the opinion of Vinicius, continue with deploys via FTP, if not already implemented, to deploy with GIT via FTP there is a GIT repository that can help you GIT-FTP and has all the necessary content.

To the point of organization:

Use a Branch master - It is the branch that contains code at the production level, that is, the most mature code in your application. All new code produced is eventually merged with the master branch at some point in development;

Branch develop - It is the branch that contains code at the preparatory level for the next deploy. That is, when Features are terminated, they are merged with the develop branch, tested (together, in the case of more than one Feature), and only then do the updates of the develop branch go through one more process to then be merged with the master branch;

If the project is very large and has many Ports, use the organization by Branches Feature - These are branches in which new resources are developed for the project in question. These branches are conventionally named starting with Feature/ (example: Feature/new-layout) and are created from the develop branch (as one resource may depend directly on another resource in some situations), and are ultimately merged with the develop branch;

If you’re interested, you can read the git flow, recommend.

Hugs

Browser other questions tagged web-application git versioning

You are not signed in. Login or sign up in order to post.