wojciech.kapcia@tigase.net opened 6 months ago
|
|||||||
wojciech.kapcia@tigase.net changed state to 'In Progress' 6 months ago
|
|||||||
Referenced from commit 5 months ago
|
|||||||
Referenced from commit 5 months ago
|
|||||||
Referenced from commit 5 months ago
|
|||||||
wojciech.kapcia@tigase.net changed state to 'In QA' 5 months ago
|
|||||||
I added docker compose documentation to our main distribution repository (tigase-server now) under dedicated docker directory with docker-compose.yaml file: https://tigase.dev/tigase/_server/tigase-server/~files/master/src/main/docker/README.md (linked from main page) and updated our docker hub page: https://hub.docker.com/r/tigase/tigase-xmpp-server I also updated the TURN/STUN guilde: https://tigase.org/blog/tigase-server-with-stun-turn/ (While updating the guide I had to add 1dev build job so the site would be automatically updated and fixed a couple of issues with permissions) |
|||||||
wojciech.kapcia@tigase.net changed fields 5 months ago
|
|||||||
This allowed me to create and run docker compose environment with def settings. Except I used " However, in the configuration wizard I was not able to setup the system. I got stuck on DB. I selected MySQL and provided host, root user, pass from the yaml file (would be nice for the configurator to automatically pickup these settings from env if possible).
But clicking next, leads to an empty page with: |
|||||||
I also tested |
|||||||
I think the ticket can be closed now. |
|||||||
Works like a dream. Looking forward to test the 8.4 with the new dashboard. |
|||||||
wojciech.kapcia@tigase.net added "Related" tigase/_server/tigase-http-api#142 5 months ago
|
|||||||
It's planned: https://tigase.dev/tigase/_server/tigase-http-api/~issues/142, I think I should be able to add it soon as part of 8.4 release. The idea is to have "next-next-next" setup experience without having to change too much and get the system up and running.
Did you happen to get the whole stacktrace (it should be in the container logs)? |
|||||||
wojciech.kapcia@tigase.net changed state to 'Closed' 5 months ago
|
|||||||
I do not have any stackrace but I could recreate the problem if necessary. Let me know when the version 8.4 is working, I would like to see and test the new dashboard. |
|||||||
No need - while working on the env I got the stacktrace. |
|||||||
wojciech.kapcia@tigase.net added "Related" tigase/_server/tigase-server#22 5 months ago
|
|||||||
@kobit There were a couple of issues to fix but I think I squashed all of them so now getting latest |
|||||||
Did you mean Also, is the installer available on |
|||||||
In general Tigase http server binds to all ports so you can access it via any hostname/IP that points to it |
|||||||
Btw. @kobit I was pondering - given leaning more towards using docker and docker compose maybe we could drop (in version 9.0) Derby support? I think noone is using it and it gives little to no benefit for us (we already use docker for any testing so it's very easy to get up and running without any conflicts). Maybe we could switch default in docker-compose to postgres, which should be lighter than mysql even? |
|||||||
Yes, I agree, good idea. |
|||||||
I meant dropping Derby support. |
|||||||
I have just tried nightly and it still does not work as expected. My guess is that nightly is still the old version without your recent changes. |
|||||||
Created https://tigase.dev/tigase/_server/server-core/~issues/1526
Have you run
as well as http-api component version:
|
|||||||
wojciech.kapcia@tigase.net added "Related" tigase/_server/server-core#1526 5 months ago
|
|||||||
I removed all the previous images and now it The only, small, concern is with the DB schema creation. It takes some time, like a minute or so. And after clicking |
|||||||
Great. Btw. I was thinking whether we shouldn't use postgres by default (especially in the "tiny fast deployment" kinda scenario) as it should use less resources.... (~500M vs ~85M) mysql:
postgres:
Weird... It takes like 2-3s on my machines.
Do you use native images or maybe wrong platform and emulation is used? How long it takes for Tigase to start?
We could add a notice/info/warning on DB configuration page that installation may take a while and page should not be refreshed/reloaded - that should be quite simple and easy to add (as opposed to page with progress) |
|||||||
Referenced from commit 5 months ago
|
|||||||
@kobit I added notice/info to the web-installer |
|||||||
Sure, in such a case I am in favor of using postgresql instead of mysql. This is kind of strange, I was always under impression that mysql is the DB with little resources requirements. 0.5GB RAM for such a small setup seems really excessive. I am running the setup on my NAS. But this is really powerful setup - Intel Core i7-7700 3.6 GHz, 64GB RAM. I do not have any performance issues with anything on it. Maybe loading schema to postgresql would be faster? Maybe there is some issue with resources limits which slows down mysql? In any case, after loading schema all works fine, so it does not concern me much. |
|||||||
Just tested the latest nightly. The added working is good, and enough. This time schema loaded within a few seconds. To sum it up. I consider the task finished and fully working, you can close the issue if there is nothing else to do. |
|||||||
As for the PostgreSQL, I understand that we can simply have docker compose for MySQL and another one for PostgreSQL? |
|||||||
Maybe in the past it required less resources but AFAIR for a while now PostgreSQL is considered as more efficient... However I did quick digging and from https://www.startechup.com/blog/postgresql-vs-mysql/ I get:
Yes. We can have both: just distinct files like I think the most sensible option would be having two compose files: |
|||||||
Ok, we have a working docker compose and it works very well. And, additional versions or options are not a priority right now. I leave it to you to decide whether you want to spend some more time on this or close the issue. TBH, for the use-case like mine I do not need many DB connections, so probably postgresql with just few DB connections would work well enough, saving memory. But, the current MySQL option works well enough. |
|||||||
Referenced from commit 4 months ago
|
|||||||
In the end I switched the default to postgresql and created alternative |
Type |
Task
|
Priority |
Normal
|
Assignee | |
Version |
none
|
Target Release |
1.0
|
Sprints |
n/a
|
Customer |
n/a
|
Include docker-compose example (on hub and in repo) for fast, nice and easy setting up Tigase