moviplus/synthese-front-pod Docker 镜像 - 轩辕镜像 | Docker 镜像高效稳定拉取服务

Synthese Front Pod

Docker image(s) and script to generate a Kubernetes Pod usable as a FRONT instance.

This image adds some configuration and script to the Synthese image to integrate it in a Synthese POD.

This was intended for the SaaS project.

A Synthese front pod is intended to be used as a throwable replica of a source instance. The source instance must have a pre-defined inter-Synthese flux that the pod will use to register itself on its source. A MariaDB sidecar is used to store Synthese data.

To register itself, an user token on the source is used.

Requirement

The Synthese image is based on moviplus/synthese, and so the login to the private Moviplus registry must be made :

docker login moviplus 

The password is in Bitwarden.

Build

Simply with :

docker pull moviplus/synthese:latest
docker build --no-cache ./ -t YOUR-TAG

By default, the latest synthese version is used. To change this, change the FROM line from the Dockerfile.

Commit to docker registry

The new image must be tagged correctly using the format : synthese-front-pod:SYNTHESE_VERSION-IMAGE_VERSION where :

• SYNTHESE_VERSION corresponds to the Synthese version

• IMAGE_VERSION corresponds to the image version, in case that the scripts hve changed but the synthese version did not. Restart at 1 at each new synthese version.

  docker tag YOUR-TAG moviplus/synthese-front-pod:VERSION docker push moviplus/synthese-front-pod:VERSION

The Synthese version can be found using the following command :

docker run --rm moviplus/synthese:latest --version | grep -o '3\......'

Lifecycle

At start the Synthese instance will be launched using the defined (and usually empty) database.

The /opt/synthese-pod/entrypoint.sh script is used as the Docker entrypoint to create an inter-Synthese flux client on the source and a related import in the pod and then start Synthese

Pre/post import SQL scripts

If SQL scripts are found in the /opt/synthese-pod/sql-pre.d or /opt/synthese-pod/sql-post.d directories that end in .sql, they will be executed against the Synthese database respectively before and after the source database import, but always after the default sql script.

Pre/post start Synthese scripts

If an executable file (bash, python, etc) is found in the /opt/synthese-pod/script-pre.d or /opt/synthese-pod/script-post.d directories, they will be executed respectively before and after Synthese is started (but after the database has been setup).

If a pre start script fails (return an exit code above 0), the entrypoint will also stop there.

Parameters

All the parameters are described in the [config file]{config}.

Most of them can be left to their default, by each can be set through environment variables.

The config file in /etc/config is used by the script to define all the default parameters.

Note : The CLIENT_NAME parameter has to be set to an unique value among the pods connected to the same source.

All the container parameters (given after the tag) are directly given to Synthese

For example, to run the images with a different Synthese source, flux and token :

docker run --rm -it -e "SOURCE=172.17.0.1" -e "SOURCE_PORT=8081" -e "SOURCE_SID=XXXXX" -e "FLUX=XXX" -e "CLIENT_NAME=test" moviplus/synthese-front-pod:latest [synthese parameters...]

Synthese source instance

For this pod to work, a source has to be created with :

• A user with a fixed token that has the rights to create and remove an inter-Synthese flux client
• A flux fully defined that will contain all the necessary data