sneak/mastodon-docker
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

update docs and add deploy command to makefile

Browse Source
This commit is contained in:
Jeffrey Paul 2019-12-09 05:26:49 -08:00
parent 2862faf676
commit 47af4d5efc
2 changed files with 16 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Makefile
View File

@ -8,3 +8,6 @@ build:
run:
-docker rm -f mastodon
docker run --env WEB_DOMAIN="test123.example.com" --hostname mastodon --name mastodon -ti $(NAME)
deploy:
caprover deploy -a mastodon --default

21
README.md
View File

@ -4,19 +4,21 @@ Don't ever host things anywhere but on a domain that you own.
This violates all the docker best practices and puts the whole-ass app
inside a single container (including redis and postgres!) so that you can
easily bring up a sef-hosted mastodon on things like caprover in a single
"app" without having to worry about cross-container links.
easily bring up a self-hosted mastodon on things like caprover self-hosted
PaaS in a single "app" without having to worry about multiple containers or
configuring cross-container links.
This is scratching an itch: I really just wanted a one-command single-user
Mastodon instance.
Mastodon instance that stores all of its state in a single directory I can
tar and scp.
# Features
* Ubuntu bionic
* Everything in one container, including a very minimal postfix, postgres,
* Everything in one container, including minimal postfix, postgres,
and redis
* assets are precompiled on startup
* all state is in one volume
* assets are precompiled on server startup
* all state is in one volume/dir
* database migrations can be run at startup
# Build Variables
@ -47,8 +49,8 @@ here for all processes without restarting the docker container.
# Ports
* 3000: mastodon web (no tls, do that elsewhere)
* 4000: mastodon streaming
* `3000`: mastodon web (no tls, do that elsewhere)
* `4000`: mastodon streaming
# Credits
@ -90,3 +92,6 @@ mastodon@c81a376bf546:~$ cd app
mastodon@c81a376bf546:~/app$ RAILS_ENV=production envdir /state/envdir bin/tootctl accounts create <newusername> --email <your email> --confirmed --role admin
```
If `WEB_DOMAIN` != `LOCAL_DOMAIN` make sure you have both set in your
shell's environment (or in the envdir) before running tootctl to add your
user.