All the latest news and announcements, straight from the WooThemes HQ!
Behind The Scenes: SVN & Development
29. Sep, 2009 by Adii Rockstar in Development
We’ve received many questions on our development and how we manage to maintain and update 40+ themes. In addition to reading about our development cycle, the below screencast should give you a good idea of how we roll around here…
Behind The Scenes: SVN & Development from WooThemes on Vimeo.
19 Responses to “Behind The Scenes: SVN & Development”
29 September 2009 at 8:25 am #
Very interesting! thx for sharing this. Not used beanstalk as yet. I am just a bit concerned that you are displaying the urls of the main site [svn, etc]. Not advisable from security perspective. my 2 cents.
29 September 2009 at 9:23 am #
Beanstalk is great.
And whilst this may not be the greatest thing in terms of security, we haven’t shared any authentication details, so I guess we’ll be okay!
29 September 2009 at 11:05 am #
What program are you editing files in?
29 September 2009 at 12:01 pm #
I use Coda on Mac OSX.
29 September 2009 at 7:24 pm #
Interesting. I will try that out. I have been using TextWrangler on my mac which I like but it is very basic. Although – your code seems to have a lot of spacing in it sometimes and I’m not sure if that is your program or your methods.
30 September 2009 at 4:01 pm #
It’s a bit of both I think, Coda inserts a lot of spaces in CSS files as a part of its autocomplete function. (something that bugs the hell out of me)
But I think you’re talking about extra line-breaks, which as far as I know is done manually by the WooTeam to improve readability for users/customers when editing the code
29 September 2009 at 3:26 pm #
Is there a way to push the updates to the clients installation of the Woo Themes code or do they have to download the updates and manually update it themselves?
29 September 2009 at 4:52 pm #
All user update their themes themselves, by getting the new zip version on our site. I don’t believe there is a way to push out the source updates to a users web server, but in the future we hope to have an auto update function, so it’s easier for users to one-click-upgrade their themes.
30 September 2009 at 4:03 pm #
There would be if the Woo Framework was hosted externally I guess – but that would be server-load hell!
8 October 2009 at 3:05 pm #
That would be badass….
30 September 2009 at 4:16 am #
You should have a look at Warehouse: http://warehouseapp.com/
Warehouse recently became Open Source and is a Great SVN app
30 September 2009 at 5:08 am #
As far as I understand, Beanstalkapp is built on top of Warehouse!?
30 September 2009 at 5:39 am #
Oh right didn’t know that!
Warehouse is self hosted so it may help keep costs down.
But I will give Beanstalk a trial, look quite good
30 September 2009 at 6:40 am #
I’m a little concerned with self-hosting our SVN repositories though (I may be stupidly over-cautious here), because if the website goes down, then we can’t reach SVN and can’t continue working. If hosted on two different boxes you should be fine though.
30 September 2009 at 4:04 pm #
This makes a lot of sense to me – I was going to say the same
30 September 2009 at 4:04 pm #
Really awesome video guys – this is the sort of stuff I love to see: “Behind the Scenes”
1 October 2009 at 3:24 pm #
Thanks for sharing Adii. I also use Beanstalk (love it) but with tortoisesvn (PC only) since there wasn’t a real good gui svn client for the Mac. I didn’t know about Versions so now it’s time to make the switch.
So what do you guys use for issue/bug tracking? I use and recommend Lighthouse which integrates nicely with Beanstalk. Gotta love hosted apps!
http://lighthouseapp.com/
~Dave
1 October 2009 at 4:28 pm #
I use tortoiseSVN as well, as I’m the only PC g33k at Woo
We use Lighthouse as well, but haven’t hooked it up to Beanstalk yet… will have to look into that
4 October 2009 at 5:24 pm #
Thanks for sharing! We use TortoiseSVN at the studio, although haven’t tried Beanstalk yet.
Great work keeping all your updates in perfect order and documented.
Cheers!