Your setup really sounds interesting to me and I would love to have something similar setup. Can you please elaborate on this a bit?
Here’s how it looks like and how exactly I use it…
Like a lot of other services, I self-host rwtxt using Docker on my home cloud (using an Odroid HC2). It sits behind an Caddy reverse proxy and the entry in the docker-compose services section looks like this:
rwtxt: container_name: rwtxt build: https://github.com/schollz/rwtxt.git restart: unless-stopped volumes: - /data/rwtxt:/data environment: - TZ=Europe/Berlin
I only need to run
docker-compose build rwtxt and
docker-compose up -d rwtxt sometimes and it builds and starts the Docker image using the
Dockerfile directly from the official repository.
If I wanted to make my rwtxt instance fully private, I could have setup basic authentication using Caddy, but I decided not to do so, because I sometimes use it to share (for example) drafts with others to proofread them.
Inside rwtxt I created a domain (it’s like an account with name and password) for my journal and made sure to not enable the option to make it public. That way my journal should be private, unless someone guesses the correct password (it’s a long auto-generated one, so very unlikely) or hacks either rwtxt or my server, but I hope that won’t happen. For every new diary entry, I create a new entry in the domain.
For other needs (like sharing drafts for new blog posts), I use another domain (with a password, but the public option enabled) or the “/public” domain.