All,

is it a good idea to restructure the server a bit?

I'd like to have:
 - builds.wicketstuff.org
 - repo.wicketstuff.org
 - snapshots.wicketstuff.org
 - issues.wicketstuff.org
 - wiki.wicketstuff.org
 - examples.wicketstuff.org

I'd like to be able to have multiple containers running on the box, so
we can restart for example the wicket examples without having to
restart the builds/issues/confluence instance.

We could set repo.wicketstuff.org up so that it syncs with the central
repository.

So I'd like the following containers running:
 - builds/jira/confluence/maven repo
 - examples
 - mini containers for small production type of apps, such as wicket
bot, teatime, etc.

I don't have root access, and I'm not that experienced in setting such
a thing up, but I am willing to learn.

Martijn

-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3

Reply via email to