Remove README.md (see Documentation) and move to framasoft/mobilizon

image

Signed-off-by: Thomas Citharel <tcit@tcit.fr>

docker/production/README.md

@@ -1,56 +0,0 @@
-# Build and deploy Mobilizon with docker
-
-You will need to :
-- build the image
-- tune the environment file
-- use docker-compose to run the service
-
-## Build the image
-
-    git clone https://forge.tedomum.net/tedomum/mobilizon
-    cd mobilizon
-    docker build -t mobilizon -f docker/production/Dockerfile .
-
-## Update the env file
-
-    cd docker/production/
-    cp env.template .env
-
-Edit the `.env` content with your own settings.
-More settings can be added in .env, see all in docker-compose.yml file.
-
-You can generate `MOBILIZON_INSTANCE_SECRET_KEY_BASE` and `MOBILIZON_INSTANCE_SECRET_KEY` with:
-
-    gpg --gen-random --armor 1 50
-
-## Run the service
-
-Start by initializing and running the database:
-
-    docker-compose up -d db
-
-Instanciate required Postgres extensions:
-
-    docker-compose exec db psql -U <username>
-    # CREATE EXTENSION pg_trgm;
-    # CREATE EXTENSION unaccent;
-
-Finally, run the application:
-
-    docker-compose up -d mobilizon
-
-A migration will be automatically run before starting Mobilizon (can be run even if no migration is needed without incidence).
-
-## Run a mobilizon_ctl command
-
-    docker-compose exec mobilizon mobilizon_ctl [options]
-
-## Update the service
-
-Pull the latest image, then update the service:
-
-    docker-compose pull mobilizon
-    docker-compose up -d mobilizon
-
-Migration is automatic.
-

docker/production/docker-compose.yml

@@ -2,7 +2,7 @@ version: "3"
 
 services:
   mobilizon:
-    image: mobilizon
+    image: framasoft/mobilizon
     environment:
       - MOBILIZON_INSTANCE_NAME
       - MOBILIZON_INSTANCE_HOST