|
GettingTheCode
Getting The CodeDownload a full archiveThe easiest way to get the latest version of the code is by snagging pre-built archives, available here. SVNFor the more savvy developer, you might want to grab the code via subversion. If you're upgrading for instance, you probably will want to replace the items in vendor/plugins and vendor/rails by following the directions below. SVN CheckoutIf you don't have your application already checked into svn you should do the following.
# Replace the url with a REAL working download...this is just an example. wget http://substruct.googlecode.com/files/substruct.tar.gz tar -xzvf substruct.tar.gz cd substruct_app rm -rf vendor svn export http://substruct.googlecode.com/svn/trunk/ vendor SVN ExternalsIf you already have a Rails application setup and checked into svn...you can make sure that you have the most stable (and up to date) setup of Substruct by using svn:externals. 1. Delete your plugins directory in svn svn delete substruct_app/vendor svn ci -m "Preparing for substruct installation" svn update . 2. Edit your externals definitions svn pe svn:externals substruct_app This will bring up the property edit page for svn:externals. Externals make sure that you have the latest copy of everything from multiple svn repositories when executing a 'svn update' command. 3. From the window that comes up enter the following: vendor http://substruct.googlecode.com/svn/trunk/ 4. Save this file in your editor. 5. Commit your changes to svn by running a 'svn commit' 6. Run a 'svn update' You should see all of the items being fetched from their externals. This is how I set up all of my Substruct projects. The beauty here is that you can update at any time just by changing the external definition. Where To Now?Check out the installation instructions |
Note that currently for the above you will need to replace substruct.tar.gz and substruct_app with the latest version found in http://substruct.googlecode.com/files/
Also for externals step 2 you need to be in the directory 'below' your app, then run it.
If you use externals and plan on editing substruct code, I'd recommend just making copies of the files you edit in your own app's directory (as specified on http://code.google.com/p/substruct/wiki/Customizing) so that it's easy to svn update and still have customized code.
Just observe that in order to be able to contribute sending patches using svn diff (as specified in ContributingToSubstruct), you need a "working copy" checked out, using svn export the contents are not maintained under version control. You need to use svn checkout instead.
You may want to consider using piston http://piston.rubyforge.org/ to include the substruct code into your project.