Code versus content - your way copies code, the plugin copies content.

On Tue, Sep 29, 2009 at 20:04, Jake Barnes <[email protected]> wrote:
>
> How is this different from
>
> scp -r [email protected]:/path/to/symfony/project/* [email protected]:/path/
> to/symfony/project/
>
> Followed by "symfony cc".
>
> Does it work 2 ways?
>
>
>
>
>
> On Sep 29, 10:19 am, Tom Boutell <[email protected]> wrote:
>> With this handy plugin, you can just type this:
>>
>> ./symfony project:sync-content frontend dev from stag...@staging
>>
>> … And down comes the content from the staging server, beginning with
>> the current state of the database and optionally followed by data
>> folders, such as your uploads folder, search indexes and other data
>> kept in the filesystem rather than the database.
>>
>> You can also push content in the other direction. For instance, the
>> day you launch the production site, you might do this to push content
>> from staging up to production:
>>
>> ./symfony project:sync-content frontend staging to p...@production
>>
>> You can pick up the plugin here:
>>
>> http://www.symfony-project.org/plugins/sfSyncContentPlugin?tab=plugin...
>>
>> For more information about the plugin, check out my new blog post about it:
>>
>> http://window.punkave.com/2009/09/29/sfsynccontentplugin-moving-conte...
>>
>> --
>> Tom Boutell
>> P'unk Avenue
>> 215 755 1330
>> punkave.com
>> window.punkave.com
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to