modx gitify which files should be version controlled

#MODX GITIFY WHICH FILES SHOULD BE VERSION CONTROLLED UPDATE#
#MODX GITIFY WHICH FILES SHOULD BE VERSION CONTROLLED CODE#
#MODX GITIFY WHICH FILES SHOULD BE VERSION CONTROLLED FREE#

Finally, you will need SSH (Secure Shell) access to your server so the remote repo ( GitLab, Bitbucket, GitHub etc.) can safely communicate with your server.

Don't worry, the past couple years have seen an explosion of Git clients that provide a simple and beautiful graphic interface from which you access your local repo as well as those hosted on the above services, and many are free!

Many Git users use the command-line which isn't nearly as intimidating as it may sound but it's not for everyone.

#MODX GITIFY WHICH FILES SHOULD BE VERSION CONTROLLED CODE#

Such services are very useful for sharing public code as well as managing private projects and users while serving as a hub between the local repo and your server.

#MODX GITIFY WHICH FILES SHOULD BE VERSION CONTROLLED FREE#

There are online hosting services where you can setup a public or private remote repo, the more popular being: GitHub (Git free and paid), Bitbucket (Git and Mercurial free and paid) and Beanstalk (Subversion and Git paid).Files can be edited by any number of users from any geographic location, though there are ways of setting up a collaborative workflow that should be observed in order to prevent problems.Branches and merging can be immensely useful, it makes organizing projects easier as well as providing a safe environment for parallel testing and experimentation. Existing files can be branched (thus creating a new file) which can be independently modified by anyone and, if desired, be merged back into the main file at anytime.Kaleidoscope - by far the nicest but also the most expensive - it's a simple matter to set it as the default “difftool”. If you'd rather use a 3rd Party diff application, e.g. It's possible to compare different revisions of a file (using the command line) to see precisely what changed using the git diff command.

Files and folders can easily be kept out of the repo with a.

A VCS excels at collaborative workflows, this really is its milieu, though by no means do you have to use it in this way.

This type of workflow typically (but not always) requires 3 repos: local, remote (usually hosted), and a clone of the remote repo on your own server, though you only interact directly with two. See below for an explanation. Commonly referred to as “deployment” in VCS-speak. Instead of “Publishing” or “Uploading” files to a server you “Push” revisions from a repo to the server which replaces the current site file(s) with those from the repo.

#MODX GITIFY WHICH FILES SHOULD BE VERSION CONTROLLED UPDATE#

A VCS is frequently used in lieu of (S)FTP to update a website.Where this typical scenario may differ is if you only work locally (or work alone) and have no need for a remote repo. The local and remote repos communicate with one another so changes can be easily “Pushed” and “Pulled” so you always have the latest revisions no matter how many people are editing.Any number of users may be given access to the repo.A repository can be setup locally on your computer, on your own remote server or with a dedicated repository hosting service (see below). The heart of a VCS is its repository (repo), a central location from which users can search, Add (new files), Commit (file changes), delete/restore revisions and, if this is your goal, deploy to a website.When you edit a text file the changes are stored in a database and can be accessed or restored later. A VCS is typically used to manage website and software development but it's also a perfect tool for writers. First and foremost they are applications used to track, store and manage the state (or revision) of a file. A couple other popular systems include Mercurial and Subversion. Git is a Version Control System (VCS), sometimes referred to as Source Control Management (SCM) which is the parent term that encompasses more than a VCS.But sometimes when trying to decide if a workflow is right for you a simpler explanation is better.īefore we get started, and in the interest of establishing a baseline understanding for this article, here's a basic Git overview for those who may already be scratching their head.

Step-by-step how-tos for developing a Git-based workflow including all the command-line tips any sane person could ever want, so I see no point in rehashing what has already been thoroughly documented elsewhere.

There are numerous well-written articles that explain in painstaking detail the über technical aspects of version control. If you're like me - or how I used to be - you're probably reading this because you've heard of Git but aren't exactly sure what it's for, how it works or why you would want to use it. Rather it's a brief (and not too technical) overview of Git and an insight into why I took the plunge and what my experience has been so far using Git for web deployment in place of (s)ftp. If you're an experienced Git user this article probably won't be of interest as it's intended for those who may be on the fence about using version control.

Modx gitify which files should be version controlled