Added by Takeo Sato over 10 years ago
For small organizations and for improved integration, wouldn’t it be helpful if the same OpenProject instance could serve both internal and external purposes?
I’d love to see an easy-to-configure option whereby you can:
- Deploy openproject.example.com, with your usual projects, wiki, etc.
- Allow public access to the same server via an alternate host name like wiki.example.com, that exposes only the public wiki documents, with a custom home page just for this public access system
In this way, OpenProject could replace three different systems: project management, private documentation repository (e.g. SharePoint) and public wiki system (e.g. MediaWiki).
By easy-to-configure I mean just a couple of simple questions, like active or not, alternate access URL, etc. This would then take care of the appropriate web server setup (adding alternate host name, rewrite if necessary, etc.)
As per another post, I’d further like nice, user-friendly URLs for the public side.
In MediaWiki style these could be:
- wiki.example.com/Document_title
In WordPress style these could be:
- wiki.example.com/document-title
Replies (1)
+1
My colleague just ask me if the wiki could be made public, to allow our customers to see FAQ, troubleshooting… This implies that there should be an access control set per project / per user / per module.
Non an easy task.
I don’t think this is the first feature to develop, openproject is a bit too far from this.