Duplicacy windows preference file update#
Duplicacy windows preference file driver#
Duplicacy windows preference file free#

The only thing going on at night was…Nightly Channel Optimizations. I was noticing it was falling off at night, which was odd. The good news though is that I was able to fix it again for the time being! It lasted many months, but something changed (unifi firmware, printer firmware, who knows). **Update April-ish 2023** So at some point in the past, the printer began falling off the network again. Nginx-ingress controller allows exposing of TCP ports, but doesn’t have a way of securing them with TLS protections (via ACME/Let’s Encrypt automation).The Owntracks client will buffer requests until it can sync. Unless you want realtime tracking, you don’t need to expose your MQTT broker to the internet.It appears as if they changed the timestamp name and/or no longer include the unix epoch timestamp anymore The owntracks script to import your Google Timeline doesn’t work anymore.Otherwise it defaults to something random When using MQTT, be sure to set the Tracker ID to something you want in the Identification section.On the owntracks client, flipping between MQTT and HTTP changes all of the settings – including the locationDisplacement and locationInterval settings.For versions > 2.0 in eclipse mosquitto MQTT, you need to define a config file for accessing the broker from anywhere other than localhost.If you want to use HTTP POST method instead of MQTT on the Owntracks recorder, set OTR_PORT=0.In the interim, here are some quick things I learned along the way:

Once I’ve gotten my setup a bit more production ready I’ll probably post the code. I’m not going to lie, the documentation definitely leaves a bit to the reader to figure out. There’s a lot of complaints about how difficult it is to get Owntracks setup. I do feel as if I need to take another look at traccar, but the table is below – you can mix/match the clients and the backends to a certain extent: Component This is primarily due to a few things a) decent updates b) a mobile app that only updates when it needs to…saving battery. Ultimately I think I’ve landed on owntracks. I had already set the auto-delete to any activity over 3 months, but I really do like seeing all that data. After receiving my latest google timeline email, I realized this was a good next area to focus on.

Duplicacy windows preference file free#

Over the past few years, I’ve been moving to more of a self-hosted model instead of using free services where I am the product (aka my data). I’m just thankful it’s back up and running! Published April 5, 2023 Sadly, there didn’t appear to be a way to do that after the restore, and tbh I didn’t look to see what version was listed as the Engine Image after the restore.

Duplicacy windows preference file update#

Once the volume is successfully restored and running, you can then upgrade to the latest version via the update steps, and update the engine on the volume. So, note to self (and others) – when restoring a longhorn volume from backup, make sure you are running the same version as from when the backup was taken. So yes, the error message was factual, if not incredibly frustrating.

Needless to say, the backups were on engine 1.4.0 (driver), but I only had 1.4.1 (driver) running as I was never prompted to upgrade the engine on the volume when restoring it. During any upgrades of longhorn, you must do an engine upgrade to the volume. However, the old cluster was still on 1.4.0, as were the backups. Well, lo-and-behold it was because when I built the new cluster, I decided to use the newest version of longhorn – 1.4.1 – as you do.

This was super odd though, I could create a new PVC with the same longhorn StorageClass and it would mount.

Duplicacy windows preference file driver#

It kept throwing the error Attach failed for volume : CSINode does not contain driver The volume restored properly, and I was able to recreate the PVC with the same name, but the deployment kept complaining about it and my Influx DB wouldn’t mount the drive. Thankfully, I had tested most of this prior to becoming reliant on longhorn, so I knew the backup and restore process worked well – just point the backTarget variable for longhorn on the new cluster to the same place as the old cluster and magic happens. This isn’t really a post about that, but long story short, it’s because of how microk8s does a non-existant job of updating addons, and you basically have to use the DNS (coreDNS) addon as I could never get that to work as a normal helm chart (even with updating the kubelet config).Īnyways as part of that change, I need to create a new cluster, get longhorn running, and restore the volumes it was running in the old cluster. I’ve been doing a bit of housekeeping on the home k8s cluster, and one of the things I’m doing is moving from microk8s to k3s.