![]() ![]() If you use your own server as an Origin repository, then it is easiest to track changes visually using GUI based third party desktop software. If you choose to use an online repository, they all have a user friendly GUI to enable you to inspect changes and track back through the commit log. You could create an origin repository on your own server, however there are many great online providers including GitHub, Bitbucket, and Gitlab. Think of it like a time machine for your development work. Your origin repository, is the repository that is used to store all changes and acts like a complete backup of your code and any work that you have done. Your terminal should now look something like this: $ git config -global user.email any time you can check these configurations using the following command: We need to configure ' git' with our name and email address like so: $ git config -global user.name "New User" Once the installation of ' git' is complete, we should use the ' git config' command to ensure that our commit messages contain the correct user information. ![]() We don't require any of the suggested packages immediately, so proceed and click yes to proceed. Your package manager will list the new packages that will be installed, and also make some suggestions regarding other useful associated packages that could be installed. If this is the first time using the package manager since you logged in to your server, remember to update its package list first. You can check to see if it installed with:Īssuming ' git' is not installed, you can install it using the ' apt' package manager. $ ssh may already have ' git' installed on your system, especially if you used something like EasyEngine or other automation tools to install your LEMP stack. Install Gitįirst login to your server if you haven't already: The tutorial examples will also be using ' ' as my main site domain, and ' ' as my staging site subdomain, remember to replace these with your own site's domain and staging site's domain in the relevant files and commands. Please replace my superuser with your own when issuing the tutorial's commands. So if you haven't completed either of those combinations of tutorials yet, then please do so first before returning here.Īs in the previous tutorials, all instructions will be issued by my superuser ' new_user' using the sudo command where necessary. This tutorial follows on directly from two of the previous tutorials in this series, and can not be completed without finishing Part 1 together with either Part 2 or Part 3. We will use ' git' to push changes between the local, staging and production environments. In this final tutorial, we will set up the Git distributed version control system (/) and connect all our environments. The staging will be used to test code changes to the site on an exactly matching environment to the production site. Previously in this series we copied the main production site, with which we created a local development environment, alongside an online staging site. In Part 4, we will look at Git version controlled deployment. In this series of tutorials we will implement a modern development and deployment workflow for WordPress on an Alibaba Cloud Elastic Compute Service (ECS) instance with LEMP (Linux, Nginx, MariaDB, PHP) installed. Tech Share is Alibaba Cloud's incentive program to encourage the sharing of technical knowledge and best practices within the cloud community. By Jeff Cleverley, Alibaba Cloud Tech Share Author. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |