diff --git a/content/posts/tailscale-serve-docker-compose-sidecar/index.md b/content/posts/tailscale-serve-docker-compose-sidecar/index.md
index 2d590d0..83b179d 100644
--- a/content/posts/tailscale-serve-docker-compose-sidecar/index.md
+++ b/content/posts/tailscale-serve-docker-compose-sidecar/index.md
@@ -45,7 +45,7 @@ miniflux.runtimeterror.dev {
 
 *and so on...* You get the idea. This approach works well for services I want/need to be public, but it does require me to manage those DNS records and keep track of which app is on which port. That can be kind of tedious.
 
-And I don't really need all of these services to be public. Not because they're particularly sensitive, but I just don't really have a reason to share my personal [Miniflux](https://github.com/miniflux/v2) or [CyberChef](https://github.com/gchq/CyberChef) instances with the world at large. Those would be great candidates to serve with [Tailscale Serve](/tailscale-ssh-serve-funnel#tailscale-serve) so they'd only be available on my tailnet. Of course, with that setup I'd have to differentiate the services based on external port numbers since they'd all be served with the same hostname. That's not ideal either.
+And I don't really need all of these services to be public. Not because they're particularly sensitive, but I just don't really have a reason to share my personal [Miniflux](https://github.com/miniflux/v2) or [CyberChef](https://github.com/gchq/CyberChef) instances with the world at large. Those would be great candidates to proxy with [Tailscale Serve](/tailscale-ssh-serve-funnel#tailscale-serve) so they'd only be available on my tailnet. Of course, with that setup I'd then have to differentiate the services based on external port numbers since they'd all be served with the same hostname. That's not ideal either.
 
 ```shell
 sudo tailscale serve --bg --https 8443 8180 # [tl! .cmd]
@@ -58,14 +58,14 @@ https://tsdemo.tailnet-name.ts.net:8443/
 |-- proxy http://127.0.0.1:8080
 ```
 
-It would be really great if I could directly attach each container to my tailnet and then access the apps with addresses like `https://miniflux.tailnet-name.ts.net` or `https://cyberchef.tailnet-name.ts.net`. Tailscale does provide an [official Tailscale image](https://hub.docker.com/r/tailscale/tailscale) which seems like it should make this a really easy problem to address. It runs in userspace by default (neat!), and [even seems to accept a `TS_SERVE_CONFIG` parameter](https://github.com/tailscale/tailscale/blob/5812093d31c8a7f9c5e3a455f0fd20dcc011d8cd/cmd/containerboot/main.go#L43) to configure Tailscale Serve... unfortunately, I haven't been able to find any documentation about how to create the required `ipn.ServeConfig` file to be able to use of that. I also struggled to find guidance on how to actually connect a Tailscale sidecar to an app container in the first place.
+It would be really great if I could directly attach each container to my tailnet and then access the apps with addresses like `https://miniflux.tailnet-name.ts.net` or `https://cyberchef.tailnet-name.ts.net`. Tailscale does provide an [official Tailscale image](https://hub.docker.com/r/tailscale/tailscale) which seems like it should make this a really easy problem to address. It runs in userspace by default (neat!), and [even seems to accept a `TS_SERVE_CONFIG` parameter](https://github.com/tailscale/tailscale/blob/5812093d31c8a7f9c5e3a455f0fd20dcc011d8cd/cmd/containerboot/main.go#L43) to configure Tailscale Serve... unfortunately, I haven't been able to find any documentation about how to create the required `ipn.ServeConfig` file to be able to use of that.
 
 And then I came across [Louis-Philippe Asselin's post](https://asselin.engineer/tailscale-docker) about how he set up Tailscale in Docker Compose. When he wrote his post, there was even less documentation on how to do this stuff, so he used a [modified Tailscale docker image](https://github.com/lpasselin/tailscale-docker) with a [startup script](https://github.com/lpasselin/tailscale-docker/blob/c6f8d75b5e1235b8dbeee849df9321f515c526e5/images/tailscale/start.sh) to handle some of the configuration steps. His repo also includes a [helpful docker-compose example](https://github.com/lpasselin/tailscale-docker/blob/c6f8d75b5e1235b8dbeee849df9321f515c526e5/docker-compose/stateful-example/docker-compose.yml) of how to connect it together.
 
 I quickly realized I could modify his startup script to take care of my Tailscale Serve need. So here's how I did it.
 
 ### Docker Image Description
-My image will start out the same as Louis-Philippe's:
+My image starts out the same as Louis-Philippe's:
 
 ```Dockerfile
 # torchlight! {"lineNumbers": true}
@@ -81,9 +81,9 @@ The `start.sh` script has a few tweaks for brevity/clarity, and also adds a bloc
 #!/bin/ash
 trap 'kill -TERM $PID' TERM INT
 echo "Starting Tailscale daemon"
-tailscaled --tun=userspace-networking --statedir="${TS_STATEDIR}" ${TS_OPT} &
+tailscaled --tun=userspace-networking --statedir="${TS_STATE_DIR}" ${TS_TAILSCALED_EXTRA_ARGS} &
 PID=$!
-until tailscale up --authkey="${TS_AUTHKEY}" --hostname="${TS_HOSTNAME}"; do
+until tailscale up --authkey="${TS_AUTHKEY}" --hostname="${TS_HOSTNAME}" ${TS_EXTRA_ARGS}; do
   sleep 0.1
 done
 tailscale status
@@ -101,7 +101,7 @@ fi
 wait ${PID}
 ```
 
-That script will start the `tailscaled` daemon in userspace mode, and it will store the Tailscale state in a user-defined location. It will then use a supplied [pre-auth key](https://tailscale.com/kb/1085/auth-keys) to bring up the new Tailscale node.
+This script starts the `tailscaled` daemon in userspace mode, and it tells the daemon to store its state in a user-defined location. It then uses a supplied [pre-auth key](https://tailscale.com/kb/1085/auth-keys) to bring up the new Tailscale node and set the hostname.
 
 If both `TS_SERVE_PORT` and `TS_FUNNEL` are set, the script will publicly proxy the designated port with Tailscale Funnel. If only `TS_SERVE_PORT` is set, it will just proxy it internal to the tailnet with Tailscale Serve.
 
@@ -110,7 +110,7 @@ I'm using [this git repo](https://github.com/jbowdre/tailscale-docker/) to track
 On that note...
 
 ### Compose Configuration Description
-There's also a [sample `docker-compose.yml`](https://github.com/jbowdre/tailscale-docker/blob/a996ea8d28d1357beb4eea65cff7d024ba94c8e3/docker-compose-example/docker-compose.yml) in the repo to show how to use the image:
+There's also a [sample `docker-compose.yml`](https://github.com/jbowdre/tailscale-docker/blob/54da987ff5b132b75ea051a0787ec686c7efeb64/docker-compose-example/docker-compose.yml) in the repo to show how to use the image:
 
 ```yaml
 # torchlight! {"lineNumbers": true}
@@ -122,7 +122,9 @@ services:
     environment:
       TS_AUTHKEY: ${TS_AUTHKEY:?err} # from https://login.tailscale.com/admin/settings/authkeys
       TS_HOSTNAME: ${TS_HOSTNAME:-ts-docker}
-      TS_STATEDIR: "/var/lib/tailscale/" # store ts state in a local volume
+      TS_STATE_DIR: "/var/lib/tailscale/" # store ts state in a local volume
+      TS_TAILSCALED_EXTRA_ARGS: ${TS_TAILSCALED_EXTRA_ARGS:-} # optional extra args to pass to tailscaled
+      TS_EXTRA_ARGS: ${TS_EXTRA_ARGS:-} # optional extra flags to pass to tailscale up
       TS_SERVE_PORT: ${TS_SERVE_PORT:-} # optional port to proxy with tailscale serve (ex: '80')
       TS_FUNNEL: ${TS_FUNNEL:-} # if set, serve publicly with tailscale funnel
     volumes:
@@ -138,6 +140,8 @@ The variables can be defined in a `.env` file stored alongside `docker-compose.y
 # torchlight! {"lineNumbers": true}
 TS_AUTHKEY=tskey-auth-somestring-somelongerstring
 TS_HOSTNAME=tsdemo
+TS_TAILSCALED_EXTRA_ARGS=
+TS_EXTRA_ARGS=--ssh
 TS_SERVE_PORT=8080
 TS_FUNNEL=1
 ```
@@ -146,17 +150,21 @@ TS_FUNNEL=1
 | --- | --- | --- |
 | `TS_AUTHKEY` | `tskey-auth-somestring-somelongerstring` | used for unattended auth of the new node, get one [here](https://login.tailscale.com/admin/settings/keys) |
 | `TS_HOSTNAME` | `tsdemo` | optional Tailscale hostname for the new node |
-| `TS_STATEDIR` | `/var/lib/tailscale/` | required directory for storing Tailscale state, this should be mounted to the container for persistence |
+| `TS_STATE_DIR` | `/var/lib/tailscale/` | required directory for storing Tailscale state, this should be mounted to the container for persistence |
+| `TS_TAILSCALED_EXTRA_ARGS` | `--verbose=1` | optional additional [flags](https://tailscale.com/kb/1278/tailscaled#flags-to-tailscaled) for `tailscaled` |
+| `TS_EXTRA_ARGS` | `--ssh` | optional additional [flags](https://tailscale.com/kb/1241/tailscale-up) for `tailscale up` |
 | `TS_SERVE_PORT` | `8080` | optional application port to expose with [Tailscale Serve](https://tailscale.com/kb/1312/serve) |
 | `TS_FUNNEL` | `1` | if set (to anything), will proxy `TS_SERVE_PORT` **publicly** with [Tailscale Funnel](https://tailscale.com/kb/1223/funnel) |
 
 
 - If you want to use Funnel with this configuration, it might be a good idea to associate the [Funnel ACL policy](https://tailscale.com/kb/1223/funnel#tailnet-policy-file-requirement) with a tag (like `tag:funnel`), as I discussed a bit [here](/tailscale-ssh-serve-funnel/#tailscale-funnel). And then when you create the [pre-auth key](https://tailscale.com/kb/1085/auth-keys), you can set it to automatically apply the tag so it can enable Funnel.
-- It's very important that the path designated by `TS_STATEDIR` is a volume mounted into the container. Otherwise, the container will lose its Tailscale configuration when it stops. That could be inconvenient.
-- Tying `network_mode` on the application container back to the `service:tailscale` definition is the magic that lets the sidecar proxy traffic for the app. This way the two containers effectively share the same network interface, allowing them to share the same ports. So port `8080` on the app container is available on the tailscale container, and that allows `tailscale serve --bg 8080` to work.
+- It's very important that the path designated by `TS_STATE_DIR` is a volume mounted into the container. Otherwise, the container will lose its Tailscale configuration when it stops. That could be inconvenient.
+- Linking `network_mode` on the application container back to the `service:tailscale` definition is the magic that lets the sidecar proxy traffic for the app. This way the two containers effectively share the same network interface, allowing them to share the same ports. So port `8080` on the app container is available on the tailscale container, and that enables `tailscale serve --bg 8080` to work.
 
 ### Usage
-To tie it all together, here are the steps that I took to serve up a quick CyberChef instance on my tailnet.
+
+#### CyberChef
+To tie it all together, here are the steps that I took to publish a CyberChef instances with Funnel.
 
 I started by going to the [Tailscale Admin Portal](https://login.tailscale.com/admin/settings/keys) and generating a new auth key. I gave it a description, ticked the option to pre-approve whatever device authenticates with this key (since I have [Device Approval](https://tailscale.com/kb/1099/device-approval) enabled on my tailnet). I also used the option to auto-apply the `tag:internal` tag I used for grouping my on-prem systems as well as the `tag:funnel` tag I use for approving Funnel devices in the ACL.
 
@@ -170,26 +178,29 @@ I'll use that new key as well as the knowledge that CyberChef is served by defau
 
 ```shell
 # torchlight! {"lineNumbers": true}
-# .env
 TS_AUTHKEY=tskey-auth-somestring-somelongerstring
 TS_HOSTNAME=cyberchef
+TS_EXTRA_ARGS=--ssh
 TS_SERVE_PORT=8000
 TS_FUNNEL=true
 ```
 
-And I can add the corresponding `docker-compose.yml` to go with it:
+And I can add the corresponding `docker-compose.yml` to go with it. Note that I'm also pulling the `tailscale-docker` image from GHCR instead of building it locally as in the earlier example:
 
 ```yaml
 # torchlight! {"lineNumbers": true}
-# docker-compose.yml
 services:
   tailscale:
-    image: ghcr.io/jbowdre/tailscale-docker:latest
+    build: # [tl! --:1 .nocopy:1]
+      context: ./image/
+    image: ghcr.io/jbowdre/tailscale-docker:latest # [tl! ++ reindex(-2)]
     container_name: cyberchef-tailscale
     environment:
       TS_AUTHKEY: ${TS_AUTHKEY:?err}
       TS_HOSTNAME: ${TS_HOSTNAME:-ts-docker}
-      TS_STATEDIR: "/var/lib/tailscale/"
+      TS_STATE_DIR: "/var/lib/tailscale/"
+      TS_TAILSCALED_EXTRA_ARGS: ${TS_TAILSCALED_EXTRA_ARGS:-}
+      TS_EXTRA_ARGS: ${TS_EXTRA_ARGS:-}
       TS_SERVE_PORT: ${TS_SERVE_PORT:-}
       TS_FUNNEL: ${TS_FUNNEL:-}
     volumes:
@@ -200,3 +211,86 @@ services:
     restart: unless-stopped
     network_mode: service:tailscale
 ```
+
+I can just bring it online like so:
+```shell
+docker compose up -d # [tl! .cmd .nocopy:1,4]
+[+] Running 3/3
+ ✔ Network cyberchef_default      Created
+ ✔ Container cyberchef-tailscale  Started
+ ✔ Container cyberchef            Started
+```
+
+And after ~10 minutes or so (it sometimes takes a bit longer for the DNS and SSL to start working outside the tailnet), I'll be able to hit the instance at `https://cyberchef.tailnet-name.ts.net` from anywhere on the web.
+
+#### Miniflux
+Similarly, here's my setup for serving Miniflux internal to my tailnet.
+
+`.env`:
+
+```shell
+# torchlight! {"lineNumbers": true}
+DB_USER=db-username
+DB_PASS=db-passw0rd
+ADMIN_USER=sysadmin
+ADMIN_PASS=hunter2
+TS_AUTHKEY=tskey-auth-somestring-somelongerstring
+TS_HOSTNAME=miniflux
+TS_EXTRA_ARGS=--ssh
+TS_SERVE_PORT=8080
+```
+
+`docker-compose.yml`:
+```yaml
+# torchlight! {"lineNumbers": true}
+services:
+  tailscale:
+    image: ghcr.io/jbowdre/tailscale-docker:latest
+    container_name: miniflux-tailscale
+    environment:
+      TS_AUTHKEY: ${TS_AUTHKEY:?err}
+      TS_HOSTNAME: ${TS_HOSTNAME:-ts-docker}
+      TS_STATE_DIR: "/var/lib/tailscale/"
+      TS_TAILSCALED_EXTRA_ARGS: ${TS_TAILSCALED_EXTRA_ARGS:-}
+      TS_EXTRA_ARGS: ${TS_EXTRA_ARGS:-}
+      TS_SERVE_PORT: ${TS_SERVE_PORT:-}
+      TS_FUNNEL: ${TS_FUNNEL:-}
+    volumes:
+      - ./ts_data:/var/lib/tailscale/
+  miniflux:
+    image: miniflux/miniflux:latest
+    container_name: miniflux
+    depends_on:
+      db:
+        condition: service_healthy
+    environment:
+      - DATABASE_URL=postgres://${DB_USER}:${DB_PASS}@db/miniflux?sslmode=disable
+      - RUN_MIGRATIONS=1
+      - CREATE_ADMIN=1
+      - ADMIN_USERNAME=${ADMIN_USER}
+      - ADMIN_PASSWORD=${ADMIN_PASS}
+    network_mode: "service:tailscale"
+  db:
+    image: postgres:15
+    container_name: miniflux-db
+    environment:
+      - POSTGRES_USER=${DB_USER}
+      - POSTGRES_PASSWORD=${DB_PASS}
+    volumes:
+      - ./mf_data:/var/lib/postgresql/data
+    healthcheck:
+      test: ["CMD", "pg_isready", "-U", "${DB_USER}"]
+      interval: 10s
+      start_period: 30s
+```
+
+This one doesn't have `TS_FUNNEL` defined in `.env` so it will just use Tailscale Serve internally.
+
+```shell
+docker compose up -d # [tl! .cmd .nocopy:1,5]
+[+] Running 4/4
+ ✔ Network miniflux_default       Created
+ ✔ Container miniflux-db          Started
+ ✔ Container miniflux-tailscale   Started
+ ✔ Container miniflux             Created
+```
\ No newline at end of file