Is there a way to upload all your changed files to live with unfuddle (or even svn)?

eg, I make 1 or two changes locally on my testing machine.
SVN them to unfuddle.
Then upload the changed to the live server without having to FTP. individual bits?

Thanks for your time,

DanCourse

Dan,

This is very possible. We provide a callback for each repository which can ping a specific URL with basic information about each new commit to the repository as they are made. You could set up your server to respond to this “ping” by automatically checking out the repository.

Alternatively you may want to check out a deployment tool such as Capistrano . Capistrano can help you easily deploy your source code to a server with just a simple command from the command line. Tools like Capistrano are generally better than the above solution for pushing code into a production environment since they help manage many aspects of the deployment.

In general, Unfuddle offers a lot more features than Springloops does, but here is one area where Springloops offers a more elegant solution. They have a deploy option that will deploy all changes to one’s server, using either the FTP or SFTP protocal (the customer gets to choose). Using Springloops, we were able to get our graphic designers and programmers to give up on FTP and SFTP. Instead, when people want to get something to the server, they just commit to Subversion. There is the added benefit that no one can ever overwrite someone else’s files on the server, since all files have to go through Subversion first, and Subversion catches all the conflicts.

I realize that something similar can be set up with the ping that you are suggesting here, but myself, as the customer, has to do a bit more work this way, when compared to Springloops. More so, doing a checkout, or update, to the actual server means the actual site will have a “.svn” folder inside of every folder. This is a hassle if the code ever gets moved to a new location, and possibly even a security risk.

I like the combination of features that Unfuddle offers. I hope you all will think about providing better deployment options in the future.

Big fan of Capistrano here; however, I do think a Springloops-like deployment would be an excellent addition to the unfuddle system. There is a bit of overhead to setting up and learning how to do Capistrano deployments, and for smaller projects, I can see people preferring a point-and-click deployment option.

David, are you guys considering adding this kind of functionality? I can imagine this is a frequently requested feature, which seems to be a logical extension of your current product mix.

Greg,

We have not planned to add this functionality. However, we have not yet ruled it out either. We have had a number of customers request the ability to do this so we may still consider this for a future release of unfuddle.

Can we write our own post commit scripts? That would certainly take care of the problem and it would be the most flexible solution, as your customers could then write their own code. However, I imagine such a thing might cause you all security issues. Still, for my part, I’d like to take advantage of the post commit hook, as they’ve described it here:

http://subversion.tigris.org/faq.html#website-auto-update

I know for one my projects, I have a python script running on the server that automatically checks the SVN revision and automatically deploys any new revisions, like what “David C.” suggested. This works pretty well, and can be adapted for other things like continuous integration.

jumpfroggy, is this for an unffudle account? would you be willing to share the code?

Beanstalk has a similar deployment mechanism to Springloops which has been quite useful for our newbie-SVN using staff. It was not without issues though, there were a few times when not all changes got pushed through.

It would be nice if Unfuddle had some documentation on various ways to deploy.

It’s been two years and unfuddle has not yet added this feature. I’ve already become comfortable with unfuddle especially with it’s ticketing system but the lack of sftp/ftp deployment feature has kept me looking for other alternatives. Sure there is capistrano, phing, etc, but it’s such a pain to set up with each small/medium sized project. I’m lazy, I don’t want to setup commit hooks or upload via ftp client. I’m looking at ProjectLocker, it has trac, remote ftp deploy, as well as autodeploy feature, even a lot cheaper too. The interface is a little bit outdated but it works well: https://www.projectlocker.com/scenario/startup

+1 for auto-deploy