Tidy up like it's 2019

2026-11-02 13:58:18 +00:00 · 2019-05-15 10:54:50 +12:00
1 parent 480dee111a
commit 4654c131b2
@@ -125,7 +125,7 @@ Now work your way through the list of tools below, adding whichever tools your w
 * [Jackett](/recipes/autopirate/jackett/)
 * [End](/recipes/autopirate/end/) (launch the stack)

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -13,7 +13,7 @@ Log into each of your new tools at its respective HTTPS URL. You'll be prompted

 1. This is a complex stack. Sing out in the comments if you found a flaw or need a hand :)

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -74,7 +74,7 @@ Continue through the list of tools below, adding whichever tools your want to us

 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -81,7 +81,7 @@ Continue through the list of tools below, adding whichever tools your want to us
 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.
 2. The inclusion of Heimdall was due to the efforts of @gkoerk in our [Discord server](http://chat.funkypenguin.co.nz). Thanks gkoerk!

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -74,7 +74,7 @@ Continue through the list of tools below, adding whichever tools your want to us

 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -87,7 +87,7 @@ Continue through the list of tools below, adding whichever tools your want to us
 1. The calibre-server container co-exists within the Lazy Librarian (LL) containers so that LL can automatically add a book to Calibre using the calibre-server interface. The calibre library can then be properly viewed using the [calibre-web](/recipes/calibre-web) recipe.
 2. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -76,7 +76,7 @@ Continue through the list of tools below, adding whichever tools your want to us
 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.
 2. The addition of the Lidarr recipe was contributed by our very own @gpulido in Discord (http://chat.funkypenguin.co.nz) - Thanks Gabriel!

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -72,7 +72,7 @@ Continue through the list of tools below, adding whichever tools your want to us

 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -79,7 +79,7 @@ Continue through the list of tools below, adding whichever tools your want to us

 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -78,7 +78,7 @@ Continue through the list of tools below, adding whichever tools your want to us

 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -94,7 +94,7 @@ Continue through the list of tools below, adding whichever tools your want to us
 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra2, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.
 2. Note that NZBHydra2 _can_ co-exist with NZBHydra (1), but if you want your tools (Sonarr, Radarr, etc) to use NZBHydra2, you'll need to change both the target hostname (_to "hydra2"_) and the target port (_to 5076_).

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -79,7 +79,7 @@ Continue through the list of tools below, adding whichever tools your want to us

 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -90,7 +90,7 @@ Continue through the list of tools below, adding whichever tools your want to us

 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -79,7 +79,7 @@ Continue through the list of tools below, adding whichever tools your want to us

 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -86,7 +86,7 @@ Continue through the list of tools below, adding whichever tools your want to us

 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -76,7 +76,7 @@ Continue through the list of tools below, adding whichever tools your want to us

 1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -90,7 +90,7 @@ Once you've created your account, jump over to https://bitwarden.com/#download a
 1. You'll notice we're not using the *official* container images (*[all 6 of them required](https://help.bitwarden.com/article/install-on-premise/#install-bitwarden)!)*, but rather a [more lightweight version ideal for self-hosting](https://hub.docker.com/r/mprasil/bitwarden). All of the elements are contained within a single container, and SQLite is used for the database backend.
 2. The inclusion of Bitwarden was due to the efforts of @gkoerk in our [Discord server](http://chat.funkypenguin.co.nz)- Thanks Gerry!

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -145,7 +145,7 @@ Log into your new instance at https://**YOUR-FQDN**, authenticate with oauth_pro

 1. If you wanted to expose the BookStack UI directly, you could remove the oauth2_proxy from the design, and move the traefik_public-related labels directly to the bookstack container. You'd also need to add the traefik_public network to the bookstack container.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -127,7 +127,7 @@ Log into your new instance at https://**YOUR-FQDN**. You'll be directed to the i
 1. Yes, Calibre does provide a server component. But it's not as fully-featured as Calibre-Web (_i.e., you can't use it to send ebooks directly to your Kindle_)
 2. A future enhancement might be integrating this recipe with the filestore for [NextCloud](/recipes/nextcloud/), so that the desktop database (Calibre) can be kept synced with Calibre-Web.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -304,7 +304,7 @@ Now browse your NextCloud files. Click the plus (+) sign to create a new documen

 1. Yes, this recipe is complicated. And you probably only care if you feel strongly about using Open Source rich document editing in the browser, vs using something like Google Docs. It works impressively well however, once it works. I hope to make this recipe simpler once the CODE developers have documented how to pass optional parameters as environment variables.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -35,7 +35,7 @@ For readability, I've split this recipe into multiple sub-recipes, which can be

 1. Ultimately I hope to move all the configuration / mining executables into docker containers, but for now, they're running on a CentOS7 host for direct access to GPUs. (Apparently it _may_ be possible to pass-thru the GPUs to docker containers, but I wanted stability first, before abstracting my hardware away from my miners)

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -162,7 +162,7 @@ Now, continue to the next stage of your grand mining adventure:

 1. My two RX580 cards (_bought alongside each other_) perform slightly differently. GPU0 works with a 2050Mhz memory clock, but GPU1 only works at 2000Mhz. Anything over 2000Mhz causes system instability. YMMV.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -48,7 +48,7 @@ Now, continue to the next stage of your grand mining adventure:

 ## Chef's Notes

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -98,7 +98,7 @@ Now, continue to the next stage of your grand mining adventure:

 ## Chef's Notes

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -51,7 +51,7 @@ Now, continue to the next stage of your grand mining adventure:

 ## Chef's Notes

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -48,7 +48,7 @@ Yes. It's the ultimate _#firstworldproblem_, but if you have a means to remotely

 (_I hooked up a remote-controlled outlet to my rig, so that I can power-cycle it without having to crawl under the desk!_)

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -86,7 +86,7 @@ Now, continue to the next stage of your grand mining adventure:

 1. Ultimately I hope to move all the configuration / mining executables into docker containers, but for now, they're running on a CentOS7 host for direct access to GPUs. (_Apparently it **may** be possible to pass-thru the GPUs to docker containers, but I wanted stability first, before abstracting my hardware away from my miners_)

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -157,7 +157,7 @@ Now, continue to the next stage of your grand mining adventure:

 ## Chef's Notes

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -21,7 +21,7 @@ Get in touch and share your experience - there's a special [discord](https://dis

 ## Chef's Notes

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -34,7 +34,7 @@ Now, continue to the next stage of your grand mining adventure:

 ## Chef's Notes

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -165,7 +165,7 @@ Nothing will happen. Very boring. But when the cron script fires (daily), duplic
 1. Automatic backup can still fail if nobody checks that it's running successfully. I'll be working on an upcoming recipe to monitor the elements of the stack, including the success/failure of duplicity jobs.
 2. The container provides the facility to specify an SMTP host and port, but not credentials, which makes it close to useless. As a result, I've left SMTP out of this recipe. To enable email notifications (if your SMTP server doesn't require auth), add ```SMTP_HOST```, ```SMTP_PORT```, ```EMAIL_FROM``` and ```EMAIL_TO``` variables to duplicity.env

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -248,7 +248,7 @@ This takes you to a list of backup names and file paths. You can choose to downl
 1. If you wanted to expose the ElkarBackup UI directly, you could remove the oauth2_proxy from the design, and move the traefik_public-related labels directly to the app service. You'd also need to add the traefik_public network to the app service.
 2. The original inclusion of ElkarBackup was due to the efforts of @gpulido in our [Discord server](http://chat.funkypenguin.co.nz). Thanks Gabriel!

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -89,7 +89,7 @@ Log into your new instance at https://**YOUR-FQDN**, and complete the wizard-bas
 2. Got an NVIDIA GPU? See [this blog post](https://www.funkypenguin.co.nz/note/gpu-transcoding-with-emby-plex-using-docker-nvidia/) re how to use your GPU to transcode your media!
 3. We don't bother exposing the HTTPS port for Emby, since [Traefik](/ha-docker-swarm/traefik/) is doing the SSL termination for us already.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -70,7 +70,7 @@ Create your first administrative account at https://**YOUR-FQDN**/admin/
 [root@ds1 ghost]#
 ```

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -95,7 +95,7 @@ Log into your new instance at https://**YOUR-FQDN**, with user "root" and the pa
 2. Originally I deployed runners in the same stack as GitLab, but I found that they would frequently fail to start properly when I launched the stack. I think that this was because the runners started so quickly (and GitLab starts so slowly!), that they always started up reporting that the GitLab instance was invalid or unavailable. I had issues with CI builds stuck permanently in a "pending" state, which were only resolved by restarting the runner. Having the runners deployed in a separate stack to GitLab avoids this problem.


-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -136,7 +136,7 @@ A few comments on decisions taken in this design:
 1. I use the **sameersbn/gitlab:latest** image, rather than a specific version. This lets me execute updates simply by redeploying the stack (and why **wouldn't** I want the latest version?)


-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -129,7 +129,7 @@ Authenticate against your OAuth provider, and then start editing your wiki!

 1. In the current implementation, Gollum is a "single user" tool only. The contents of the wiki are saved as markdown files under /var/data/gollum, and all the git commits are currently "Anonymous"

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -132,7 +132,7 @@ Log into your new instance at https://**YOUR-FQDN**, the password you created in

 1. I **tried** to protect Home Assistant using [oauth2_proxy](/reference/oauth_proxy), but HA is incompatible with the websockets implementation used by Home Assistant. Until this can be fixed, I suggest that geeks set frontend: api_key to a long and complex string, and rely on this to prevent malevolent internet miscreants from turning their lights on at 2am!

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -146,7 +146,7 @@ Log into your new instance at https://**YOUR-FQDN**. You'll need to use the "Sig

 1. I initially considered putting an oauth proxy in front of Huginn, but since the invitation code logic prevents untrusted access, and since using a proxy would break oauth for sevices like Twitter integration, I left it out.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -129,7 +129,7 @@ You can **also** watch the bot at work by VNCing to your docker swarm, password

 1. Amazingly, my bot has ended up tagging more _non-penguins_ than actual penguins. I don't understand how Instagrammers come up with their hashtags!

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -184,7 +184,7 @@ QmbqPBLJNXWpbXEX6bVhYLo2ruEBE7mh1tfT9s6VXUzYYx | 28c13ec68f33 | Sees 2 other pee

 1. I'm still trying to work out how to _mount_ the ipfs data in my filesystem in a usable way. Which is why this is still a WIP :)

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -121,7 +121,7 @@ Log into your new instance at https://**YOUR-FQDN**. Default credentials are adm
 1. The default theme can be significantly improved by applying the [ThemePlus](https://github.com/phsteffen/kanboard-themeplus) plugin.
 2. Kanboard becomes more useful when you integrate in/outbound email with [MailGun](https://github.com/kanboard/plugin-mailgun), [SendGrid](https://github.com/kanboard/plugin-sendgrid), or [Postmark](https://github.com/kanboard/plugin-postmark).

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -180,7 +180,7 @@ For each of the following mappers, click the name, and set the "_Read Only_" fla

 ## Chef's Notes

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -264,7 +264,7 @@ To look at the Kanboard pod's logs, run ```kubectl logs -n kanboard <name of pod

 1. The simplest deployment of Kanboard uses the default SQLite database backend, stored on the persistent volume. You can convert this to a "real" database running MySQL or PostgreSQL, and running an an additional database pod and service. Contact me if you'd like further details ;)

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -321,7 +321,7 @@ To look at the Miniflux pod's logs, run ```kubectl logs -n miniflux <name of pod

 ## Chef's Notes

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -126,7 +126,7 @@ Log into your new instance at https://**YOUR-FQDN**, with user "root" and the pa

 1. If you wanted to expose the Wekan UI directly, you could remove the oauth2_proxy from the design, and move the traefik_public-related labels directly to the wekan container. You'd also need to add the traefik_public network to the wekan container.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -119,7 +119,7 @@ Log into your new instance at https://**YOUR-FQDN**, with user "root" and the pa

 1. If you wanted to expose the Wekan UI directly, you could remove the oauth2_proxy from the design, and move the traefik_public-related labels directly to the wekan container. You'd also need to add the traefik_public network to the wekan container.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -126,7 +126,7 @@ Log into your new instance at https://**YOUR-FQDN**, with user "root" and the pa

 1. If you wanted to expose the Wekan UI directly, you could remove the oauth2_proxy from the design, and move the traefik_public-related labels directly to the wekan container. You'd also need to add the traefik_public network to the wekan container.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -264,7 +264,7 @@ To look at the Kanboard pod's logs, run ```kubectl logs -n kanboard <name of pod

 1. The simplest deployment of Kanboard uses the default SQLite database backend, stored on the persistent volume. You can convert this to a "real" database running MySQL or PostgreSQL, and running an an additional database pod and service. Contact me if you'd like further details ;)

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -184,7 +184,7 @@ Launch the mail server stack by running ```docker stack deploy docker-mailserver

 2. If you're using sieve with Rainloop, take note of the [workaround](https://discourse.geek-kitchen.funkypenguin.co.nz/t/mail-server-funky-penguins-geek-cookbook/70/15) identified by [ggilley](https://discourse.geek-kitchen.funkypenguin.co.nz/u/ggilley)

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -120,7 +120,7 @@ Log into your new instance at https://**YOUR-FQDN**, with user "root" and the pa

 1. If you wanted to expose the Wekan UI directly, you could remove the oauth2_proxy from the design, and move the traefik_public-related labels directly to the wekan container. You'd also need to add the traefik_public network to the wekan container.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -140,7 +140,7 @@ Log into your new instance at https://**YOUR-FQDN**, using the credentials you s

 1. Find the bookmarklet under the **Settings -> Integration** page.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -176,7 +176,7 @@ goofys#bucket   /mnt/mountpoint        fuse     _netdev,allow_other,--file-mode=
 2. Some applications (_like [NextCloud](/recipes/nextcloud/)_) can natively mount S3 buckets
 3. Some backup tools (_like [Duplicity](/recipes/duplicity/)_) can backup directly to S3 buckets

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -206,7 +206,7 @@ To actually **use** your new MQTT broker, you'll need to connect to any one of y

 ## Chef's Notes

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -138,7 +138,7 @@ Log into your new instance at https://**YOUR-FQDN**, with user and password pass

 1. If you wanted to expose the Munin UI directly, you could remove the oauth2_proxy from the design, and move the traefik-related labels directly to the munin container. You'd also need to add the traefik_public network to the munin container.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -234,7 +234,7 @@ Note that this .htaccess can be overwritten by NextCloud, and you may have to re
 1. Since many of my other recipes use PostgreSQL, I'd have preferred to use Postgres over MariaDB, but MariaDB seems to be the [preferred database type](https://github.com/nextcloud/server/issues/5912).
 2. I'm [not the first user](https://github.com/nextcloud/docker/issues/528) to stumble across the service discovery bug with reverse proxies.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -441,7 +441,7 @@ Create your users using the "**New User**" button.

 1. The KeyCloak](/recipes/keycloak/) recipe illustrates how to integrate KeyCloak with your LDAP directory, giving you a cleaner interface to manage users, and a raft of SSO / OAuth features.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -115,7 +115,7 @@ Log into your new instance at https://**YOUR-FQDN**, with user "root" and the pa
 2. I'm using my own image rather than owntracks/recorderd, because of a [potentially swarm-breaking bug](https://github.com/owntracks/recorderd/issues/14) I found in the official container. If this gets resolved (_or if I was mistaken_) I'll update the recipe accordingly.
 3. By default, you'll get a fully accessible, unprotected MQTT broker. This may not be suitable for public exposure, so you'll want to look into securing mosquitto with TLS and ACLs.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -209,7 +209,7 @@ Log into your new instance at https://**YOUR-FQDN**, and follow the on-screen pr

 1. If you wanted to expose the phpIPAM UI directly, you could remove the oauth2_proxy and the nginx services from the design, and move the traefik_public-related labels directly to the phpipam container. You'd also need to add the traefik_public network to the phpipam container.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -92,7 +92,7 @@ Launch the Piwik stack by running ```docker stack deploy piwik -c <path -to-dock

 Log into your new instance at https://**YOUR-FQDN**, and follow the wizard to complete the setup.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -99,7 +99,7 @@ Log into your new instance at https://**YOUR-FQDN** (You'll need to setup a plex
 1. Plex uses port 32400 for remote access, using your plex.tv user/password to authenticate you. The inclusion of the traefik proxy in this recipe is simply to allow you to use the web client (as opposed to a client app) by connecting directly to your instance, as opposed to browsing your media via https://plex.tv/web
 2. Got an NVIDIA GPU? See [this blog post](https://www.funkypenguin.co.nz/note/gpu-transcoding-with-emby-plex-using-docker-nvidia/) re how to use your GPU to transcode your media!

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -68,7 +68,7 @@ Log into your new instance at https://**YOUR-FQDN**. You'll be prompted to set y

 1. I wanted to use oauth2_proxy to provide an additional layer of security for Portainer, but the proxy seems to break the authentication mechanism, effectively making the stack **so** secure, that it can't be logged into!

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -63,7 +63,7 @@ Log into your new instance at https://**YOUR-FQDN**, with user "root" and the pa
 1. The [PrivateBin repo](https://github.com/PrivateBin/PrivateBin/blob/master/INSTALL.md) explains how to tweak configuration options, or to use a database instead of file storage, if your volume justifies it :)
 2. The inclusion of PrivateBin was due to the efforts of @gkoerk in our [Discord server](http://chat.funkypenguin.co.nz). Thanks Jerry!!

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -113,7 +113,7 @@ Log into your new instance at https://**YOUR-FQDN**, authenticate against oauth_
 1. If you wanted to expose the Realms UI directly, you could remove the oauth2_proxy from the design, and move the traefik_public-related labels directly to the realms container. You'd also need to add the traefik_public network to the realms container.
 2. The inclusion of Realms was due to the efforts of @gkoerk in our [Discord server](http://chat.funkypenguin.co.nz). Thanks gkoerk!

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -395,7 +395,7 @@ Log into your new grafana instance, check out your beautiful graphs. Move onto d

 1. Pay close attention to the ```grafana.env``` config. If you encounter errors about ```basic auth failed```, or failed CSS, it's likely due to misconfiguration of one of the grafana environment variables.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -118,7 +118,7 @@ Log into your new instance at https://**YOUR-FQDN**, with user "root" and the pa

 1. If you wanted to expose the Wekan UI directly, you could remove the oauth2_proxy from the design, and move the traefik_public-related labels directly to the wekan container. You'd also need to add the traefik_public network to the wekan container.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -135,7 +135,7 @@ There are several TTRSS containers available on docker hub, none of them "offici

 2. The upstream git URL [changed recently](https://discourse.tt-rss.org/t/gitlab-is-overbloated-shit-garbage/325/6), but my experience of the new repository is that it's **SO** slow, that the initial "git clone" on setup of the container times out. To work around this, I created [my own repo](https://github.com/funkypenguin/tt-rss.git), cloned upstream, pushed it into my repo, and pointed the container at my own repo with TTRSS_REPO. I don't get the _latest_ code changes, but at least the app container starts up. When upstream git is performing properly, I'll remove TTRSS_REPO to revert back to the "rolling release".

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -448,7 +448,7 @@ Two possible solutions to this are (1) disable banning, or (2) update the pool b

 3. After a [power fault in my datacenter caused daemon DB corruption](https://www.reddit.com/r/TRTL/comments/8jftzt/funky_penguin_nz_mining_pool_down_with_daemon/), I added a second daemon, running in parallel to the first. The failsafe daemon runs once an hour, syncs with the running daemons, and shuts down again, providing a safely halted version of the daemon DB for recovery.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -201,7 +201,7 @@ Even with all these elements in place, you still need to enable Redis under Inte
 1. If you wanted to expose the Wallabag UI directly (_required for the iOS/Android apps_), you could remove the oauth2_proxy from the design, and move the traefik-related labels directly to the wallabag container. You'd also need to add the traefik_public network to the wallabag container. I found the iOS app to be unreliable and clunky, so elected to leave my oauth_proxy enabled, and to simply use the webUI on my mobile devices instead. YMMMV.
 2. I've not tested the email integration, but you'd need an SMTP server listening on port 25 (_since we can't change the port_) to use it

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -144,7 +144,7 @@ Log into your new instance at https://**YOUR-FQDN**, with user "root" and the pa

 1. If you wanted to expose the Wekan UI directly, you could remove the oauth2_proxy from the design, and move the traefik-related labels directly to the wekan container. You'd also need to add the traefik network to the wekan container.

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏

@@ -103,7 +103,7 @@ Browse to your new browser-cli-terminal at https://**YOUR-FQDN**. Authenticate w
 1. You could set SSHHOST to the IP of the "docker0" interface on your host, which is normally 172.17.0.1. (_Or run ```/sbin/ip route|awk '/default/ { print $3 }'``` in the container_) This would then provide you the ability to remote-manage your swarm with only web access to Wetty.
 2. The inclusion of Wetty was due to the efforts of @gpulido in our [Discord server](http://chat.funkypenguin.co.nz). Thanks Gabriel!

-### Tip your waiter (donate) 👏
+### Tip your waiter (support me) 👏

 Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