Merge branch 'develop' into feature/cryptominer

manuscript/recipies/autopirate.md

@@ -121,4 +121,8 @@ Now work your way through the list of tools below, adding whichever tools your w
 * [Ombi](/recipies/autopirate/ombi/)
 * [End](/recipies/autopirate/end/) (launch the stack)
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/calibre-web.md

@@ -118,7 +118,7 @@ networks:
 
 ### Launch Calibre-Web
 
-Launch the Wekan stack by running ```docker stack deploy calibre-web -c <path -to-docker-compose.yml>```
+Launch the Calibre-Web stack by running ```docker stack deploy calibre-web -c <path -to-docker-compose.yml>```
 
 Log into your new instance at https://**YOUR-FQDN**. You'll be directed to the initial GUI configuraition. Set the first field (_Location of Calibre database_) to "_/books/_", and when complete, login using defaults username of "**admin**" with password "**admin123**".
 
@@ -127,4 +127,8 @@ 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](/recipies/nextcloud/), so that the desktop database (Calibre) can be kept synced with Calibre-Web.
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/cryptominer.md

@@ -1,8 +1,34 @@
+hero: We dig dig digga-dig dig!
+
 # CryptoMiner
 
-This is a diversion from my usual recipies - since a hardware-based crypto currency miner can't really use docker swarm :)
+This is a diversion from my usual recipes - since a hardware-based crypto currency miner can't really use a docker swarm :)
+
+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)
+
+![NAME Screenshot](../images/cryptominer.png)
+
+
+## Menu
+
+
+
+## Ingredients
+
+1. [Docker swarm cluster](/ha-docker-swarm/design/) with [persistent shared storage](/ha-docker-swarm/shared-storage-ceph.md)
+2. [Traefik](/ha-docker-swarm/traefik) configured per design
+3. Access to NZB indexers and Usenet servers
+4. DNS entries configured for each of the NZB tools in this recipe that you want to use
+
+## Preparation
+
+### Setup data locations
+
+
+
+## Your comments?
+
 
-![NAME Screenshot](../images/name.jpg)
 
 Details
 
@@ -30,8 +56,75 @@ You'll want to setup accounts at the following (if you use the URLs below, I get
 # For flashing
 https://bitcointalk.org/index.php?topic=1809527.0
 
+# Testing
 
+--
+/opt/minerhotel/bin/claymore/ethdcrminer64 -epool stratum+tcp://daggerhashimoto.usa.nicehash.com:3353 -ewal 394LeTTJFXkY6yGR95kY5q2Er68P81fDtv -epsw x -esm 3 -allpools 1 -estale 0 -dpool stratum+tcp://decred.usa.nicehash.com:3354 -dwal 394LeTTJFXkY6yGR95kY5q2Er68P81fDtv -di 012 -dcri 28 -cclock 1200 -cvddc 900 -mclock 2250 -mvddc 850 -tstop 85 -tt 65 -fanmin 10 -fanmax 60 -gser 5 -lidag 5 -asm 1
+---
 
+## Results of the flash
+
+```
+GPU #0: Ellesmere, 4078 MB available, 36 compute units
+GPU #1: Ellesmere, 4082 MB available, 36 compute units
+```
+
+Speed:
+```
+ETH: GPU0 30.115 Mh/s, GPU1 22.176 Mh/s
+```
+
+Power consumption (stock)
+```
+GFX Clocks and Power:
+        1750 MHz (MCLK)
+        1411 MHz (SCLK)
+        144.107 W (VDDC)
+        16.0 W (VDDCI)
+        171.161 W (max GPU)
+        172.209 W (average GPU)
+
+GPU Temperature: 67 C
+GPU Load: 100 %
+```
+
+Power consumption (flashed)
+
+```
+GFX Clocks and Power:
+        2050 MHz (MCLK)
+        1150 MHz (SCLK)
+        87.155 W (VDDC)
+        16.0 W (VDDCI)
+        117.152 W (max GPU)
+        116.1 W (average GPU)
+
+GPU Temperature: 62 C
+GPU Load: 100 %
+```
+
+R290 flash. Started with 290X elpida. Not elpida. Trying hynix.
+
+```
+[root@kvm ~]# ./atiflash -f -p 0 Insan1ty\ R9\ 390X\ BIOS\ v1.81/R9\ 290X/MEM\ MOD\ --\ ELPIDA/290X_ELPIDA_MOD_V1.8.rom
+Old SSID: E285
+New SSID: 9395
+Old P/N: 113-E285FOC-U005
+New P/N: 113-GRENADA_XT_C671_D5_8GB_HY_W
+Old DeviceID: 67B1
+New DeviceID: 67B0
+Old Product Name: C67111 Hawaii PRO OC GDDR5 4GB 64Mx32 300e/150m
+New Product Name: C67130 Grenada XT A0 GDDR5 8GB 128Mx32 300e/150m
+Old BIOS Version: 015.044.000.011.000000
+New BIOS Version: 015.049.000.000.000000
+Flash type: M25P10/c
+Burst size is 256
+20000/20000h bytes programmed
+20000/20000h bytes verified
+
+Restart System To Complete VBIOS Update.
+[root@kvm ~]#
+```
 
 
 ### Setup data locations

