Cloudron Forum

Just FYI our company (relm.us) is sponsoring some new feature development in Vikunja that may help others here:

1. Image previews: when attaching an image-type file to a task, a thumbnail of the image will be visible (currently, only the filename/description is shown).
2. Cover image on kanban cards: you will be able to promote a kanban card's attached image to the "cover", so that you can see the image in "kanban" mode. This is similar to the way Trello does it.
3. The large "Vikunja" logo/branding in anonymous/read-only mode will be optional.

Vikunja's developer, Konrad, estimates these features will be ready by end of year (i.e. at the next release).

Best,
Duane Johnson
CEO/developer Relm.US

I have a working setup, based on @Valexico 's work here:

https://github.com/canadaduane/librechat-cloudron

The package has been updated to the latest version of LibreChat 0.7.8, and I fixed a few minor wrinkles such as OIDC login, write access to the public dir, and postgres support. I haven't yet tested it with all of the providers (this requires access keys in the .env file).

Open WebUI has changed their license to a not-strictly-open-source license (by OSI definition):

https://docs.openwebui.com/license/

https://www.reddit.com/r/LocalLLaMA/comments/1kg4avg/openwebui_license_change_red_flag/

This looks really interesting:

https://github.com/nitnelave/lldap

Has anyone looked into how it might be used with Cloudron?

From the github page:

A lightweight authentication server that provides an opinionated, simplified LDAP interface for authentication. It integrates with many backends, from KeyCloak to Authelia to Nextcloud and more!

It comes with a frontend that makes user management easy, and allows users to edit their own details or reset their password by email.

The goal is not to provide a full LDAP server; if you're interested in that, check out OpenLDAP. This server is a user management system that is:

• simple to setup (no messing around with slapd),
• simple to manage (friendly web UI),
• low resources,
• opinionated with basic defaults so you don't have to understand the subtleties of LDAP.

We now have a working LibreChat cloudron container set up. See: https://forum.cloudron.io/topic/12850/first-try-app-packaging-librechat-issue-with-postgresql-extention-pgvector/14?_=1749416165430

It's been several months (perhaps more than a year) since I tried logging in to my Ghost installation. When I tried to log in, however, it didn't seem to recognize my email. A pop-up said, "No member exists with this e-mail address. Please sign up first."

When I logged in via MySQL I could tell that the email exists in the users table. In fact, it was the only user. However, it still didn't seem to recognize the email.

It turned out that I needed to add "/ghost" to the URL to log in to the Ghost backend. I had forgotten that there is a "member" login for email sign-ups, and the member login is the visible "sign in" button on the typical landing page.

I hope this helps someone else!

I just noticed the image features landed a few days ago:

https://github.com/go-vikunja/frontend/commit/877e4250554b31db2d57f44a7443c5d04c783e59

https://github.com/go-vikunja/frontend/commit/3d88fdaaddca15b98efa938f0b2813420d56ad84

(they have not been included in the Vikunja release yet, however)

I just noticed they have mattermost integration! From the .env.example file:

# Mattermost Integration
MATTERMOST_ENABLED=false                          # Enable Mattermost (true|false)
MATTERMOST_SERVER_URL=YourMattermostServerUrl     # Mattermost server URL
MATTERMOST_USERNAME=YourMattermostUsername        # Mattermost username
MATTERMOST_PASSWORD=YourMattermostPassword        # Mattermost password
MATTERMOST_TOKEN=YourMattermostToken              # Mattermost slash command token
MATTERMOST_COMMAND_NAME=/sfu                      # Mattermost command name
MATTERMOST_DEFAULT_MESSAGE=Here is your meeting room: # Mattermost default message

Coming from a Slack-at-work setup with huddles (video meetings) this is really cool.

This is awesome progress @Valexico! Did pgvector make it in to the base Cloudron release, and were you able to then connect LibreChat's DB up?

BTW I'm very interested in this right now because Open WebUI (the only chat frontend currently supported by Cloudrain AFAIU) recently changed their license to something that is no longer open source (by OSI definition).

Cloudron support mentioned here (but not implemented at time of writing):

https://github.com/activepieces/activepieces/issues/1277

@girish It's fixed! Thank you very much.

@nebulon This has been released!

https://vikunja.io/blog/2022/10/whats-new-in-vikunja-0.20.0/

Hello!

Is there a way to add environment variables or otherwise configure Uptime Kuma?

Specifically, a recent upstream change appears to have disabled the ability (by default) to embed Uptime Kuma in an iframe.

The solution for this particular issue appears to be to set UPTIME_KUMA_DISABLE_FRAME_SAMEORIGIN to true, however I'm not sure where to do this in Cloudron.

Thanks!

While investigating this issue, I discovered a small bug in the "noop" code:

/home/yellowtent/box/src/backupformat/tgz.js:28

If you'll note, at line 28, fileType is not yet defined, and therefore throws an error.

Unfortunately, this does not fix my issue. The dropdown box is still missing.

@firmansi Thanks! This worked. It would be better if the URL need not be configured inside the app, but just wanted to note that the solution/workaround is ok.

@nebulon said in How to set up backups after "noop" selected?:

Maybe you could enable remote SSH support for us and send a mail to support@cloudron.io with the Cloudron details and we can check this directly.

Done, thanks.

For the record, the resolution was that I had two accounts, one an admin and one a superadmin (both with a similar username). I believe that my logging into an app as the admin caused my current account in Cloudron to also become admin. This hid the "Configure" button in the Backup section--while admins can see the backup settings, only the superadmin can change them. Logging out of the admin account immediately gave me access to superadmin again.

@girish Thank you, this did the trick. In my case, I have Ubuntu 20.04 on a kvm inside my host, so I had to change the inotify watch limit for the "inner host". The warning message went away a few minutes after that.