Using rsync to create two versions of the same software.

[Lisa Kachold]

On Tue, Jun 15, 2010 at 11:51 AM, Bryan O'Neal <
Bryan.ONeal at theonealandassociates.com> wrote:

> I agree SVN for version control, but for available features I just have a
> config file. For java you use a JNDI lookup or parse the XML based config
> file directly or JDBc to your dab based config what ever floats your boat,
> but basically you just set a variable - free = no - and then check the state
> of said var when laying out the site.  Same way you did it in the desktop
> only now you set the session var after cheeking login credentials instead of
> when you compile and distribute the software.
>
>
> On Tue, Jun 15, 2010 at 11:08 AM, Eric Cope <eric.cope at gmail.com> wrote:
>
>> I use SVN for that. Specifically, EXPORT. Then I use a script clean out
>> directories, then pass my PHP through the PHP compiler as a last time double
>> check things compile.
>>
>> Eric
>>
>> On Tue, Jun 15, 2010 at 10:44 AM, keith smith <klsmith2020 at yahoo.com>wrote:
>>
>>>
>>> Hi All,
>>>
>>> In the old days of writing desktop applications, when one wanted to make
>>> two versions of the same app - one free or demo and the other with all the
>>> features, all one had to do was add a switch to include (run) or exclude
>>> (not run) the code to create either version and compile.
>>>
>>> Now that we have interpreted web based applications written in PHP and
>>> the like, this option does not work so well.  I was thinking about this
>>> recently and wondering how to address such an issue with PHP.
>>>
>>> Yesterday while looking at rsync I happened upon a website and read "I
>>> personally use it to synchronize Website trees from staging to production
>>> servers....".
>>>
>>> Then it occurred to me that I can use rsync for building two different
>>> versions of a PHP application.
>>>
>>> I can add that switch to the code and test each version by setting the
>>> switch.  Then I can run rsync to copy each code set to its own directories.
>>>
>>>
>>> The other solution would be to use a compiler.
>>>
>>> I suspect I could use this to upload changes to a production server.
>>> Configuring it to only copy files that have changed.  Interesting idea.
>>> Only down side is any code not ready for production would be uploaded to the
>>> production server as well.
>>>
>>> ------------------------
>>> Keith Smith
>>>
>>
Usually production servers in a PCI compliant network will not allow
scripted scp or rsync - even with keys.
Apache WebDAV required for svn write, and svn 389 are also excluded
generally in such an environment.

Hand based rsync (or scheduled) authenticated ssh push from internal QA
servers - originated from trust to DMZ is generally allowed.

 I doubt that even "expect" will be allowed in most complaint networks to
automate password challenges.

Ideas?

-- 
Office: (480)307-8707
AT&T: (503)754-4452
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.PLUG.phoenix.az.us/pipermail/plug-discuss/attachments/20100621/444aa07a/attachment.html>