mirrors/shlink
1
0
Fork 0
mirror of https://github.com/shlinkio/shlink.git synced 2025-03-29 21:12:36 +03:00
Code Issues Projects Releases Packages Wiki Activity

Used stable docker tag on every docker run example

Browse source
This commit is contained in:
Alejandro Celaya 2019-12-07 09:31:46 +01:00 • committed by GitHub
parent e5f262869c
commit a0a1d3de72
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docker/README.md
View file

@ -19,7 +19,7 @@ It also expects these two env vars to be provided, in order to properly generate
So based on this, to run shlink on a local docker service, you should run a command like this: So based on this, to run shlink on a local docker service, you should run a command like this:
```bash ```bash
docker run --name shlink -p 8080:8080 -e SHORT_DOMAIN_HOST=doma.in -e SHORT_DOMAIN_SCHEMA=https shlinkio/shlink docker run --name shlink -p 8080:8080 -e SHORT_DOMAIN_HOST=doma.in -e SHORT_DOMAIN_SCHEMA=https shlinkio/shlink:stable
``` ```
### Interact with shlink's CLI on a running container. ### Interact with shlink's CLI on a running container.
@ -73,13 +73,13 @@ It is possible to use a set of env vars to make this shlink instance interact wi
Taking this into account, you could run shlink on a local docker service like this: Taking this into account, you could run shlink on a local docker service like this:
```bash ```bash
docker run --name shlink -p 8080:8080 -e SHORT_DOMAIN_HOST=doma.in -e SHORT_DOMAIN_SCHEMA=https -e DB_DRIVER=mysql -e DB_USER=root -e DB_PASSWORD=123abc -e DB_HOST=something.rds.amazonaws.com shlinkio/shlink docker run --name shlink -p 8080:8080 -e SHORT_DOMAIN_HOST=doma.in -e SHORT_DOMAIN_SCHEMA=https -e DB_DRIVER=mysql -e DB_USER=root -e DB_PASSWORD=123abc -e DB_HOST=something.rds.amazonaws.com shlinkio/shlink:stable
``` ```
You could even link to a local database running on a different container: You could even link to a local database running on a different container:
```bash ```bash
docker run --name shlink -p 8080:8080 [...] -e DB_HOST=some_mysql_container --link some_mysql_container shlinkio/shlink docker run --name shlink -p 8080:8080 [...] -e DB_HOST=some_mysql_container --link some_mysql_container shlinkio/shlink:stable
``` ```
> If you have considered using SQLite but sharing the database file with a volume, read [this issue](https://github.com/shlinkio/shlink-docker-image/issues/40) first. > If you have considered using SQLite but sharing the database file with a volume, read [this issue](https://github.com/shlinkio/shlink-docker-image/issues/40) first.
@ -145,7 +145,7 @@ docker run \
-e "BASE_PATH=/my-campaign" \ -e "BASE_PATH=/my-campaign" \
-e WEB_WORKER_NUM=64 \ -e WEB_WORKER_NUM=64 \
-e TASK_WORKER_NUM=32 \ -e TASK_WORKER_NUM=32 \
shlinkio/shlink shlinkio/shlink:stable
``` ```
## Provide config via volumes ## Provide config via volumes
@ -192,7 +192,7 @@ The whole configuration should have this format, but it can be split into multip
Once created just run shlink with the volume: Once created just run shlink with the volume:
```bash ```bash
docker run --name shlink -p 8080:8080 -v ${PWD}/my/config/dir:/etc/shlink/config/params shlinkio/shlink docker run --name shlink -p 8080:8080 -v ${PWD}/my/config/dir:/etc/shlink/config/params shlinkio/shlink:stable
``` ```
## Multi instance considerations ## Multi instance considerations