| Author |
Message |
|
| Guest |
 Posted: Wed Feb 28, 2007 4:30 pm |
 |
|
|
Guest
|
Hi,
is it possible to deploy ejabberd on multiply domains having
PostgreSQL as a backend? As I see here, SQL shema does not provide
"host" part of JID, so users can authenticate and see their roster on
any domain, which obviously is wrong.
--
Patryk Szczyg |
|
|
| Back to top |
|
| Guest |
| Posted: Wed Feb 28, 2007 10:17 pm |
|
|
|
Guest
|
Patryk Szczyg?owski wrote:
> Hi,
>
> is it possible to deploy ejabberd on multiply domains having
> PostgreSQL as a backend? As I see here, SQL shema does not provide
> "host" part of JID, so users can authenticate and see their roster on
> any domain, which obviously is wrong.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ejabberd mailing list
> ejabberd@jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd
I don't get the question at all! But i have some domains in my ejabberd
server using pgsql external auth.
I'm using external auth because of the problem of the pgsql internal
backend (SQL shema does not provide "host" part of JID)
I'm using a single database for all domains. And the my user's roster is
in Mnesia.
--
-----------------------------------------------
Manuel Mely P |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Mar 01, 2007 8:09 am |
|
|
|
Guest
|
Hello,
Le 28 févr. 07 à 17:30, Patryk Szczygłowski a écrit :
Quote: Hi,
is it possible to deploy ejabberd on multiply domains having
PostgreSQL as a backend? As I see here, SQL shema does not provide
"host" part of JID, so users can authenticate and see their roster on
any domain, which obviously is wrong.
It is not wrong. The philosophy is to have one DB per virtual host. This work perfectly well.
--
Mickaël Rémond
http://www.process-one.net/
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Mar 01, 2007 1:49 pm |
|
|
|
Guest
|
Ok, but most of the people that are trying to deploy ejabberd server
using pgsql as a backend have a custom DB that it is used by other
services as mail.
It will be interesting to modify the pgsql module to have the ability
of specify what fields we are going to use for authentication, as well
as use the JID=email for auth.
Greetings
PS: sorry for my english
On 3/1/07, Mickaël Rémond <mickael.remond@process-one.net> wrote:
> Hello,
>
>
> Le 28 févr. 07 à 17:30, Patryk Szczygłowski a écrit :
>
> Hi,
>
> is it possible to deploy ejabberd on multiply domains having
> PostgreSQL as a backend? As I see here, SQL shema does not provide
> "host" part of JID, so users can authenticate and see their roster on
> any domain, which obviously is wrong.
>
> It is not wrong. The philosophy is to have one DB per virtual host. This
> work perfectly well.
>
> --
> Mickaël Rémond
> http://www.process-one.net/
>
>
> _______________________________________________
> ejabberd mailing list
> ejabberd@jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd
>
>
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Mar 01, 2007 4:13 pm |
|
|
|
Guest
|
|
| Back to top |
|
| Guest |
| Posted: Thu Mar 01, 2007 6:51 pm |
|
|
|
Guest
|
On 3/1/07, Mickaël Rémond <mickael.remond@process-one.net> wrote:
> Hello,
>
>
> Le 1 mars 07 à 14:49, Manuel Mely a écrit :
>
> Ok, but most of the people that are trying to deploy ejabberd server
> using pgsql as a backend have a custom DB that it is used by other
> services as mail.
>
> It will be interesting to modify the pgsql module to have the ability
> of specify what fields we are going to use for authentication, as well
> as use the JID=email for auth.
>
> It depends. Some company providing hosting are willing to use separate
> database. This way, if a site becomes big, they can make move it to another
> machine, without having to change, move split the database.
You're right, but it shouldn't make much difference to include "host"
field. If company wants to keep each domain in it's own database,
"host" field will just contain single value. If they want to do mass
domain hosting, creating, for example, 10000 databases, is shooting
your own foot.
--
Patryk Szczygłowski
patryk.szczyglowski//gmail.com
JID: psz//chrome.pl
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Mar 01, 2007 6:59 pm |
|
|
|
Guest
|
|
| Back to top |
|
| Guest |
| Posted: Fri Mar 02, 2007 7:45 am |
|
|
|
Guest
|
Hello,
Le 1 mars 07 à 19:51, Patryk Szczygłowski a écrit :
Quote: You're right, but it shouldn't make much difference to include "host"
field. If company wants to keep each domain in it's own database,
"host" field will just contain single value. If they want to do mass
domain hosting, creating, for example, 10000 databases, is shooting
your own foot.
Yes, but there is some change anyway to do in internal data structure to do mass domain hosting. You can not do mass virtual hosting with ejabberd as is.
--
Mickaël Rémond
http://www.process-one.net/
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Fri Mar 02, 2007 2:55 pm |
|
|
|
Guest
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
