ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Updating to latest EE version when all files are in .svn

October 18, 2011 10:32am

Subscribe [3]
  • #1 / Oct 18, 2011 10:32am

    TheBlackHole

    72 posts

    Hi all,

    How do you guys go about updating to the latest version when the EE site is under .svn version control? There are too many files to change individually and I know if I copy over the system folder in Finder it will remove all the .svn files.

    Cheers

  • #2 / Feb 17, 2012 6:03am

    TheBlackHole

    72 posts

    Hi everybody,

    I’m really curious to how you all handle this. Does anyone use Subversion with EE sites?

    Cheers

  • #3 / Feb 18, 2012 10:44am

    Gareth Redfern

    86 posts

    There is a great two part post on using GIT and beanstalk to version control you EE sites here: http://www.johnfaulds.com.au/journal/developing-expressionengine-sites-with-mamp-git-tower-and-beanstalk-part-1/

    I haven’t managed to do a complete version control of all the EE files yet but I do keep all my CSS, Js and EE templates in one assets folder then version control that using GIT and beanstalk to deploy. Works pretty good for me.

  • #4 / Feb 20, 2012 5:36am

    TheBlackHole

    72 posts

    That’s an interesting approach Gareth, I’d really like to have it all under version control if possible. Hopefully someone will have done it!

    Thanks for the point to that article, I’m sure there will be tips in there that would work across any version control.

    @gareth - I edited my answer as I hadn’t read your answer properly originally. Monday morning 😖

  • #5 / Feb 21, 2012 5:35pm

    Dave O'Brien

    6 posts

    We’ve got the whole shabang under version control and I dread updating the core and addons to be honest. I make a copy of the site, then delete thru svn and add the files back in - my templates etc are kept out of the system/expressionengine folder like Gareth’s so I’m only losing the repo history for first-party and third-party code (with the exception of config.php. That said, you could do most of the leg work in here with http://ee-garage.com/nsm-config-bootstrap and locate that outside the system/expressionengine folder.

    I’m starting to take a serious look at keeping the EE core separate and using a shedload of symlinks (cue bash script) to replicate the ee structure within the repository. Which means the index.php, admin.php, images, templates, css & js are under version control and first-party and third-party files are kept elsewhere.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases