confluence usage with a subdomain

[Serkan Sevim]

Hello,

We would like to setup confluence as a public knowledge base and also as an internal document repo.

Is it possible to set it up as for example docs.ourcompany.com, for the public to see and also have another subdomain internaldocs.ourcompany.com which is restricted for internal use only.

Thank you,

[Tom Rough]

Hi Serkan, 

We offer an app which may suit your needs – Scroll Viewport. 

In short, the app provides you with an option for having an alternative view for your Confluence content, which you can deliver to the web. This means you could have a public knowledge base available via a Viewport, whilst also keeping your other spaces (or content) inaccessible, for internal use only.  

Once you have activated a Viewport within your space, it is available at a configurable URL and uses themes to output the content. This means that you can configure the look and feel as you require. Would this be an option for you?

Should you want to find out further information please see our Atlassian Marketplace listing. Additionally, you can also choose to trial the app.

Let me know what you think. 

Thanks, Thomas (K15t Software) 

[Nic Brough -Adaptavist-]

There are ways to do it, but it won't work.

Confluence needs to be given one single base url to run on.  If you set up your network to expose it on two different urls, then users using one of them (the one that is not set as the base url) will have problems with it.

Use the external url as the base url and have everyone use that.  Then split up your docs into different spaces, allowing external users access to a limited set of those spaces.