OTRS support for virtual sites
Hi, I'm new to OTRS, and looking at installing it on a CentOS server with Apache (and mod_perl). However, the server is currently hosting numerous websites and e-mail accounts under different domains (i.e. virtual sites), and I would like to provide an OTRS "instance" for each domain. So, for example, foo.com would have a website www.foo.com, and should have its own OTRS "instance" (and associated tickets, users, etc.), whereas bar.com has a website www.bar.com hosted on the same server, and should have its own OTRS "instance". I believe I could achieve this by having multiple installations of OTRS; however, that would then become a nightmare to support with say hundreds of virtual sites running from the same server (an upgrade or patch would have to be applied to hundreds of installations). So what I require is one OTRS installation, with individual config and database for each virtual site. In fact, I don't really mind if there is only one database (this might even be preferable), but the tickets/users etc. of foo.com have to be completely separate (and inaccessible) by bar.com's tickets/users etc. Please could someone advise if this is possible? I have trawled the documentation, web, mailing lists etc. and have not found an answer, let alone any config to achieve it. Thanks in advance, Gary
I don't see why it wouldn't be possible.
Copy the otrs directory elsewhere, edit the config (otrs location, database
details) edit apache config....
If you're worried though, you might want to run virtual private servers....
----- Original Message -----
From: "Gary Sedgwick"
Hi,
I'm new to OTRS, and looking at installing it on a CentOS server with Apache (and mod_perl). However, the server is currently hosting numerous websites and e-mail accounts under different domains (i.e. virtual sites), and I would like to provide an OTRS "instance" for each domain. So, for example, foo.com would have a website www.foo.com, and should have its own OTRS "instance" (and associated tickets, users, etc.), whereas bar.com has a website www.bar.com hosted on the same server, and should have its own OTRS "instance".
I believe I could achieve this by having multiple installations of OTRS; however, that would then become a nightmare to support with say hundreds of virtual sites running from the same server (an upgrade or patch would have to be applied to hundreds of installations). So what I require is one OTRS installation, with individual config and database for each virtual site. In fact, I don't really mind if there is only one database (this might even be preferable), but the tickets/users etc. of foo.com have to be completely separate (and inaccessible) by bar.com's tickets/users etc.
Please could someone advise if this is possible? I have trawled the documentation, web, mailing lists etc. and have not found an answer, let alone any config to achieve it.
Thanks in advance,
Gary _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? => http://www.otrs.com/
Hi,
I'm new to OTRS, and looking at installing it on a CentOS server with Apache (and mod_perl). However, the server is currently hosting numerous websites and e-mail accounts under different domains (i.e. virtual sites), and I would like to provide an OTRS "instance" for each domain. So, for example, foo.com would have a website www.foo.com, and should have its own OTRS "instance" (and associated tickets, users, etc.), whereas bar.com has a website www.bar.com hosted on the same server, and should have its own OTRS "instance".
I believe I could achieve this by having multiple installations of OTRS; however, that would then become a nightmare to support with say hundreds of virtual sites running from the same server (an upgrade or patch would have to be applied to hundreds of installations). So what I require is one OTRS installation, with individual config and database for each virtual site. In fact, I don't really mind if there is only one database (this might even be preferable), but the tickets/users etc. of foo.com have to be completely separate (and inaccessible) by bar.com's tickets/users etc.
Please could someone advise if this is possible? I have trawled the documentation, web, mailing lists etc. and have not found an answer, let alone any config to achieve it.
Could this be better done with some advanced ACL's and groupings in OTRS? ie. one admin (you) to group agents, customers, etc into specific groups so no one group can see another with permission. I use software which does this for mail filtering etc and it works fine. My guess is a little OTRS coding will need to take place to support such a thing though. Personally I'd like to see it happen as I could use that type of functionality. Regards, Michael.
Thanks in advance,
Gary _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? => http://www.otrs.com/ ------- End of Original Message -------
participants (3)
-
Gary Sedgwick -
Michael Mansour -
Ryan Meyer