Cloudron Forum

Ah this is good information and indeed a likely a problem for rsync backups with a lot of files (not sure how the rate-limit turns out in the end though)

Works in Edge as well, thanks @fbartels

yeah you are right. That's a clean alternative. Thanks!

@chetbaker I couldn't figure how these two are related i.e API and permalinks... Do you know?

Since it is a static site generator, I guess you could also generate the assets locally and then push to a surfer instance.

Otherwise, it may be similar to github pages, which build the static assets on git push and then just serve those. For this you would probably build a custom Cloudron app, which knows how to build the assets.

If you want some CI/CD inspiration with GitLab + static asset hosting, you can look at our docs repo. It builds using mkdocs and then pushes the build to surfer . See https://git.cloudron.io/cloudron/docs/-/blob/master/.gitlab-ci.yml?ref_type=heads .

The build server is a separate VM running gitlab runner (but only costs around 5 a month).

Interesting, but check how the camera scan performs. QuickScan does a great job.

@docuseal this is great, thanks!

Sure. I didn't mention any of that because as the developer said, probably it's not on the stage for being implemented right away. Such as happened with Outline for ages.

In any event, there is no docker image whatsoever and the code uses a CC Zero v1.0 Universal

+1. Any public site that runs a service like this gets blacklisted by paywalled sites very quickly.

This is the same issue as the linked one. Will close this so we can discuss it in the other thread.

This is fixed now with package v0.2.0

Yes, it's fixed. Thanks

@robi It's perfectly fine to use your Cloudron instance for that. Maybe it's easier to warm up your IP. For me, it was another challenge to learn postal 🙂 It all depends on your use case.

Just tried it here with the latest app versions and it does work here at least.

Given that Jitsi on Cloudron can't be maintained for the time being I'd expect those kind of issues to not be solved (I also experienced that problem). We do need an alternative.

@chetbaker It was quite a ride to find this information. The information in the docs was quite cryptic.

What I found is (maybe):

You have to build a .plugin file yourself from source. Apparently, you do this by " Archive the plugin files (it must contain config.json, index.html, and pluginCode.js). Change the file extension to .plugin. " . I think one has to read up how to create a plugin to test this out (I haven't).

You have to edit the line https://github.com/ONLYOFFICE/onlyoffice.github.io/blob/master/sdkjs-plugins/content/languagetool/scripts/langTool.js#L61 before creating the plugin file.