The main thing that we will be working with is the Hg Workbench. TortoiseHG integrates with your context menu (right click menu). Open this file and follow the installation wizard. Ok, so now that you have your “Server”, we can install Mercurial with TortoiseHG. Here is my Google Drive folder with the shared “Dev01” folder inside. Permissions to the content can be governed by the access to this shared folder on the Google Drive settings. You should have received some email to notify you that someone has shared a Google Drive folder with you. Dropbox works great, but I will use Google Drive for now. This should be some folder that everyone needs access to in realtime. Mercurial is command line based and can be used without TortoiseHG, but this makes life a lot easier.įirstly, you will need your “Server” share. This can be seen as the user interface for the Mercurial system. This is the main thing that you will use to manage the source. This is the core of everything, but you do not need to worry about this, because you will not really work with it directly. It is a popular free distributed source control management tool. This is the source control software that we will use. So if someone pushes a change, it will become available to others immediately. Google Drive and Dropbox are nice because they syncronize the whole time. The only time that you will work on it is when you want to create a repo. I am mentioning the “Server” word here, because we need to remember – Never do changes, add files, work on, or do anything on this shared drive. We will be using shared Google Drive folders that will act as our “Server” repositories. If you are reading this, you probably have this running already. If everyone follows these procedures, this can become a very nice source control environment for all of us to work with. It is very important that everybody using this repo understands how it works and follows the simple guidelines and rules. It looks like a lot, but it isn’t really (lots of pics). Please take some time to read through this document and understand how this works. If you are reading this, you have been given access to a shared repository to collaboratively work with some other people. Let me know what you think, or if you have some suggestions to improve this: Here is the guide that I shared with them. The other thing that I did not want to do is run home server on a static ip via dyndns for various reasons. This will work for your own work or collaborative work. Firstly, I know there’s GitHub and Sourceforge etc., but that is not “personal” enough for the free solutions. It is either a local folder, on Dropbox or a flash drive or something, but there is no source control management whatsoever. So me and a couple of friends all have our code base for our random projects. Please note that Google drive gives plenty of issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |