Begin to remove CI

pica-tls-certs-monitor/README.md

@@ -28,4 +28,4 @@ On a choisi une bonne fois pour toutes `/DATA/docker/certs` comme dossier de sto
 
 ## Mise à jour
 
-Il suffit de mettre à jour la variable d'environnement `TLS_CERTS_MONITOR_VERSION` dans le Dockerfile, quand une nouvelle release (tag) apparaît sur le dépôt.
+Il suffit de mettre à jour la variable d'environnement `TLS_CERTS_MONITOR_VERSION` dans le Dockerfile, quand une nouvelle release (tag) apparaît sur le dépôt, ainsi que le numéro de version de l'image dans Compose.

pica-tls-certs-monitor/clair-whitelist.yml

-generalwhitelist:

pica-tls-certs-monitor/docker-compose.yml

@@ -3,6 +3,7 @@ version: '3.7'
 services:
   tls-certs-monitor:
     image: registry.picasoft.net/pica-tls-certs-monitor:v1.5
+    build: .
     container_name: tls-certs-monitor
     volumes:
       - /DATA/docker/traefik/certs/acme.json:/certs/acme.json

pica-wekan/docker-compose.yml

@@ -10,7 +10,8 @@ networks:
 services:
 
   wekan-app:
-    image: pica-wekan:2.75
+    image: registry.picasoft.net/pica-wekan:2.75
+    build: .
     container_name: wekan-app
     restart: always
     links:

template/README.md

@@ -6,7 +6,7 @@ In this README, you should explain, if applicable, the following :
 * How to configure (secrets, environment variables...)
 * How to start (usually just a `docker-compose up -d` and copying the secret files : this is the goal)
 * How to update the service itself (usually just changing a tag in the Docker Compose file and an argument in the Dockerfile)
-* How to update the customization of the service : add more environment variables, change configurtion, etc.
+* How to update the customization of the service : add more environment variables, change configuration, etc.
 * How to administrate the service (e.g. CLI tool)
 * Warnings about breaking changes (e.g. "you cannot update the database to a major version without doing this or that")
 
@@ -14,4 +14,4 @@ And everything that you find useful.
 
 This README should act as a reference for all administration tasks.
 
-However it should not contain user documentation, nor general advices about how to resolve build errors and so on (this is the job of the CI documentation).
+However it should not contain user documentation, nor general advices about how to resolve build errors and so on.

template/clair-whitelist.yml

-# Put all CVE as sub-keys
-# The format is :
-#  CVE-XXX-XXX: <paquet name> -> <reason>
-generalwhitelist:

template/docker-compose.yml

@@ -30,9 +30,15 @@ services:
   # Main application
   app:
     # This is the name of the image
-    # which will be built on the registry
+    # which will be built and pushed on the registry
     # Never use latest as a tag
-    image: registry.picasoft.net/<image>:<tag>
+    image: registry.picasoft.net/pica-<service>:<tag>
+    # When using a local Dockerfile,
+    # add this directive so that then `docker-compose build`
+    # command works. See other options here
+    # (such as using an alternate Dockerfile) :
+    # https://docs.docker.com/compose/compose-file/#build
+    build: .
     # Use a comprehensive name for easy
     # understanding of `docker ps` output
     container_name: app
@@ -80,8 +86,10 @@ services:
     restart: unless-stopped
 
   # Some services have a database : here is an example
+  # Here is could be postgres:12. We do not build it manually,
+  # so no need for `build` key nor registry.picasoft.net prefix.
   db:
-    image: registry.picasoft.net/<image>:<tag>
+    image: <image>:<tag>
     container_name: db
     # Database secrets should be in a separate file
     env_file: