Using SpringLoops for developing eWrite
As a developer Im quite aware that I should have begun to use version control a long long time ago to develop our apps.
More than once I read about and tried to use CVS or SVN. The learning curve to set these systems up on a server is probably not too steep but I was continually dissatisfied and turned away from it.
I wrote my own version control system at one point using PHP to monitor changes in the files and collect any comments in the changed files. The PHP code could also upload the changed files to the users servers. This worked quite well for a time but I was worried about security and I had a tendency to get bogged down in the development of the system itself instead of what it was supposed to do to help me in my daily work.
Earliy in September I came across SpringLoops and found they offer a free version of their source code management tools. Their free version allowed me to create 1 repository so I signed up and created a repository for eWrite Lite.
I installed TortoiseSVN on my desktop machine and on my laptop and got used to downloading and updating the code from both locations and getting familiar with the terminology.
I’ve read plenty of tutorials and blogs where developers encourage the use of version control. More than once a developer would write “Use version control, you can thank me laterâ€. The smug feckers were right. I’ve been using SpringLoops and TortoiseSVN for a few weeks and its allowed me a freedom to concentrate on the development of the software rather than fiddling around with my own bad habits.
I used to have HP servers in the attic running Ubuntu Server with Apache, PHP and mySQL to host, develop and backup everything I was developing. I sold off all the servers, replaced a dodgy router and ran CAT5e 100MBPs cable through the building rather than using a wireless connection.
On my desktop machine I use WampServer to deploy a development environment of Apache, PHP and mySQL in Windows XP. I can write and test the code on my local machine and use TortoiseSVN to commit the changes to SpringLoops and deploy the stable versions to customers sites.
Im still learning my way around SpringLoops and version control abilities in general. I’ve upgraded to the ‘Field’ package on SpringLoops to allow for more repositories and servers to deploy to.
The packages that are available are more than enough for my needs in some cases but lack a little in others. For example the ‘Field’ package Im using now has 10GB of space, 100 protects and 20 servers per project. The space and projects are way more than I need, but the servers per project are important to me, I need more.
The next package up allows for only 30 servers. I emailed SpringLoops to ask if there were customized packages available. They seemed helpful at first asking what I would need. I asked for at least 50 servers per project and far less space and projects. I’d be more than happy with 10-15 projects and 2-5 GB of space. I didn’t get any reply to that, they probably think Im joking. I’ll contact them again shortly to see if they’ll allow it.
Developing with SpringLoops for the past few weeks has been great. I’ve been able to develop the eWrite products much faster, commit changes to the server and deploy these changes to clients sites with just a couple of clicks, It is far far faster than FTP. I wish I had joined the version control party sooner, the eWrite software and my time are all the better for it.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=f5b8c2ab-0e32-4b8a-814a-1484d123e40a)
I’d agree with you about Springloops, it’s a great service. Like yourself I’ve only quite recently started using it for development. I found that getting use to the new workflow process (i.e. not forgetting to Commit regularly) took a bit of time, but since then there are big benefits.
Im getting used to that myself. My problem is that I work away on one machine, commit changes, then go off to the laptop in the evenings and commit changes there too forgetting to update it with earlier changes.
You need to stick a post-it on the laptop saying “UPDATE”…a low-tech solution to solving all your problems
I like it
Same goes for you with ‘Commit’
Look at Capistrano http://www.capify.org/ for multiple server deployment.
Looks good, based on Ruby though.. hmm
I’m just reading this post now (v.busy week). I looked at Springloops too, but eventually went for self-hosted version control with an integrated build system. Great for automatic deployment (plus lots of other goodies too). I just wrote a blog post on it over on my blog if you want to find out more.
Yah, Just read your blog about it. I’d love automatic deployment, I thought it was available in Springloops but its only available for one server per project.
Once I’m more proficient in using version control I might move over to self-hosted, I don’t want to spend too much of my own time getting my head around it. Other than the automatic deployment, SpringLoops is working out very well for me at the moment.
Cool. Well if you do decide to get it setup, let me know and I’ll give you a hand.
Cool, I will. Thank you.
[...] Using SpringLoops for developing eWrite [...]
[...] use Springloops to version control our ewrite software. I’ve been using it for a number of months now with excellent results. I can easily get the [...]