Merge branch 'dockerize' into 'master'
Add a Dockerfile and instructions to run with Docker See merge request pleroma/relay!20
This commit is contained in:
commit
f3b4fc44b8
3
.gitignore
vendored
3
.gitignore
vendored
|
@ -96,3 +96,6 @@ ENV/
|
|||
|
||||
viera.yaml
|
||||
viera.jsonld
|
||||
|
||||
# config file
|
||||
relay.yaml
|
||||
|
|
11
Dockerfile
Normal file
11
Dockerfile
Normal file
|
@ -0,0 +1,11 @@
|
|||
FROM python:3-alpine
|
||||
WORKDIR /workdir
|
||||
RUN apk add alpine-sdk autoconf automake libtool gcc
|
||||
|
||||
ADD requirements.txt /workdir/
|
||||
RUN pip3 install -r requirements.txt
|
||||
|
||||
ADD . /workdir/
|
||||
CMD ["python", "-m", "relay"]
|
||||
|
||||
VOLUME ["/workdir/data"]
|
10
README.md
10
README.md
|
@ -69,3 +69,13 @@ This will show the available management tasks:
|
|||
|
||||
When following remote relays, you should use the `/actor` endpoint as you would in
|
||||
Pleroma and other LitePub-compliant software.
|
||||
|
||||
## Docker
|
||||
|
||||
You can run ActivityRelay with docker. Edit `relay.yaml` so that the database
|
||||
location is set to `./data/relay.jsonld` and then build and run the docker
|
||||
image :
|
||||
|
||||
$ docker volume create activityrelay-data
|
||||
$ docker build -t activityrelay .
|
||||
$ docker run -d -p 8080:8080 -v activityrelay-data:/workdir/data activityrelay
|
||||
|
|
Loading…
Reference in a new issue