Nimmo

Yea, after another hour today I’ve decided that my time is better spent elsewhere, so I’m just going to stick with Navidrome and not worry too much about losing out on the federated music idea for now.

I gave up on funk whale about 6 months ago and was loving navidrome, but hadn’t realised the lack of library separation. Thankfully that doesn’t bother me too much. I’ll give this another go and see how I get on though if I can find some time over the weekend

I’ve got my instance of matrix working with voice calls. It’s not built in, but it’s just another service in my compose file alongside the bridges I use to have my unified chat app.

I’m using coturn and it just works when doing voice and video calls with federated users.

I think I’ve seen people using jitsi as well, so it seems there are many options available

Oh, I’m fine with my setup, I have a couple of external servers that can monitor all my web accessible stuff with kuma and then I’ve got another local one to monitor my non-web accessible stuff.

Thanks for those tips though, definitely useful to consider other options

On the uptime monitoring I’ve been quite happy with uptime kuma, but… If you put it on the same host that’s down… Well, that’s not going to work :p (I nearly made that mistake)

That sounds like a rather unpleasant experience indeed! I’ve never looked into it in more detail than scrolling through the lsio containers they offer, so thanks for that insight and saving me a headache in case I get around to a similar project I’ve also been meaning to embark upon

Could Snipe it work for you? https://docs.linuxserver.io/images/docker-snipe-it/

It looks like an asset management tool. The description copied and pasted from above reads:Snipe-it makes asset management easy. It was built by people solving real-world IT and asset management problems, and a solid UX has always been a top priority. Straightforward design and bulk actions mean getting things done faster

One time I ran out of disk space due to it having created since 200gb log files (not sure why that happened) then another time I think I broke something whilst moving from I’ve got to another. I can’t remember what else happened to break my instances but it was always big enough there I couldn’t restore it to working it after hours if work, so if just export the vaults from everyone’s machine, nuke it, start again and try to learn how I broke it so I didn’t do it again.

I believe I was the problem for most of them except the massive log files one, but still, it was probably my fault as the things usually are. (Guess whose wife has them well trained at accepting the blame 😋)

I pay my $10 license and a personal organisation license for bitwarden because I like their platform but after yet another irrecoverable loss of data (partly my fault for not sufficiently backing it up) I’ve moved over to vaultwarden for my family’s password management.

I don’t think I’ll stop supporting bitwarden even if I’m not using their platform directly though as I do like the service I’ve had from them for something like 4 or 5 years now.

I was going to say that the big downside to that would be a lack of any kind of version control, but I guess if you need that you can always use git and just commit changes there and (optionally) push them to a repository somewhere.

I chose to take down my production instance of lemmyz do a cp -r of it, update the docker compose file to specify the new version numbers for Lemmy and lemmy-ui plus change the port that the stack exposes and do a docker-compose pull && docker-compose up -d on that stack to check to see if it could all work. Thankfully it did, so I updated the production compose file and tada! I’m on 19.0 safely

Ooo, I’ll add that to one of my planka boards for “things to look at later” thanks for sharing

I’ve been using planka and have been quite happy with my experiences for the last couple of months.

Magic, thanks for posting this. I’ve been trying to find a good and clear explanation of that been going on since I started reading about people getting upset with unity during the week.

Fair points well made. I thought the 11th was a Wednesday and I’ve been off on holiday for a week or so, so brain no worky so good just now.

I’ll l go back under my lurking rock again.

I find it quite interesting that Ubisoft Montreal chose the same day as my employer to enforce 2 days in the office every week.

I’ll accept that there is a 1 in 356.25 chance that any employer will pick a specific day to enforce a return to office, but it does seem interesting that there would be 2 employers in different countries picking the same day. Is there something special about that day that makes it a special day to change where and how people work? (I know that there were events on 2001 that took place on this day, but that doesn’t seem too likely a reason to pick that particular day to enact this change)

That’s interesting, because I was finding guides for traefik and caddy but not nginx (specifically swag in my case)

The issue I was having, in case it helps you, is that I was trying to expose 8448 on my synapse container which doesn’t have SSL instead of on my SWAG container and then redirect to my synapse one.

I personally use gitea but there is also a community version of gitlab that has way more power than I need.

Gitea can import a repo from GitHub but I don’t know whether it can also push updates out as one never tried to do that.

I picked gitea as I didn’t need all of the extra power of gitlab and they were the first two options I found. I don’t deploy it using portainer but all of my stacks are set up as git repos in portainer and using the webhook feature it’ll auto pull and redeploy whenever I push to it

Testing with a comment

One method that many people use to hide their IP address of their host is to use Cloudflare for DNS, that way you don’t directly expose your IP address to the wider internet. A nice bonus to Clouldflare is that it’s free too! Just get yourself a domain, get Cloudflare set up to provide DNS for it and you’re golden.