Cloudron Forum

Thank You!

Good idea. We already do this in our appstore pipeline using cloudron appstore verify-manifest . I have added cloudrons versions verify for the next release to match this.

@scooke said: the forums or help have been very very weak, or actually non-existent (no one knows what went wrong and how to fix it). This is a very good and important point. Aside from mostly Just Working (and apps that are maintained and updated promptly), one of the best things about Cloudron is how amazingly good the support is, both from staff and from the rest of the users here on the forum.

So for sshfs mostly we just do a local sshfs (fuse) mount point and then the backup strategy runs exactly the same way as for all other backup targets. So that code is not specific. However if you use rsync with hardlink support, then sshfs really can shine and for that we have added specific code paths to do the remote ssh login and create the hardlinks on the server directly, which is the most common operation for incremental backups. This speeds up the backup process a lot. I am writing this, since above it seems to be about that optimized code path, which is doing the ssh login first and then runs the cp on the remote host (not your Cloudron).

@timconsidine Probably? Not sure. By and large, if it doesn't show up in my Cloudon App Store I don't install it (with the exception of some of your apps!).

@creative567145 thanks for the info, yes that would be the easiest way. Sounds like they need to manage flavors

@dantheman thanks for the write up. It looks like there are fans of this and firezone. I do not know enough to know what would be best, but I love this as an option to provide apps to specific users AND also as a means of backing things up locally.

@doodlemania2 said: I could start maybe looking to package the Rust one RustFS has already been packaged by the Cloudron team. It's in the app store. But note that it's still in Alpha.

Hi guys, I think we need to revive this post again: The Rocket.Chat Apps Engine is broken on both Cloudron package versions 3.1.0 (upstream 8.2.1) and 3.2.0 (upstream 8.3.1). No marketplace apps can be installed or run. Error logs: error: failed reading lockfile '/app/code/bundle/programs/server/npm/node_modules/@rocket.chat/apps-engine/deno-runtime/deno.lock' Caused by: Error getting response at https://registry.npmjs.org/@msgpack/msgpack for package "@msgpack/msgpack": An npm specifier not found in cache: "@msgpack/msgpack", --cached-only is specified. Root cause: The deno.lock file is located in /app/code/, which is on the read-only Docker image layer. When Deno tries to resolve the @msgpack/msgpack npm dependency, it can't find it in cache and can't update the lockfile because the filesystem is read-only (Read-only file system, os error 30). This means the Deno runtime can't start app subprocesses, so all marketplace apps (e.g. Giphy) fail with compiler errors and crash-loop. Steps to reproduce: Install or update to Rocket.Chat 3.1.0 or 3.2.0 on Cloudron Go to Admin > Apps > Marketplace Try to install any app (e.g. Giphy) Installation fails with "The App had compiler errors, can not enable it" Suggested fix: Either pre-cache the @msgpack/msgpack npm package in the Docker image at build time, or move the Deno cache/lockfile to a writable location (e.g. /app/data/ or /tmp/). Thanks!

sfeldkamp said: Hey everyone! I've published this as a community app. Currently only a "testing" version (how does that work anyway?), so please don't add it to the Community Apps topic just yet. Would love to get some feedback on it and see if any issues are discovered. https://github.com/sfeldkamp/cloudron-bluesky-pds This implementation has a critical bug in it that prevents an account alias from being updated or account migration to another PDS, because of the federated nature of the network, these accounts can't be fixed by fixing the app. I've "unpublished" the community app by removing the CloudronVersions.json file from the repository main branch. I've added information to the github project readme and archived it to prevent any further installations. I've requested that the app be removed from the Community Apps index.

@joseph I shall kill that monster and eradicate its remains