Update 2: as pointed out by , several comments on , and the excellent book, seems to be a better solution for multi-user hosted Git than Gitosis. I particularly like the branch—level permissions aspect, and what that means for business teams. Update: the ever—vigilant has pointed out that my instructions for and were slightly askew. These errors have been rectified. Given how much of my life revolves around technology, a large part of this will be consolidating the various services I consume and often pay for. For this reason, paying money to GitHub awesome though they may be seemed wasteful. So I decided to move all my private repositories to my own server. This is how I did it. Test it out: ssh git myserver. Otherwise, do it as the Git user we added above. If using the Git user, log in as them: login git Now we can create our repositories: mkdir myrepo. Repeat that last step for each remote Git repository you want. Log out of the server as the remaining operations will be completed on your local machine. Configure your development machine First, we add the remotes to your local machine. PasswordAuthentication no Where 2207 is a port of your choosing. Dropbox seems able to get through most corporate firewalls my blocked SSH, for example , and is very unobtrusive in its synchronisation behaviour. Enough introductions, make with the commands Okay, here we go. Basically we made a bare repository in the Dropbox directory. This Git repository will now be available on all computers that your Dropbox account is. I think this approach could be valuable for things like keeping personal documents or text files in version control or indeed personal coding projects without bothering to set up your own Linux box or server. Git really does make these things incredibly easy. Folder sharing is a bit of a pain to install, especially because OS upgrades on the guest seem to break the guest tools installation. The solution is one of the oldest file sharing technologies there is:. It also supports symlinks, which means you can sidestep. Configuration time This is the easy bit. First we export whichever folder we want to share from the host OS. In my case my VM listens on 192. The rest of the flags you can ignore. Now we need to run a few commands in the OS X terminal to complete this side of the configuration: sudo nfsd checkexports showmount -e If everything went well no errors should be reported and your exported directory should be printed to stdout. Now on the guest OS, you first need to install the NFS software. We can now configure fstab so mount knows what to do. What I can do, however, is tell you how I set up , which is a super light—weight web server, on my VPS here on who are awesome, by the way. This server currently serves the meat of my site. Static assets JS, CSS, images are served directly from Nginx without ever touching Apache. Get Nginx At the time of writing, the latest stable version of Nginx was 0. Note that we need full source code as the version that ships with Ubuntu and Debian is 0. Compile Nginx We have a few different options to run here, most of which are personal taste. Feel free to modify as required:. If you want to use a different user account, be sure to create this user before running. Make Apache listen on a different port I chose port 8080, since that seemed sensible and symmetrical. You should see your old site there. When you next start Nginx, it should send all requests through to Apache on port 8080, and your memory overhead should start coming down. Additional reading This article is based on the hard work of those awesome people over at , and my experience on their servers. To check what interfaces are listening, period, use this command: netstat -pant. This article is really nothing more than me pointing at a link to. The solution is to. Also, the JeOS version of Ubuntu 8. Update 29th June, 2009: , which contains an updated VMWare Tools package for Ubuntu 9. This removes the requirement to edit the source files as. I live in fear of trashing the default Apache or Python on my Mac and not being able to recover from it. I will continue to use my Mac as my main machine, because I love , and , and , and all the other applications on my Mac. I love the toolset available to me, and value the user experience. Following are some hopefully bulletproof instructions for setting up a virtual—machine friendly version of Ubuntu Server, as pointed out to me by in VMWare in such a way as to make it an ideal development environment. I recommend 256MB RAM and HDD of about 10GiB. You now have a fresh virtual machine. Polish the settings change HDD size, for example , and start it up. At this point, we need to differ from the usual Ubuntu install process and change our install mode. Now the machine will start up, so we can install VMWare tools. This gives us the benefit of Shared Folders, which let us treat the machine as a local folder, so we can use or other local tools to edit files within the system. This is the real key to making the development VM usable. After the machine starts up in a VMWare window, log in and type ifconfig. Take note of the IP address in the eth0 section alongside inet addr:. Since the terminal provided by basic Linux is a bit sparse on features, install SSH with sudo apt-get install ssh. When this completes, log out and open Terminal. Now we need to update the system a bit. Note: if you ran dist-upgrade above, you should restart your virtual machine now with: sudo shutdown -r now. Otherwise you may get clashes with kernel versions in the next step thanks. Now we can get on with installing VMWare tools. At this point you can basically accept all the default dialogue options until it completes. Edit: as has rightly pointed out, passing the --default flag to the install command automatically accepts all defaults for you. Now your VM can write back to the shared folder, and all is well. From a local terminal on your Mac, type: defaults write com. Now you can close VMWare with a running VM and not have the machine stop. This is one of the biggest wins of virtualisation in my opinion—making it easy and non—dangerous to experiment. Also, thanks to Danny for helping me out a bit and for being my guinea pig. Update: A note on Symfony A have written and asked me about how to get running under this set up. This configuration means that Symfony runs with the same permissions as your primary user, which gives it full control over your project directories, and also inherits the permissions granted by HGFS. Needless to say: never do this on a public web server.
