Browse Source

extra services and architectures

merge-requests/25/head
Steven Foerster 6 years ago
parent
commit
2a3a96cd3a
  1. 1
      .gitignore
  2. 23
      README.md

1
.gitignore vendored

@ -1,3 +1,4 @@
compose/production/traefik/traefik.toml compose/production/traefik/traefik.toml
.envs/ .envs/
.env .env
*.swp

23
README.md

@ -48,6 +48,15 @@ Tested Operating Systems (in order of thoroughness):
- Debian 10 (Buster) - Debian 10 (Buster)
- Raspbian Buster - Raspbian Buster
The default tests are run on DigitalOcean Droplets: 2GB RAM, 1 CPU, 50GB hard disk.
The Mistborn docker images exist for these architectures:
| Mistborn Docker Images (hub.docker.com) | Architectures |
|------------------------------------------------|---------------------|
| mistborn (django, celery{worker,beat}, flower) | amd64, arm64, armv7 |
| dnscrypt_proxy | amd64, arm64, armv7 |
Recommended System Specifications: Recommended System Specifications:
| Use Case | Description | RAM | Hard Disk | | Use Case | Description | RAM | Hard Disk |
@ -295,6 +304,20 @@ The `dev/` folder contains a script for completing a hard reset: destroying and
sudo ./dev/rebuild.sh sudo ./dev/rebuild.sh
``` ```
## Troubleshooting Extra Services
Each extra service has its own systemd process which can be monitored:
```
sudo journalctl -xfu Mistborn-homeassistant
sudo journalctl -xfu Mistborn-bitwarden
sudo journalctl -xfu Mistborn-syncthing
sudo journalctl -xfu Mistborn-jellyfin
sudo journalctl -xfu Mistborn-nextcloud
sudo journalctl -xfu Mistborn-jitsi
sudo journalctl -xfu Mistborn-rocketchat
sudo journalctl -xfu Mistborn-onlyoffice
sudo journalctl -xfu Mistborn-tor
```
## Troubleshooting Docker ## Troubleshooting Docker
Instead of defaulting to a system DNS server, Docker will try to use a public DNS server (e.g. 8.8.8.8). If you're having issues pulling or building Docker containers with "failure to connect" errors, this is the likely problem. You can manually set the DNS server Docker should use with the `DOCKER_OPTS` field in `/etc/default/docker`. Example: Instead of defaulting to a system DNS server, Docker will try to use a public DNS server (e.g. 8.8.8.8). If you're having issues pulling or building Docker containers with "failure to connect" errors, this is the likely problem. You can manually set the DNS server Docker should use with the `DOCKER_OPTS` field in `/etc/default/docker`. Example:
``` ```

Loading…
Cancel
Save