Closed mfranzon closed 10 months ago
Current folder structure:
$ tree . -I Resources -I Old
.
├── config.env
├── demos
│ ├── Dockerfile.demos.step1
│ ├── Dockerfile.demos.step2
│ ├── fractal.env
│ ├── get_fractal_client.sh
│ ├── get_fractal_demos.sh
│ ├── get_fractal_tasks_core.sh
│ ├── requirements-validation.txt
│ └── run_demos.sh
├── docker-compose-demos.yml
├── LICENSE
├── makefile
├── README.md
├── server
│ ├── Dockerfile.server.step1
│ ├── Dockerfile.server.step2
│ ├── get_fractal_server.sh
│ └── server.env
└── web
├── Dockerfile.web.step1
├── Dockerfile.web.step2
├── get_fractal_web.sh
└── web.env
3 directories, 21 files
where the get
scripts are the ones handling versions.
As per versions: we can now set them via the config.env
file (not for GitHub CI, but for local tests).
I've not yet implemented some from-git installs, but the release can be set correctly.
Some of the latest updates:
config.env
;makefile
, with precise cache/no-cache targets and with two main targets for local tests (possibly with versions, and always with web) and github tests;This is enough for this PR, let's open new issues/PRs for specific future updates.
Work in progress fractal demos compose.
Refactor of
fractal-share
directory. At the moment there is a mess in thefractal-share
usage, it is used during the image building and during the startup of services. This provokes inconsistencies in the state of the folder, it can be empty, with the right content or not.Possible solution, move all the demos services command in the docker compose, leaving demos image without an entrypoint.
This postpone the usage of fractal-server resolving the the inconsistency.
In general, is highly discourage using a mount-point during the image building, it should be use just at run time.
ref fractal-analytics-platform/fractal-server#866 , fractal-analytics-platform/fractal-containers#18