<HTML>
<HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
Actually, using that logic - you could put both CMS into separate user "personal webs". User1 and User2, and make sure neither is a "site admin" - they wouldn't be able to see each other's files/CMS. That takes care of security.
<br />
<br />But how do you handle http requests and point them to the right directory/CMS? You'd have to create some type of home page (maybe using PHP) in the main site /web directory that would point requests to the proper CMS based on visitor selection.
<br />
<br />That would force visitors to select when they hit the main page, because the system would have no way of telling which company's site a visitor is requesting (since they have a single domain). A bit ugly - but it would work.
<br />
<br />And that could entail some long-term management, updating yourself. Since neither company would have access to that "home" or "selection" page - you'd have to do any updates/changes. Remember, if you give either company "admin" rights to be able to modify that home/selection page - they'd be able to see the other company's CMS. So you'd get to do it. That could either be considered long-term PIA if you're not paid for it, or long-term job security if you bill them for the time!!
<br />
<br />
<br />
<br />Chuck
<br />
<br />
<br />
<br /><font size="2"><b>---------- Original Message
-----------</b>
<br />
From: Arbalister <arbalister@gmail.com>
<br />
To: BlueOnyx General Mailing List <blueonyx@mail.blueonyx.it>
<br />
Sent: Fri, 27 Jan 2012 14:22:33 -0500
<br />
Subject: [BlueOnyx:09454] Re: 2 CMS-Systems on one webspace
<br />
<br />> Chuck - *could* put the second CMS into a user subfolder... <a href="http://www.somedomain.com/~user2.">www.somedomain.com/~user2.</a>.. and
only give the user rights, rather then siteadmin. But...that's a messy
kludge.
<br />>
<br />> Other then that... create 2 sites <a href="http://www.somesite.com/">www.somesite.com</a> and www2.somesite.com...
which is also a kludge..
<br />>
<br />> On Fri, Jan 27, 2012 at 1:48 PM,
Chuck Tetlow <span dir="ltr"><<a href="mailto:chuck@tetlow.net">chuck@tetlow.net</a>></span> wrote:
<br />>
<blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
<br />>
Yes, you can run multiple CMS's on one site. Just put them into uniquely
named directories under /web. The url might be <a target="_blank" href="http://www.domain.com/joomla">www.domain.com/joomla</a>,
<a target="_blank" href="http://www.domain.com/wordpress">www.domain.com/wordpress</a>, and <a target="_blank" href="http://www.domain.com/cms">www.domain.com/cms</a>.
I've done that under one site when multiple people were learning CMSs and
wanted to play with their own
installation.
<br />>
<br />> BUT! You've got a bigger
problem.
<br />>
<br />> If you have two companies that both won't accept the other
accessing their webspace - you can't have one domain. That's plain and
simple - it can't be done security-wise.
<br />>
<br />> Any FTP user created in a site/domain will have access to just
their home directory. If made a "site admin", they'll gain access
to the whole website, including the site's /web directory. But you
can't split up the /web directory and give one "site admin" FTP
user access to one half while no access to the other
half.
<br />>
<br />> Sounds like its time for a second domain - and they can fight
over who gets the original name. Because I don't think your reverse proxy
idea will work either. How would you set up the proxy to "combine"
the
sites??
<br />>
<br />>
Chuck
<br />>
<br />> <font>
<br />>
<br />> <b>---------- Original Message
-----------</b>
<br />>
From: Klein Joachim <<a target="_blank" href="mailto:j.klein@ibusiness.at">j.klein@ibusiness.at</a>>
<br />>
To: BlueOnyx General Mailing List <<a target="_blank" href="mailto:blueonyx@mail.blueonyx.it">blueonyx@mail.blueonyx.it</a>>
<br />>
Sent: Fri, 27 Jan 2012 16:16:13 +0100
<br />>
Subject: [BlueOnyx:09451] 2 CMS-Systems on one webspace
<br />>
<br />> > Hy to the list!
<br />> >
<br />> >
I have the following request:
<br />> >
A customer wants that on one webspace should exists two different
<br />> >
CMS-Systems.
<br />> >
I think the blueonyx can handle it, but the systems are managed between two
<br />> >
different companys and the shouldn´t get access for the other system.
<br />> >
Also both wants to use the same domain and no sudomain (like www2).
<br />> >
<br />> >
<a target="_blank" href="http://www.domain.com/">www.domain.com</a>
<br />> >
/cms1 -> FTP-User 1
<br />> >
/cms2 -> FTP-User 2
<br />> >
<br />> >
SuPHP is enabled because of the security and then also Userwebs are
<br />> >
disabled.
<br />> >
<br />> >
For now I have only one Idea to get this thing running:
<br />> >
Take two websites (cms1 and cms2) and then take a reverse Proxy and
<br />> >
combine this two.
<br />> >
<br />> >
Have anyone another idea - or simplier???
<br />> >
Thanks
<br />> >
Joachim
<br />> >
<br />> >
_______________________________________________
<br />> >
Blueonyx mailing list
<br />> >
<a target="_blank" href="mailto:Blueonyx@mail.blueonyx.it">Blueonyx@mail.blueonyx.it</a>
<br />> >
<a target="_blank" href="http://mail.blueonyx.it/mailman/listinfo/blueonyx">http://mail.blueonyx.it/mailman/listinfo/blueonyx</a>
<br />> <b>------- End of Original Message
-------</b>
<br />>
</font>
<br />> _______________________________________________
<br />>
Blueonyx mailing list
<br />>
<a href="mailto:Blueonyx@mail.blueonyx.it">Blueonyx@mail.blueonyx.it</a>
<br />>
<a target="_blank" href="http://mail.blueonyx.it/mailman/listinfo/blueonyx">http://mail.blueonyx.it/mailman/listinfo/blueonyx</a>
<br />>
<br />> </blockquote>
<br /><b>------- End of Original Message
-------</b>
<br />
</font>
</BODY>
</HTML>