Dev-Live Setup Practices?

[Indy]

Hi guys... I have another question. Hope someone has faced this and
can suggest an approach.

I have a dev environment on a dev/staging box where I'm creating
layouts/snippets/pages etc.

I have a live environment on another server where I need to move these
changes across. However, the live environment will have the real
content for the site (pages)

Both servers push/pull from a shared git repo, and I'm using the
standard .gitignore that ships with Splash so that stuff in layouts/
snippets etc. doesn't get checked in.

Any thoughts on how best can I streamline this workflow?

Currently I'm doing creating layouts/snippets on dev, and then
recreating them on live, and then apply to the pages created in live
-- which is not the most elegant way!

Would really like to hear if your thoughts on this.

Indy

[raulriera]

Removing the gitignore would be nice.. although an enhancement request
to keep the same file names would be nice... so Splash doesnt do
CreateUUID on every update

[Russ Johnson]

Remember, one of the reasons for creating new UUID's and files was the first step in having multiple versions and saving your revision history of the files.

I think we could make the change and still allow it to keep the same file names but also store multiple revisions as well.

- Russ