wojciech.kapcia@tigase.net opened 6 years ago
|
|||||
I think this would be task for you Wojciech. |
|||||
%kobit considering that I'm not using Docker and Andrzej is running all his software using it (and also playing a bit with creating docker image of Tigase) I would say he would be better choice… |
|||||
You are a better person for this task, I am certain of it. However, feel free to ask Andrzej for help or suggestions. |
|||||
%wojtek I've committed an initial version of Docker files required to build 4 different versions of Tigase XMPP Server images:
For all images, I've used existing OpenJDK Docker images to make them easier. All of them are based on "slim" versions of those images containing only necessary stuff. I've considered creating some of them for "Alpine Linux" as well, but our startup scripts are incompatible with Alpine (there is no BASH by default). JDK11 images are slightly larger than JDK8 images but I've not found any issues with them (most likely different packages are installed on the base image from OpenJDK). You can build and run those images on your machine having docker installed with the following commands: Tigase 8.0.0 on JDK 8
Tigase 8.0.0 on JDK 11
Tigase 8.1.0-SNAPSHOT (latest) on JDK 8
Tigase 8.1.0-SNAPSHOT (latest) on JDK 11
Dockerfiles are filled with comments to make them easier to understand and use. I've added README.md file as well with the description of parameters provided by those images. I've skipped parameter defined by docker as most of docker users known them already. In the README file and in the examples above I've used |
|||||
Below is an example usage of those images for creating a cluster on the macOS with cluster connections created on the separate inner network (required on macOS). Creating network
|
|||||
A couple of comments and changes I made:
|
|||||
Well,
As for "flattening" I'm not sure if we should do that. What if we would like to introduce new flavors? (ie. new JDK?)
Is groovy working? I'm asking as it requires compiler... |
|||||
"stable" as in "stable release" (i.e. general-availably as opposed to nightly).
Then we can add it as sub-directory if (and when) needed? For example postgres follows this pattern and IMHO it makes sense.
Yes, it does :-) There is one thing I'm slightly concerned about, namely running
Of course NPE will be fixed, but this would be at best 8.1.1. I was thinking that in the startup script we could add a check whether |
|||||
That could work and would be a clean and easy fix for the NPE. |
|||||
NPE fixed and article published on blog (https://tigase.net/tigase-meets-docker/) and social media. |
|||||
Good stuff, both the article and documentation on GitHub. The only minor change I wold suggest is ports description. It would be better to specify that port 5222 is for plain and TLS connections and 5223 is for legacy SSL and the same for other ports. |
|||||
@kobit 5223 is for "legacy SSL" but also for newest (and fastest) DirectTLS |
|||||
Eh, I am sooo not up to date. In such a case it is even more useful to add this info to the docs. |
|||||
@kobit Port list is already there (https://docs.tigase.net/tigase-server/master-snapshot/Administration_Guide/html/#_ports_description) though it lacks proper description for 5223 (DirectTLS). I updated it slightly: https://github.com/tigase/tigase-server/commit/73b9e7d2e8ea2003159144a924507ec59d44dbfc |
|||||
I was talking about README page on GitHub: https://github.com/tigase/tigase-xmpp-server-docker This is the first and usually the only place people look for instructions. |
|||||
But what would you like to include there? explicit mention of DirectTLS? I updated documentation because it said "legacy SSL" for 5223, which was just plain wrong. On github's docker page it says "SSL/TLS connection" which seems ok. |
|||||
In the readme we have this section "Exposing ports". And for 5223 we have "connections over TLS/SSL". For 5222 there is no indication of connection type, so it may leave impression that this is only for plain text connections. So I would just update what we have to something like this:
and so on... I would be even inclined to drop "Plain" option at all from documentation as it may give impression that Tigase is not secure. |
|||||
wojciech.kapcia@tigase.net moved 1 year ago
|
Type |
New Feature
|
Priority |
Blocker
|
Assignee | |
RedmineID |
8675
|
Version |
tigase-server-8.2.0
|
configuration to prepare docker imageconfigure deployment of images/configuration to public repository/repositoriesdocumentation how to use Tigase docker image, including handling configuration and updating installation to newer version.