Would Fredistrano be able to do ALL of this, or only half of it?

[Brendon Kozlowski]

Forgive my lack of understanding, I haven't tried using Subversion in
this context before.

Situation:
I have a live site. I have a local dev machine. The SVN repository
sits on the live site's server (subdomain). I also have SVN installed
locally on the dev machine, but I don't know if it's necessary.

What I'd like to do:
I'd like to sync my live SVN repository to a local dev machine to do
local testing and development/updates. When ready, I'd like to sync
updates back (commit) to the live SVN repository. I would also like
to sync updates from the SVN repository to the live site when ready.
I'd also like to possibly work from multiple locations on the same
repository (multiple dev users?).

Therefore...

I have two site URLs, and two site paths (per user - one live, one
dev). I have one SVN server repository, and a local copy.

From reading over Fredistrano's documentation, it looks like the
expected implementation is to have the SVN server located locally on
the dev machine (or at least on the same server as Fredistrano is
installed on).


...what would be the best way to implement this? Again, sorry for my
lack of common SVN usage. I've only ever used it for simple code
version control, never for syncing to a site.

[euphrate_ylb]

Hi,

Thank you for taking the time to ask us this question. Since the
documentation we have written is quite minimalistic, I may be
difficult to understand precisely how to concretly implement
fredistrano. Therefore, I'll try to answer your question as clearly as
I can.

Basically, the only important constraint with fredistrano is that it
must be installed on the same server as the target live site. In other
words, our application is not yet able to deploy a web application on
a remote server.

That being said, I think you just need one central SVN repository. You
can put this repository anywhere. The only prerequisite is that you,
the other developers and fredistrano must be able to access this
server (SVN protocol/HTTP/File system). Often the SVN repository is
installed on the live web server but it can also be hosted on a
dedicated server like Google code.

Then, each developers simply works on its local working copy. Changes
are commited to the central repository. Afterwards, when the live site
must be updated, you just need to use fredistrano (configured to work
with the cental repository) to apply the expected code modifcations.
As always, developers make use of SVN updates to retrieve the latest
source code from the central repository.

If something is still bothering you, feel free to respond to this
message.

Best reagrds,


Yann Le Blevec

[Brendon Kozlowski]

Thank you, Yann. I believe that answers my question. Although I
would not be able to do exactly what I was planning on doing, it
sounds like what I *should* be doing is actually better anyway. Thank
you again!

I've already recommended Fredistrano to a number of people, but this
is my first attempt at using it myself. I'm sure I'll recommend it to
even more people once I use it!

[Brendon Kozlowski]

I have a clarification question about the documentation. It states,
under 4.1 (Setting up your Project): "Your project must be versionned
with subversion.". Does this mean that I simply need an accessible
repository where the project lies, or that the production web server
must have a folder that is a checkout from that same repository? I
guess what I'm asking is, does any portion of the live web server need
to be a checkout from the repository, or is that where rsync comes in
to play with regard to Fredistrano?

From what I understand right now, nothing needs to be done with the
live site, other than the fact that Fredistrano must be installed on
the same server (with the same user/rights as the live project/
server). Am I correct in this assumption?

Oh yes...also, if I don't know the SVN 'config' directory location, am
I able to leave that blank in the config.php file for Fredistrano, or
will I need to find that out? I use Dreamhost's SVN repository and am
not entirely sure where that would be located.

[fred]

Hi Brendon,

On Apr 15, 6:01 pm, Brendon Kozlowski <Brendon...@hotmail.com> wrote:
> I have a clarification question about the documentation.  It states,
> under 4.1 (Setting up your Project): "Your project must be versionned
> with subversion.".  Does this mean that I simply need an accessible
> repository where the project lies,

Yes, and Fredistrano must be able to reach your repository

or that the production web server
> must have a folder that is a checkout from that same repository?  I
> guess what I'm asking is, does any portion of the live web server need
> to be a checkout from the repository, or is that where rsync comes in
> to play with regard to Fredistrano?
>
> From what I understand right now, nothing needs to be done with the
> live site, other than the fact that Fredistrano must be installed on
> the same server (with the same user/rights as the live project/
> server).  Am I correct in this assumption?

Correct

>
> Oh yes...also, if I don't know the SVN 'config' directory location, am
> I able to leave that blank in the config.php file for Fredistrano, or
> will I need to find that out?  I use Dreamhost's SVN repository and am
> not entirely sure where that would be located.

Subversion 'configDirectory' is optional
in most case you don't need to change it
you can find the full Yann's explanation about this option here =>
http://groups.google.com/group/fredistrano-discuss/msg/3b89d5621b426a83

For information, I use Fredistrano on Dreamhost with success (SVN
repository + live site)

Regards

Frederic Bollon

[Brendon Kozlowski]

Many thanks for your time and hard work, to all of the developers.
Thank you both for answering my questions, ylb and Frederic!