Commit a722fc7f authored by LETORT Sebastien's avatar LETORT Sebastien
Browse files

Merge branch '358-script-prepare-sh-3' into 'django'

Resolve "script prepare.sh"

Closes #358

See merge request !201
parents 192b7413 42c9bd8a
Pipeline #121695 passed with stages
in 5 minutes and 36 seconds
......@@ -94,7 +94,7 @@ For convenience, all containers not running as root (django, mysql, registry)
have their user overridden to the UID:GID of the developer running
docker-compose. This is managed with the `DOCKERUSER` environment variable set
[in the `.env` file](https://docs.docker.com/compose/environment-variables/#the-env-file) by
`prepare.sh`.
`bootstrap` script.
For convenience (again), there is an extra external volume for `dev-django`,
`dev-controller` and `dev-ssh` so that the source directory of the app is mounted
......@@ -243,23 +243,23 @@ Re-open your session (to be effectively in the docker group)
#### **dev-mysql** initialisation fails
The `prepare.sh` script (also sourced by the `./bootstrap` script) creates the
`/data/dev/*/` with the ownership set to the calling user. **Be sure not to run
it as root**, otherwise it will be owned by root and you may have errors like:
At [Getting started](#getting-started) step 2 you should have create the
`/data/dev/*/` with the ownership set to the calling user. Otherwise it will be owned by root and you may have errors like:
mkdir: cannot create directory ‘/vol/rw’: Permission denied
mkdir: cannot create directory ‘/vol/log’: Permission denied
If somehow you skipped this step, you can reset the ownership to the current user:
sudo chown $USER: /data/dev
sudo chown $USER: /data/dev
sudo chown -R $USER: /data/dev/{registry,mysql,django}
If you are completely lost, you can just restart the initialisation from scratch:
fig down
sudo rm -rf /data/dev
. prepare.sh
sudo mkdir -p /data/dev
sudo chown $USER: /data/dev
./bootstrap
......@@ -318,7 +318,7 @@ TODO ?
supervisorctl stop rails
rails server
</pre>
)
)
## ssh
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment