We're using Zulip and it's incredible. The organization of channels into sub-topics is perfect. The LaTeX integration is also huge for us. It has some nice quality of life features and just generally works really well for us. Cloudron integration would be great.
B
bwag
@bwag
Posts
-
Zulip - Powerful open source group chat -
(Question) How can I stop Cloudron from starting automatically?Edit: fixed. I found docker.service inside /etc/systemd/system/multi-user.target.wants/
I didn't get this to happen: "Then, systemctl start my-disk-mounter would automatically start docker and box." But that's ok. I run a manual startup script that prompts for the encryption password, mounts the disk, then starts all the systemd services. Instead of my-disk-mounter.service, I have check-that-all-disks-are-properly-mounted.service which is Required by box and docker. Thanks again.
-
Library scan failingI am running into the same error message mentioned here: https://github.com/advplyr/audiobookshelf/issues/2854
When I scan a library, the log gives:
FATAL
[Server] Unhandled rejection: ReferenceError: structuredClone is not defined, promise: Promise { <rejected> ReferenceError: structuredClone is not defined at LibraryItemScanData.checkLibraryItemData (/app/code/server/scanner/LibraryItemScanData.js:241:41) at LibraryScanner.scanLibrary (/app/code/server/scanner/LibraryScanner.js:188:60) at async LibraryScanner.scan (/app/code/server/scanner/LibraryScanner.js:82:22) }
-
Library scan failingWow, thanks, that was fast! I'm not seeing the error any more.
-
Customizing Gitea login page so the only option is CloudronSolved
This turned out to be easier than I expected, oops. I modified signin_inner.tmpl to only have the small OAuth2 portion of the signin page, i.e. I deleted lines 13-54 and 56-58 from that file (as it exists now), and put my version in gitea's folder custom/templates/user/auth/. As desired, it still displays "Login with cloudron", but not the main login option. -
Migrating from another Gitea instance?Any advice on how to migrate repositories and access permissions from a Gitea instance that is not on Cloudron to a fresh Gitea instance on Cloudron?
My first choice would be to modify the steps in Gitea's Backup and Restore, though I'd have to sync the users and permissions correctly somehow.
But if I could access the gitea command line, I'd be okay with trying to take it from there manually. It's not a large instance at all. However, I think the cloudron doc about how to access the Gitea CLI is outdated. I guess it has to do with docker now, but I'm not sure how.