But how do I do this for a secret key? I could generate it upon first run, but wouldn't it be regenerated then when updating, which shouldn't happen?

I couldn't reproduce the github issue, but the rest is fixed. Getting there! It is, after all, still in a beta version, fortunately, having users pointing out issues that I can fix, so it's already pretty advanced.

Correct, but I'd still need to set a secret key, which is used for encryption. If I generate it automatically like that, wouldn't it be regenerated with every update or even app restart, which we should avoid?

For my version, I set it via cloudron env set, but this means the user would need to do the same.

Thank you for trying it out! The app still awaits manual approval by Google, but the calendar syncing works. Not sure why github didn't work for you, it works for me, so I'll check that.

I have successfully created a working CloudronVersions.json: https://github.com/Tymeslot/tymeslot/blob/main/CloudronVersions.json

However, my app requires some environment variables to be startable. At the moment, the installation crashes until the user sets them and restarts the app afterwards.

Is there any way to handle this?

Maybe I am wrong because this is still new, but does the changelog for a community app have to be plain text? I am having an .md already, and I am thinking about whether I have to duplicate it, but if plain text is really a prerequisite, why not allow an .md changelog in the first place?

No, teams will be a separate package, which will still take a few weeks, but it will come!

Well, glad that you are happy with cal!

There are three points I focused on with Tymeslot:

1. It has less feature-bloat, is more intuitive to use and set up
2. It is much less resource-intense
3. The UI, especially the booking page, looks much better. Like this, for example: https://tymeslot.app/demo-theme-2

I am also working on features that cal.com doesn't have, but I'll announce it when that's ready.

Tymeslot - Better Meeting Scheduling than Cal.com

---

Main Page: https://tymeslot.app
Git: https://github.com/Tymeslot/tymeslot
Licence: Elastic License 2.0
Dockerfile: Yes
Demo: https://tymeslot.app

Summary

Tymeslot is a self-hosted meeting scheduling platform — a privacy-respecting alternative to Calendly and similar tools. It lets you create booking pages for others to schedule time with you, with full timezone awareness, calendar sync, and real-time availability checking.

Key features:

• CalDAV integration — syncs with Nextcloud Calendar, iCloud, Fastmail, and any standards-compliant calendar server
• Google Calendar sync — reads busy times and creates events directly in Google Calendar
• Google Meet integration — automatically generates Meet links for booked meetings
• SSO via OIDC/OAuth — supports Google, GitHub, and any OpenID Connect provider
• Multiple themes, multiple language support (English, German, French, Ukrainian)
• No ads, no tracking, no third-party analytics
• Background jobs with retry logic, rate limiting, structured logging

Built with Elixir/Phoenix LiveView — lightweight, concurrent, and very fast.

---

Notes

I'm the developer of Tymeslot, and I built Cloudron support in from the start. The cloud version is hosted on Cloudron right now. The app also supports authentication with Cloudron accounts and uses the postgres and sendmail addons.

What makes it a great fit for Cloudron:

Automatic addon integration: The app auto-detects Cloudron's built-in services. The PostgreSQL connection (CLOUDRON_POSTGRESQL_URL) is picked up automatically — no manual database config needed. Cloudron's mail relay is used for all transactional email out of the box. Cloudron's OIDC identity provider is detected automatically, adding an SSO login button without any configuration.
Already installable today: You can install it right now as a custom app using the Cloudron CLI. Full step-by-step instructions are at: https://tymeslot.app/docs/cloudron
Minimal required config: Only SECRET_KEY_BASE and PHX_HOST are needed for a working installation. Everything else is optional or auto-configured.

The documentation page at https://tymeslot.app/docs/cloudron walks through the full install in about 3 commands. It also covers optional extras: Google Calendar/Meet setup, GitHub OAuth, switching to an external email provider, and common troubleshooting.

Having it in the official Cloudron app store would make it much more discoverable for the self-hosting community — and would mean users get one-click installs and automatic updates.

If there are any features you are looking for, let me know! The app has been developed daily for weeks now. Please also star it on Github if you like what you see!

---

Alternative to: Cal.com, Easy Appointments, Calendly
Screenshots: https://tymeslot.app

I just got it - works like standard SSO! Smooth.

How can I activate Cloudron authentication for a custom app? My goal is to use my cloudron account to log in. I have implemented it in the code. But how does this work in the frontend? When I install something from the app store, I can choose whether the app should handle authentication or cloudron, but how does this work here?

@james said in Notification being unhelpful:

Hello @ekevu123

Where did you see this log message?

In the main notifications of the server instance

@joseph said in Notification being unhelpful:

This is coming from porkbun - https://status.porkbun.com/ . They are having some service issues .

Oh, thank you, that wasn't clear!

I have just gotten this notification, possibly related to the upgrade to Cloudron 9.1.0, which happened at the same time:

Configuration error: Porkbun DNS error 400 {"status":"ERROR","message":"Create error: We were unable to create the DNS record."}

The problem is that this notification doesn't allow me to act on it. I see the domain, but which DNS record is meant? Why was it updated in the first place? Also, seemingly, everything works, so maybe the error was re-tried anyway?

This would be really nice to have, because it could replace a commercial option that you'd otherwise need to pay for.

I push code to gitea and mirror it to github, and I am actually happy with that setup. However, I want to define releases on github, and every mirror push overwrites these. Most likely because the mirroring uses force push, however, I don't see any option to change that behaviour.

Can I solve this somehow? Releases don't seem to be synchronised either, I'd be more than happy to have them defined on gitea as the source of truth and sync everything together, but that doesn't seem possible.

Thank you! I went with Github Actions for now because I don't really need to isolate it, it would be just nice-to-have.

I would like to see custom expiry dates (optionally) for the app passwords I set in my profile. I am using them sometimes for debugging, and it can happen that I even give one of it to AI, e.g. "use this to test to authenticate" when coding.

If I could set an expiry date a few hours from now, I wouldn't have to worry about cleanup.

I am using gitea on Cloudron and I am trying to set up a runner that automates the workflow of building a docker image for an app I am building. I wanted to solve this using actions.

However, the runner seems to need a separate image installed to build the docker image there. Now, I could probably install this as a custom app on Cloudron, but firstly I wanted to understand if there's an easier way of accomplishing this?

Otherwise, another option would be to use Github Actions.

EDIT: The gitea runner can't be installed on Cloudron, because it needs to be able to spawn containers.

Steps to reproduce:

1. Go to Profile
2. App Passwords section
3. Click on Add
4. Add a password using the same name and choose the same app as you already have

Expected behaviour:
A warning appears informing about the duplicate

Actual behaviour:
Nothing happens when I try to create that app password

I believe the goal is to implement this for compliance purposes.

If you are using a SMTP relay server, you could use their API to implement a custom tool. Postmark, for example, has anti-spam tools that should help.