profxadke/misskey
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update docker.en.md

Browse source
This commit is contained in:
こぴなたみぽ 2017-05-19 08:04:24 +09:00 • committed by GitHub
parent 660560892f
commit 1c5fdf1e5d
1 changed files with 13 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

20
docs/docker.en.md
View file

@ -4,20 +4,26 @@ Setup with Docker :whale:
Ensure that the working directory is the repository root directory. Ensure that the working directory is the repository root directory.
To create misskey image: To create misskey image:
``` console
`sudo docker build -t misskey ./docker` $ sudo docker build -t misskey ./docker
```
To run misskey: To run misskey:
``` console
`sudo docker run --rm -i -t -p $PORT:80 -v $(pwd):/root/misskey -v $DBPATH:/data/db misskey` $ sudo docker run --rm -i -t -p $PORT:80 -v $(pwd):/root/misskey -v $DBPATH:/data/db misskey
```
where `$PORT` is the port used to access Misskey Web from host browser where `$PORT` is the port used to access Misskey Web from host browser
and `$DBPATH` is the path of MongoDB database on the host for data persistence. and `$DBPATH` is the path of MongoDB database on the host for data persistence.
ex: `sudo docker run --rm -i -t -p 80:80 -v $(pwd):/root/misskey -v /data/db:/data/db misskey` ex:
``` console
$ sudo docker run --rm -i -t -p 80:80 -v $(pwd):/root/misskey -v /data/db:/data/db misskey
```
If you want to run misskey in production mode, add `--env NODE_ENV=production` like this: If you want to run misskey in production mode, add `--env NODE_ENV=production` like this:
``` console
`sudo docker run --rm -i -t -p 80:80 -v $(pwd):/root/misskey -v /data/db:/data/db --env NODE_ENV=production misskey` $ sudo docker run --rm -i -t -p 80:80 -v $(pwd):/root/misskey -v /data/db:/data/db --env NODE_ENV=production misskey
```
Note that `$(pwd)` is the working directory. Note that `$(pwd)` is the working directory.