Again thanks for taking the time to help and explain this to me

Yep this works

“origin=cloudsmith/caddy/stable”;

Unable to parse Unattended-Upgrade::Allowed-Origins. An error occurred: not enough values to unpack (expected 2, got 1)

// Automatically upgrade packages from these (origin:archive) pairs
//
// Note that in Ubuntu security updates may pull in new dependencies
// from non-security sources (e.g. chromium). By allowing the release
// pocket these get automatically pulled in.
Unattended-Upgrade::Allowed-Origins {
        "${distro_id}:${distro_codename}";
        "${distro_id}:${distro_codename}-security";
        // Extended Security Maintenance; doesn't necessarily exist for
        // every release and this system may not have it installed, but if
        // available, the policy for updates is such that unattended-upgrades
        // should also install from here by default.
        "${distro_id}ESMApps:${distro_codename}-apps-security";
        "${distro_id}ESM:${distro_codename}-infra-security";
        "${distro_id}:${distro_codename}-updates";
//      "${distro_id}:${distro_codename}-proposed";
//      "${distro_id}:${distro_codename}-backports";
        "origin=cloudsmith/caddy/stable";
};

Firstly thank you so much for explaing this for me.

“origin=Zabbix,codename=${distro_codename}”; //Zabbix Agent repository

I tried using this as a template for caddy

 500 https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version/main arm64 Packages
     release o=cloudsmith/caddy/stable,a=any-version,n=any-version,l=source=none,c=main,b=arm64
     origin dl.cloudsmith.io

I assume origin is:

o=cloudsmith/caddy/stable

When adding this rule

"origin=cloudsmith/caddy/stable,codename=${distro_codename}"; //Caddy repository

I get this error

Unable to parse Unattended-Upgrade::Allowed-Origins.
An error occurred: not enough values to unpack (expected 2, got 1)
Traceback (most recent call last):

https://pastebin.com/raw/7gtkRw7c

When changing the syntax to:

"cloudsmith/caddy/stable:${distro_codename}"; // Caddy

The error goes away.

Any ideas?

Update regarding virtual files has more quirks.

• You cannot move files or folders. If you try nextcloud will simply copy the files to new destinaiton while not moving.
• the nextcloud sync and virtual files refresh/update independently (a change may propigate to sync but not files and vice versa).

Also turns out the reason it was a github release was it is still in alpha 😅 .

deleted by creator

Update the stable client does have proper virtual file sync.

Regarding the previous virtual file sync system (.nextcloud) you had to enable experimental features to get it. The latest stable just has both versions of syncing and I missed the obsious vfs sync option.

The only downside to the new system is there isn’t a make file/folder available offline always option in the context menu (you can get around this by manually setting up synced folders but it is a little inconvient).

Nextcloud desktop client 3.13.0

Edit 2:

You need to grab the release from https://github.com/nextcloud-releases/desktop/releases/tag/v3.13.0

Specifically the vfs version Nextcloud-3.13.0-macOS-vfs.pkg

brew doesn’t really work

This is how it shows up for me on Nextcloud desktop client 3.13.0

Unfortunatly like syncthing nextcloud mac app also has the same file extension sync issue (they use .nextcloud).