Hello people,
I started using Versions not long ago, and I'm still learning the ins
and outs of the SVN system. Overall it seems like a very solid and
easy to use app, so my question isn't directly related to Versions
itself. However, the problem might be solved through the use of
Versions.
Anyway, here's the problem: I'm working on a WordPress theme, and I
have a repository setup at projectlocker.com. My entire WordPress
folder is located at the repository, and that includes my theme(s),
plugins and content for posts (images, etc.). I'm not sure if this is
the correct way to set things up, but I'll get to that later. It all
works fine, commits are fast, and even the initial import was done
before I knew it. So far so good.
The problems start to arise when dealing with plugins, which I use in
some of my themes. These plugins all have their own folders, which are
located in the "plugins" folder. Now, WordPress has a wonderful system
for handling plugins from the back-end. All you do is click a button,
and WordPress automatically downloads the latest version of the
plugin, unzips it, and places it in the "plugins" folder. Upgrading a
plugin works exactly the same, but in stead of updating the files
inside the plugin folder, it deletes the entire plugin folder
(including that .svn folder) and replaces it with a newly created
folder. Nothing is overwritten. All the system does is delete and
unzip. So I basically lose all of my SVN info, and of course Versions
doesn't let me commit my working copy. What's the best way to get
around this problem? I know that updating all of the plugins manually
is an option, but I'd rather use the plugin system from WordPress
itself.
So, back to the setup of my SVN repository. I've got my entire
WordPress folder under version control. This includes the theme
folders, plugin folders as explained above, and the images folder. The
reason why I do this, is because this way I can upgrade my WordPress
installation on my working copy with one click of a button, and commit
the entire thing back to projectlocker.com.
This works fine for now, but I'm not sure if this is the right way to
do it. After all, the files on projectlocker.com are in a SVN
repository, and they don't offer web hosting. So the website itself is
hosted on a different server. That basically means that every time I
create a new post on my blog, I have to create a working copy,
download the latest post images from my web hosting, save them in the
working copy folder, and commit. Is it even a good idea to get your
post images under version control?
Also, if I edit some of my theme files, I have to commit them and then
upload them from my working copy to my web hosting server. This seems
like a bit of a hassle. Maybe I should consider a hosting provider
with SVN support? Am I doing this all wrong?
I know, a lot of questions, but I'm just looking for some real world
examples of web designers. I'm just getting into all of this stuff so
be gentle :). I didn't know any other place to go besides here and I
don't know if these questions belong here, but if anyone knows a good
place to ask this stuff then please: let me know.
Thnx for the help!
--
You received this message because you are subscribed to the Google Groups
"Versions" group.
To post to this group, send email to versi...@googlegroups.com.
To unsubscribe from this group, send email to
versions+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/versions?hl=en.
