I have the beginnings of a similar structure in my wiki but I wasn’t happy with the way I was tracking todos, fixes, changes.

Try not to have info spread out too much or maintaining all the pieces will become a chore. Make it simple and easy to keep up.

I think you’re right on this point. I have a tendency to over-complicate things and that leads to them getting scrapped or neglected.

I’ll definitely take a look.

I do have a couple github repos for various things (ansible, scripts, dns). My plan for general documentation is the wiki. I’ve started the work on that but it’s far from complete (those get saved in markdown and synced to github). Maybe the simplest solution is the one I’m avoiding. Just putting it all in a readme/changelog.

It can be in git even if you’re not doing ‘config as code’ or ‘infrastructure as code’ yet/ever.

I have some of this. I have an ansible playbook I use to do initial vm/lxc setup and I’ve built out a number of roles. But none of my systems are to a point were I could just delete the vm, spin a new one up, point ansible at it, and pickup where I left off.

The one thing I have that probably closest to this is my internal BIND zones, which double as my IPAM. I’ve been fairly diligent about committing changes and documenting what the change was.

You are 100% correct. I’m on the quest to find the method that resonates with me that I’ll keep up with.

I know you don’t want a ticket system but I’m just curious what other people will suggest because I’m in the same boat as you.

I’m not opposed to a ticketing system but I’d want something pretty simple. Last one I tried was GLPI because I thought the inventory mgmt + ticketing would be useful but it was just way too much.

Currently I haphazardly use Joplin to take very loose notes and sync them to Nextcloud.

I’m currently using Wiki.js (synced to GitHub) in an attempt to document things. I’ve played with a changelog section but it’s like a stream of consciousness and I’m not real happy with the layout.

I do also use SnipeIT to track all my hardware and parts, which allows you to add notes and service history against the hardware asset.

That looks cool. I may check that out.

Thanks

My needs are pretty simple. I’ll take a look. Thanks.

After reading this thread I’m apparently not paranoid enough.

Internet facing services are on their own firewalled vlan (dmz), behind a rev proxy, and I have crowdsec running on the proxy and router.

Anything that can get away with putting up on a vps I have (e.g. this Lemmy server). But some things have storage/compute requirements I’m not willing to shell out for.

It also breaks android auto for me.

I’m checking this out to see if it’s useful to me. I can see where being able to drop straight into a shell on a docker container would be handy. My only real gripe is that I can’t use it to connect to my free-tier oracle linux cloud VMs because they deploy OracleLinux out of the box.

I don’t begrudge you wanting to make a living from your work. It’s just frustrating.

I am going to try and live in it for a week or two and we’ll see if it sticks.

I was able to get the rclone mount on boot via a systemd unit without much trouble.

I even managed to drag it kicking and screaming into a docker volume that I mounted as an external volume to the Nextcloud AIO stack. It still refused to allow me to add it as a backup directory.

I think I’m throwing in the towel with getting Nextcloud to back it up via the built in mechanism. I’ll just schedule a separate job (cron/systemd) that runs shortly after the Nextcloud backup. It should be close enough for my purposes.

Did you try to mount your bucket on your host system via rclone?

I did. That’s where I ran into the problems.

I would mount it on the host system and add an additional volume in your docker-compose.yml

I’m embarrassed to admit I didn’t try this. I think I was too far into the weeds the other night. I’ll give this a try.

If it works, I’m thinking I’ll need to setup a systemd service to auto-mount the path on boot and set it as a dependency in docker so docker doesn’t start before it?

Be aware your backup is useless, if you don’t backup nextclouds database when using a bucket as primary storage ☝🏻

Understood. My hope was to mount the bucket locally (ro) and have it backed up with the container backups using the built in borg backup option.

rclone sync b2:mybucket otherprovider:otherbucket

I’d prefer to have proper incremental backups not just a warm copy of the data.

Rclone can mount and backup almost everything. It is a swiss knife and I love it.

It seems to be very capable but I cannot make it work for my purposes. I fought with rclone/aio for a few hours yesterday trying to make it work.

I was, quite easily, able to mount the B2 bucket to a local path. I used the --allow-other option to make it available to the whole system. Everything was accessible via the CLI, but the Nextcloud AIO admin refused to allow me to add that path to the backup job. I was unable to find any logs that indicated why. If I could get this working, I think, it would be ideal as the backups would be consistent.

I also tried using a couple of the serve options. The nfs option would launch but mounts would fail with protocol errors. I couldn’t get the docker plugin to sync up properly with docker. I haven’t tried the restic serve option yet. I can provide logs if requested.

Thanks for the help.

I’m not sure if there’s a correct way. What I’ve done in the past is use “ps” to find out what user the processes are running as.

Reads to me like the container it’s running as a user that doesn’t have permission to the volume path.

You can point it to any nfs file system you have exported on the file server. That’s entirely up to you.

Weird. I don’t remember my exact request but it was basically “send email on my personal domains” and they approved it.

I’m rather confused by the config you posted. The NFS config should all be down in the volumes: section the only thing you reference in the service section is the name of the volume you define and the path to mount in the container. Something like this (tho I’m guessing as to what should be what with your setup).

services:
  navidrome:
    container_name: navidrome
    image: deluan/navidrome:latest
    ports:
      - "4533:4533"
    environment:
      ND_SCANSCHEDULE: 1h
      ND_LOGLEVEL: info
    volumes:
      - /opt/navidrome/data:/data
      - music:/music
volumes:
  music:
    driver_opts:
      type: nfs
      o: "addr=XXX.XXX.XXX.XXX,nolock,soft,ro"
      device: ":/nfs/Shared Music"

What do you mean, “for personal notifications”? I have a bunch of alert notifications that route through SES back to me. Never had an issue.