Leyne, Sean wrote:

> Sure, if that is a real problem which matters to the developers.
>
> But the larger/real problem is in deploying the software that developers
> create which is the true problem.
>

Sean, do you actually have a problem? If so, what is it?

Vulcan was designed to support multiple engine providers without any
need for a user to tailor anything. The installation provides a
configuration file for the provider with appropriate lock file names,
the dispatch modules matches a connection to an engine, and that's the
end of it.

> I have 10 developers, who are each able to handle changing IP port or
> server names, not exactly rocket science. But, I have 40 deployments
> which need to support!
>
>

Then, post-Vulcan, you'll have to find something else for your
developers to do.

Look, I hate administration. You have 10 developers. I have me, Ann,
and Wryly. Wryly is a really bad system administrator, but more willing
to do than Ann. That leaves me, and I hate. So I designed the thing so
it doesn't need administration.. Period.

If you need something for your developers to do during the time that
don't need to change IP ports, client software, or server names, let me
know, and I think of some useful projects for them to do.