manuscript/recipies/duplicity.md

@@ -165,4 +165,8 @@ 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
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/emby.md

@@ -89,4 +89,8 @@ Log into your new instance at https://**YOUR-FQDN**, and complete the wizard-bas
 2. I used the LinuxServer docker container, even though still under "active development", to maintain consistency with the [Plex](/recipies/plex/) and [autopirate](/recipies/autopirate/) recipies.
 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.
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/ghost.md

@@ -70,4 +70,8 @@ Create your first administrative account at https://**YOUR-FQDN**/admin/
 [root@ds1 ghost]#
 ```
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/gitlab-runner.md

@@ -62,4 +62,8 @@ 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.
 
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/gitlab.md

@@ -134,4 +134,8 @@ 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?)
 
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/gollum.md

@@ -129,5 +129,8 @@ 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) 👏
 
-## Your comments?
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/homeassistant.md

@@ -132,4 +132,8 @@ 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!
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/huginn.md

@@ -144,5 +144,8 @@ 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) 👏
 
-## Your comments?
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/kanboard.md

@@ -106,5 +106,8 @@ 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) 👏
 
-## Your comments?
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/mail.md

@@ -171,4 +171,8 @@ 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)
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/miniflux.md

@@ -71,5 +71,8 @@ Log into your new instance at https://**YOUR-FQDN**. Default credentials are adm
 1. I chose [saghul/miniflux](https://hub.docker.com/r/saghul/miniflux/)'s over the "official" [miniflux/miniflux](https://hub.docker.com/r/miniflux/miniflux/) image, because currently the official image doesn't log to stdout (which you want, for docker logging commands), and because I have an expectation that nginx is more lightweight (faster) than apache.
 2. Find the bookmarklet under the "about" page. I know, it took me ages too.
 
+### Tip your waiter (donate) 👏
 
-## Your comments?
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/nextcloud.md

@@ -190,4 +190,8 @@ Then navigate to https://<your FQDN>/index.php/settings/admin/additional, scroll
 
 1. Since many of my other recipies 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).
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/owntracks.md

@@ -114,4 +114,8 @@ 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.
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/piwik.md

@@ -92,4 +92,8 @@ 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.
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/plex.md

@@ -98,4 +98,8 @@ 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
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/portainer.md

@@ -68,4 +68,8 @@ 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!
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/template.md

@@ -1,3 +1,5 @@
+hero: Heroic Hero
+
 # NAME
 
 Intro
@@ -10,7 +12,7 @@ Details
 
 1. [Docker swarm cluster](/ha-docker-swarm/design/) with [persistent shared storage](/ha-docker-swarm/shared-storage-ceph.md)
 2. [Traefik](/ha-docker-swarm/traefik) configured per design
-3. 3. DNS entry for the hostname you intend to use, pointed to your [keepalived](ha-docker-swarm/keepalived/) IP
+3. DNS entry for the hostname you intend to use, pointed to your [keepalived](ha-docker-swarm/keepalived/) IP
 
 ## Preparation
 
@@ -111,4 +113,8 @@ 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.
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/tiny-tiny-rss.md

@@ -135,4 +135,8 @@ 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".
 
-## Your comments?
+### Tip your waiter (donate) 👏
+
+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! 👏
+
+### Your comments? 💬

manuscript/recipies/wekan.md

@@ -143,5 +143,8 @@ 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) 👏
 
-## Your comments?
+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! 👏
+
+### Your comments? 💬