Skip to content
Snippets Groups Projects
Unverified Commit 676c9f17 authored by Alexis Lefebvre's avatar Alexis Lefebvre Committed by GitHub
Browse files

Update README

parent 58e24533
No related branches found
No related tags found
No related merge requests found
# For common users: # Librephotos
Set the needed variables in .env (take librephotos.env as model)
## For common users:
Set the needed variables in `.env` file (take `librephotos.env` as model)
Clone the repo: `git clone git@github.com:LibrePhotos/librephotos-docker.git` Clone the repo: `git clone git@github.com:LibrePhotos/librephotos-docker.git`
docker-compose up -d Then launch it: `docker-compose up -d`
This will get the pre-built images and start all the needed processes This will get the pre-built images and start all the needed processes
# For developers: ## For developers:
Set the needed variables in .evn (take librephotos.env as model) Set the needed variables in `.env` file (take `librephotos.env` as model)
Also set the codedir variable that tells docker where your source folder are
Also set the codedir variable that tells docker where your source folder are.
Pull frontend code with `git clone https://github.com/LibrePhotos/librephotos-frontend.git ${codedir}/frontend/` Pull frontend code with `git clone https://github.com/LibrePhotos/librephotos-frontend.git ${codedir}/frontend/`
Pull backend code into `git clone https://github.com/LibrePhotos/librephotos.git ${codedir}/backend/` Pull backend code into `git clone https://github.com/LibrePhotos/librephotos.git ${codedir}/backend/`
...@@ -23,9 +28,9 @@ N.B. If you already built this image once, when you do force rebuild you have to ...@@ -23,9 +28,9 @@ N.B. If you already built this image once, when you do force rebuild you have to
`docker-compose -f docker-compose.yml -f docker-compose.dev.yml build --no-cache backend` `docker-compose -f docker-compose.yml -f docker-compose.dev.yml build --no-cache backend`
based on which one you changed if these changes need rebuild as for added dependencies/libraries etc. Based on which one you changed if these changes need rebuild as for added dependencies/libraries etc.
and then the usual `docker-compose -f docker-compose.yml -f docker-compose.dev.yml up -d` and then the usual `docker-compose -f docker-compose.yml -f docker-compose.dev.yml up -d`
If you use vscode you can also benefit auto completion and other goodies. For this just type `code .` in your dockerfile folder. If you use vscode you can also benefit auto completion and other goodies. For this just type `code .` in your dockerfile folder.
Vscode will open and ask you if you want to reopen it in the container. If you do it he will add his server to the docker layers (first time you do it can take a couple of minutes) and you will have the same python interpreter librephotos is using internally hence the same installed libraries in auto completion and the same development environment will be shared by all devs (isort, flake8 and pylint for example) Vscode will open and ask you if you want to reopen it in the container. If you do it, it will add his server to the docker layers (first time you do it can take a couple of minutes) and you will have the same Python interpreter librephotos is using internally hence the same installed libraries in auto completion and the same development environment will be shared by all devs (isort, flake8 and pylint for example).
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment