all repos — birabittoh.github.io @ 57ced0b29ebd4a1a1b1a765e9c12bec112755d2d

My current website, built with Zola.

small tweaks
Andronaco Marco marco.andronaco@olivetti.com
Mon, 17 Jul 2023 23:38:22 +0200
commit

57ced0b29ebd4a1a1b1a765e9c12bec112755d2d

parent

e11e212760e428a637a03ae4ace53cb0ad89dc58

2 files changed, 2 insertions(+), 2 deletions(-)

jump to
M content/_index.mdcontent/_index.md

@@ -19,5 +19,5 @@ - 🎬 [shows](/more/shows)

## Contact - Email: [birabittoh[at]tilde[dot]team](mailto:birabittoh@tilde.team) - - Code: [github.com](https://github.com/BiRabittoh), [tilde.institute](https://git.tilde.institute/birabittoh) + - Code: [github](https://github.com/BiRabittoh), [tildegit](https://tildegit.org/BiRabittoh) - {{ metaData(content="@BiRabittoh") }} anywhere else.
M content/blog/self-host.mdcontent/blog/self-host.md

@@ -158,7 +158,7 @@ ```

docker network connect swag_default invidious ``` -Finally, you can visit https://yt.<yourdomain>.duckdns.org/ and check if you can access Invidious through HTTPS. +Finally, you can visit https://yt.<your-domain>.duckdns.org/ and check if you can access Invidious through HTTPS. Note: now that you have a reverse proxy set up, you can remove your `ports:` section entirely from Invidious' `docker-compose.yml`. You can do this because the containers are communicating internally to the `swag_default` network, without the need to expose any ports to the outside.