New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review production ready docker setup of tine20 all-in-one #6993

Open
talsen-team opened this Issue Feb 8, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@talsen-team
Copy link

talsen-team commented Feb 8, 2019

Hi tine20 community,

We are currently running a natively installed tine20 community edition (installed via apt-get).
Due to several reasons (migratability, maintainability, an easier update to newer versions and an easy backup of persisted data) I prepared a docker ready setup of tine20 community edition.

what the setup contains

The setup contains the tine20-all-in-one package, the inventory package and the human-resources package from your latest release 2018.08.9. Apache2 is preconfigured for http access at http://localhost.

what the setup does

During docker image build those three mentioned packages (the *.tar.bz2 ones) are automatically fetched, the sha1sum is verified and extracted (to /usr/share/tine20).

The written setup used both, the official install guide as well as the apt-get installation as reference.

Apache2 is used as web server inside docker (like the apt-get setup provides), furthermore mysql is directly installed into the docker image as well.

So it should be easy to get things up and running.

why not use apt-get in docker setup?

Sadly the apt-get setup requires the mysql database to be existent.
During build time this is quite unfortunate, because the database configuration would be hard-coded into the dockerfile (including mysql passwords).
So the setup does not use apt-get install tine20 at all.

what the docker compose configuration contains

Before starting the container several things can be configured.
Host specific settings can be set in the host.env file.
Container specific settings (like usernames, passwords, the server name and the timezone to use) can be set via the container.env file.

how to use

Install the requirements described in the repo description (preferably) into a clean Ubuntu Bionic Desktop VM and clone the repository to some place using git clone https://github.com/talsen-team/docker-app--tine20.git --recurse-submodules.
Then open the clone directory with VS Code.

Afterwards you can build the image locally, by just executing the custom VS Code task docker-compose--compose--up (which requires the talsenteam/docker-tine20:v2018.08.9 image to exist).
If you want to use the pre-built image from docker hub just comment the lines 5 to 7 of the default.docker-compose file before executing the task docker-compose--compose--up.

my request

Can you please review the docker setup for correctness, it would be nice to use tine20 soon via docker :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment