InfiniTime is a fast open-source firmware for the PineTime smartwatch with many features, written in modern C++.

The previous release was over a year ago, but this one introduces some exciting new features. It seems a lot of effort went into improving background tasks because heart rate tracking and the stopwatch will each now work as expected in the background. Hopefully this doesn't hurt the amazing battery life too much!

cross-posted from: https://lemmy.ml/post/16693054

Is there a feature in a CI/CD pipeline that creates a snapshot or backup of a service's data prior to running a deployment? The steps of a ideal workflow that I am searching for are similar to:

1. CI tool identifies new version of service and creates a pull request
2. Manually merge pull request
3. CD tool identifies changes to Git repo
   1. CD tool creates data snapshot and/or data backup
   2. CD tool deploys update
4. Issue with deployment identified that requires rollback
   1. Git repo reverted to prior commit and/or Git repo manually modified to prior version of service
   2. CD tool identifies the rolled back version
      1. (OPTIONAL) CD tool creates data snapshot and/or data backup
      2. CD tool reverts to snapshot taken prior to upgrade
      3. CD tool deploys service to prior version per the Git repo
5. (OPTIONAL) CD tool prunes data snapshot and/or data backup based on provided parameters (eg - delete snapshots after _ days, only keep 3 most recently deployed snapshots, only keep snapshots for major version releases, only keep one snapshot for each latest major, minor, and patch version, etc.)

Is there a feature in a CI/CD pipeline that creates a snapshot or backup of a service's data prior to running a deployment? The steps of a ideal workflow that I am searching for are similar to:

1. CI tool identifies new version of service and creates a pull request
2. Manually merge pull request
3. CD tool identifies changes to Git repo
   1. CD tool creates data snapshot and/or data backup
   2. CD tool deploys update
4. Issue with deployment identified that requires rollback
   1. Git repo reverted to prior commit and/or Git repo manually modified to prior version of service
   2. CD tool identifies the rolled back version
      1. (OPTIONAL) CD tool creates data snapshot and/or data backup
      2. CD tool reverts to snapshot taken prior to upgrade
      3. CD tool deploys service to prior version per the Git repo
5. (OPTIONAL) CD tool prunes data snapshot and/or data backup based on provided parameters (eg - delete snapshots after _ days, only keep 3 most recently deployed snapshots, only keep snapshots for major version releases, only keep one snapshot for each latest major, minor, and patch version, etc.)

I'm trying to find a video that demonstrated automated container image updates for Kubernetes, similar to Watchtower for Docker. I believe the video was by @[email protected] but I can't seem to find it. The closest functionality that I can find to what I recall from the video is k8s-digester. Some key features that were discussed include:

• Automatically update tagged version number (eg - Image:v1.1.0 -> Image:v1.2.0)
• Automatically update image based on tagged image's digest for tags like "latest" or "stable"
• Track container updates through modified configuration files
  • Ability to manage deploying updates through Git workflows to prevent unwanted updates
• Minimal (if any) downtime
• This may not have been in the video, but I believe it also discussed managing backups and rollback functionality as part of the upgrade process

While this tool may be used in a CI/CD pipeline, its not limited exclusively to Git repositories as it could be used to monitor container registries from various people or organizations. The tool/process may have also incorporated Ansible.

If you don't know which video I'm referring to, do you have any suggestions on how to achieve this functionality?

EDIT: For anyone stumbling on this thread, the video was Meet Renovate - Your Update Automation Bot for Kubernetes and More! by @[email protected], which discusses the Kubernetes tool Renovate.

I've been looking for something "official" from the Librewolf team regarding running Librewolf in Docker, but I haven't found much. There are a few initiatives that seem to support Librewolf Docker containers (eg Github, Docker Hub), but they don't seem to be referenced much nor heavily used. However, maybe the reason I don't see it much is that there are better ways to achieve what I'm looking for.

• Better separation from daily OS environment and regular browsing environment
• Ability to run multiple instances privacy friendly browser and isolate each instance for particular use cases
• Configure each instance to be run over different VPNs (or no VPN at all)

Is there a way to best achieve this?