LumeWeb
/
skynet-webportal
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

do not enable custom.domain by default and improve docs

This commit is contained in:
Karol Wypchlo 2020-07-17 21:12:18 +02:00
parent 387c0e31c0
commit 7e06436aa6
2 changed files with 13 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docker/caddy/Caddyfile
View File

@ -97,5 +97,5 @@
} }
import localhost import localhost
import custom.domain # import custom.domain
# import siasky.net # import siasky.net

18
setup-scripts/README.md
View File

@ -94,12 +94,14 @@ At this point we have almost everything set up. We have 2 siad instances running
1. generate and copy sia api token `printf ":$(cat /home/user/.sia/apipassword)" | base64` 1. generate and copy sia api token `printf ":$(cat /home/user/.sia/apipassword)" | base64`
1. edit `/home/user/skynet-webportal/.env` and configure following environment variables 1. edit `/home/user/skynet-webportal/.env` and configure following environment variables
- `DOMAIN_NAME` is your domain name - `DOMAIN_NAME` (optional) is your domain name if you have it
- `EMAIL_ADDRESS` is your email address used for communication regarding SSL certification - `EMAIL_ADDRESS` (required) is your email address used for communication regarding SSL certification (required)
- `SIA_API_AUTHORIZATION` is token you just generated in the previous point - `SIA_API_AUTHORIZATION` (required) is token you just generated in the previous point
- `CLOUDFLARE_AUTH_TOKEN` if using cloudflare as dns loadbalancer (just for siasky.net) - `CLOUDFLARE_AUTH_TOKEN` (optional) if using cloudflare as dns loadbalancer (it's just for siasky.net configuration)
1. only for siasky.net domain instances: edit `/home/user/skynet-webportal/docker/caddy/Caddyfile`, uncomment `import siasky.net` and comment out `import custom.domain` 1. if you have a custom domain and you configured it in `DOMAIN_NAME`, edit `/home/user/skynet-webportal/docker/caddy/Caddyfile` and uncomment `import custom.domain`
1. `sudo docker-compose up -d` to restart the services so they pick up new configuration 1. only for siasky.net domain instances: edit `/home/user/skynet-webportal/docker/caddy/Caddyfile`, uncomment `import siasky.net`
1. `sudo docker-compose up -d` to restart the services so they pick up new env variables
1. `sudo docker exec caddy caddy reload --config /etc/caddy/Caddyfile` to reload Caddyfile configuration
### Useful Commands ### Useful Commands
@ -118,6 +120,10 @@ At this point we have almost everything set up. We have 2 siad instances running
- Restarting siad service - Restarting siad service
- `systemctl --user restart siad` for download node - `systemctl --user restart siad` for download node
- `systemctl --user restart siad-upload` for upload node - `systemctl --user restart siad-upload` for upload node
- Restarting caddy gracefully after making changes to Caddyfile
- `sudo docker exec caddy caddy reload --config /etc/caddy/Caddyfile`
- Restarting nginx gracefully after making changes to nginx configs
- `sudo docker exec nginx openresty -s reload`
- Checking siad service logs (follow last 50 lines) - Checking siad service logs (follow last 50 lines)
- `journalctl -f -n 50 --user-unit siad` for download node - `journalctl -f -n 50 --user-unit siad` for download node
- `journalctl -f -n 50 --user-unit siad-upload` for upload node - `journalctl -f -n 50 --user-unit siad-upload` for upload node