|
Hi Sulka,
Thank you for the suggestion, it sounds good. We will keep this in mind when working on this feature. Regards I agree with Sulka,
This is exactly what I am looking for. Rather than set up a new base for each group, many of whom want just their own area, eg space, can have a virtual host. Combined with Builder to configure the layout, it makes for an easy administrative exersise. Yes,
we run on the same issue. Each research group want an unique "identity", something like <research group name>.<our university>.ca mapped to their confluence space, without reinstalling or administrating a separate Confluence installation. Virtual hosting on Confluence with Builder will be a very simple and a killer app! The company I'm working for would certainly benefit from Sulka's solution. We have several websites with junctions to one Confluence installation. In the current situation we can use RSS-feeds for only one of our websites because there is only one server base-url.
It's hard to explain to our users that such a limitation exists. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This would allow for a lot of flexibility in configuring Confluence for uses which currently aren't possible (namely, containing multiple projects which shouldn't need to know about each other).