Instiki is great as a general-purpose CMS (Content Management System). Using a Wiki as CMS makes a lot of sense. Among other things, it’s very easy to create and edit pages.
The key to using Instiki as CMS is the
/published/ URLs. For example if you are running Instiki at
mywiki is the Web name), Instiki will have a “published” version at
if you turn it on in the Edit Web page. Try it!
is not a very nice-looking URL. And you can only access it locally. To use Instiki for your website with and mod_proxy, create two
VirtualHost sections in your Apache config file:
<Virtualhost *> ServerName edit.mysite.org ProxyPass / ProxyPassReverse / </Virtualhost> <Virtualhost *> ServerName mysite.org ServerAlias www.mysite.org ProxyPass / ProxyPassReverse / </Virtualhost>
If you have non-wiki content on the same site, you don’t need a separate host name; if you’d prefer to use a subdirectory for publishing, do this:
Jasa seo Profesional , Harga Vertical Blind , Sewa Mobil Jakarta
<Virtualhost *> ServerName mysite.org ServerAlias www.mysite.org ProxyPass /subdir/ ProxyPassReverse /subdir/ </Virtualhost>
You can now access
to edit your site (remember to set a password!) and
to access it. It should have a layout that lacks the Wiki navigation bar with the search button.
Apache will then proxy requests to the appropriate Instiki server. Remember that Apache is only acting as a proxy: You still need to run Instiki from