Merge pull request #1398 from opengisch/QF-6830-detault-development

chore: change the default ENVIRONMENT from test to development

Author: suricactus

.env.example

@@ -14,10 +14,9 @@ DEBUG=1
 QFIELDCLOUD_HOST=localhost
 
 # Environment where QFieldCloud runs
-# NOTE: the default value `test` is used to minimize changes required to run tests. Please change accordingly.
 # VALUES: `development` - local development; `staging` - staging server; `test` - tests; `production` - production server
-# DEFAULT: test
-ENVIRONMENT=test
+# DEFAULT: development
+ENVIRONMENT=development
 
 
 ######################

.github/workflows/test.yml

@@ -62,6 +62,7 @@ jobs:
       - name: Export the env variables file
         run: |
           cp .env.example .env
+          sed -ri 's/^ENVIRONMENT=(.*)/ENVIRONMENT=test/g' .env
           sed -ri 's/^COMPOSE_FILE=(.*)/COMPOSE_FILE=\1:docker-compose.override.test.yml/g' .env
           eval $(egrep "^[^#;]" .env | xargs -d'\n' -n1 | sed -E 's/(\w+)=(.*)/export \1='"'"'\2'"'"'/g')
 

README.md

@@ -49,13 +49,8 @@ To fetch upstream development, don't forget to update the submodules too:
 cp .env.example .env
 ```
 
-2. Change the `ENVIRONMENT` variable to `development`.
 
-```shell
-ENVIRONMENT=development
-```
-
-3. Build development images and run the containers:
+2. Build development images and run the containers:
 
 ```shell
 docker compose up -d --build
@@ -64,31 +59,31 @@ docker compose up -d --build
 The command will read the `docker-compose*.yml` files specified in the `COMPOSE_FILE` variable from the `.env` file. Then Django built-in server will be directly reachable at `http://localhost:8011` or through `nginx` at `https://localhost`.
 You should avoid using the Django's built-in server and better always develop and test QFieldCloud through the `nginx` [reverse proxy with SSL](#add-root-certificate).
 
-4. (OPTIONAL) In case you have a database dump, you can directly load some data in your development database.
+3. (OPTIONAL) In case you have a database dump, you can directly load some data in your development database.
 
 ```shell
 psql 'service=localhost.qfield.cloud' < ./qfc_dump_20220304.sql
 ```
 
-5. Run Django database migrations.
+4. Run Django database migrations.
 
 ```shell
 docker compose exec app python manage.py migrate
 ```
 
-6. And collect the static files (CSS, JS etc):
+5. And collect the static files (CSS, JS etc):
 
 ```shell
 docker compose run app python manage.py collectstatic --noinput
 ```
 
-7. Now you can get started by adding your super user that has access to the Django Admin interface:
+6. Now you can get started by adding your super user that has access to the Django Admin interface:
 
 ```shell
 docker compose run app python manage.py createsuperuser --username super_user --email super@user.com
 ```
 
-8. If QFieldCloud needs to be translated, you can compile the translations using Django's tooling:
+7. If QFieldCloud needs to be translated, you can compile the translations using Django's tooling:
 
 ```shell
 docker compose run --user root app python manage.py compilemessages