[DGD] Managing a persistent mud.

[Gary]

On 29/08/15 15:39, bart at wotf.org wrote:
> 
> So, I strongly suggest to reconsider the idea of allowing live edits on a
> persistent mud, in my experience it causes way more trouble and work then
> teaching your would-be coders to work on a development copy and to follow a
> more controlled change management process.
> 

The more I've dug into this, the more I've been coming to the same
conclusion as you. I really don't want to lose the traditional
develop/test/merge into stable and deploy approach but at the same time
wanted to be sure I'd not overlooked some method current muds were using
to overcome the issue.

Whilst allowing guest builders a way to introduce new code for their
regions is appealing, there's going to be a number of issues with it
beyond the current deployment one that are making me think requiring all
submissions go via the develop git repo would be wiser/safer.

May I ask what method you use for pushing changes after testing to your
live server? I was thinking of either rsync (with suitable excludes to
avoid deletion of server side generated files) or git with suitable
ignore files.

Cheers,

Gary