You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+47-34Lines changed: 47 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,13 +49,8 @@ To fetch upstream development, don't forget to update the submodules too:
49
49
cp .env.example .env
50
50
```
51
51
52
-
2. Change the `ENVIRONMENT` variable to `development`.
53
52
54
-
```shell
55
-
ENVIRONMENT=development
56
-
```
57
-
58
-
3. Build development images and run the containers:
53
+
2. Build development images and run the containers:
59
54
60
55
```shell
61
56
docker compose up -d --build
@@ -64,31 +59,31 @@ docker compose up -d --build
64
59
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`.
65
60
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).
66
61
67
-
4. (OPTIONAL) In case you have a database dump, you can directly load some data in your development database.
62
+
3. (OPTIONAL) In case you have a database dump, you can directly load some data in your development database.
and they are load balanced and available through the
406
-
db.qfield.cloud address.
407
-
408
-
There is a template database called
409
-
`template_postgis` that is used to create the databases for the
410
-
users. The template db has the following extensions installed:
411
-
412
-
- fuzzystrmatch
413
-
- plpgsql
414
-
- postgis
415
-
- postgis<sub>tiger</sub><sub>geocoder</sub>
416
-
- postgis<sub>topology</sub>
417
-
418
403
### Storage
419
404
420
405
You can use either the integrated `minio` object storage, or use an external provider (e. g. S3) with versioning enabled. Check the corresponding `STORAGE_*` environment variables for more info.
@@ -436,10 +421,38 @@ Migration to a newer database version is a risky operation to your data, so prep
436
421
437
422
Contributions welcome!
438
423
439
-
Any PR including the `[WIP]` should be:
440
-
- able to be checked-out without breaking the stack;
424
+
425
+
### Before considering a new PR
426
+
427
+
For the best chance of having your PR merged, you must first communicate your idea(s) and clarify the details with the QFieldCloud developers.
428
+
429
+
1) Create a dedicated [issue in the QFieldCloud repository](https://github.com/opengisch/QFieldCloud/issues) detailing your suggestion.
430
+
2) Engage in the feedback and guidance provided by the development team during their review of your issue.
431
+
432
+
Discussing it first is crucial. Not every idea is accepted, and these steps will save you the time and energy of creating a PR that wouldn't be merged.
433
+
434
+
Any new, follow-up discussions should be opened in a new issue that references the original.
435
+
436
+
437
+
### Before opening a new PR
438
+
439
+
- Make sure you prepare a small focused branch with your changes, properly referencing the source issue and add a detailed description to the PR opening message.
440
+
- If the change addresses a UI/UX change, provide a before and after screenshot.
441
+
- Your branch should be based on the latest `master` branch.
442
+
- In the rare occurances when it is not based on `master`, please base your PR on the respective branch.
443
+
444
+
445
+
### Pull requests
446
+
447
+
If your PR is not ready to be merged, please mark it as a [draft PR](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft).
448
+
449
+
A draft PR can allow QFieldCloud developers to provide you early feedback.
450
+
However, make sure a draft PR:
451
+
452
+
- can be checked-out without breaking the stack;
441
453
- the specific feature being developed/modified should be testable locally (does not mean it should work correctly).
0 commit comments