|
Artur Hefczyc opened 1 decade ago
|
|
|
We need also a wiki page on the Tigase XMPP Server project describing the installation, with information that it is open to everybody for tests. So people can find it and use it if they need/want. |
|
Maybe we should prepare some kind of autorestore system so ie. once every 30 day all data will be cleared to clean installation? This way we would have stable base and all other configuration changes which could create potential issues would be only temporary. |
|
|
This is a good idea, maybe even we could clear the installation on weekly basis and update it after successful nightly build. |
|
Actually this shouldn't be a problem nor much work. |
|
I installed and configured tigase-issue #5.2.0-SNAPSHOT-b3320. Domain names are in place. Registration works for mysql, pgsql, and derby. Getting errors on ldap: 2013-10-08 23:05:23.746 [jabber:iq:register Queue Worker 1] RepositoryAccess.register() SEVERE: Repository access exception. tigase.db.TigaseDBException: Not available This happens with usernames previously added to ldap and non existent users. The user-dn-pattern seems to be off: @ root@tpub ldap/ # ldapsearch -x -LLL -H ldap:/// -b cn=admin,ou=People,dc=ldap,dc=xmpp-test,dc=net No such object (32) Matched DN: ou=People,dc=ldap,dc=xmpp-test,dc=net @ Is our ldap implementation capable of adding users or just authenticating existing users? Any information you can give me here will be helpful. Do we have an external sqlserver? https://projects.tigase.org/projects/private/wiki/tpubxmpp-testnet |
|
|
SQL Server is not available yet |
|
|
Eric, do we still have this server available after moving out form Flosoft? |
|
|
Yes we do. https://projects.tigase.org/projects/servers/wiki/tpubxmpp-testnet There are a few websites running on this server and I'm using it for troubleshooting ldap authentication. |
|
Referenced from commit 1 year ago
|
| Type |
Task
|
| Priority |
Normal
|
| Assignee | |
| RedmineID |
1560
|
Let's have a public Tigase installation solely for experiments. It would be great if we could have it updated automatically after successful nightly build but this is not a critical part.
What we need is an installation with our last compilable code for our own tests and also for tests and experiments for all folks interested to play with XMPP without interrupting our other production systems. This is not for any load or performance tests. So it does not need lots of resources.
What we need:
A VM with 2GB of RAM should be enough
Tigase XMPP Installation running on latest code
Shell access to the Tigase team so anybody can update the server with latest code
The installation should have multiple VHosts, each connecting to a different database:
mysql.xmpp-tests.net for MySQL database
pgsql.xmpp-tests.net for PostgreSQL database
derby.xmpp-tests.net for Derby database
ldap.xmpp-tests.net for LDAP database
sqlserver.xmpp-tests.net for SQL Server database
XMPP User registration open to everybody
Any more suggestions for what else should be configured for the system?