Cloudron Forum

@sponch said:

@ekevu123 Hi. Caldav via SoGo and mailbox.org
The calendars do appear when I enter my login credentials, but the appointments aren't syncing. at least with one account - the other only sync partially.
"Some calendars have never been synced" - refreh doenst help.

Okay, I got it, the next update will support mailbox.org as well, but this might require 2-3 days to implement!
From what I am seeing, you would want to create an app-specific password in mailbox.org, though, as Sogo acts as another frontend, but correct me if I am wrong here.

@sponch So far, Sogo and mailbox.org aren't officially supported, and some Caldav providers handle things differently.

I'll create accounts and see if I can test it and see what happens!

@james said:

Hello @ekevu123
If you'd like some examples for how we do that, you could check out the start.sh of the mirotalk app or the start.sh form the Kutt URL shortener app to just name two examples.

---

One small note on that topic.
When merging env files together like we sometimes do, ensure that a newline is present otherwise it could end up appended to the last string.
See: https://git.cloudron.io/packages/twenty-app/-/merge_requests/6/diffs

Without the linked diff, if a new line in /app/data/env is missing the string gets appended.
So if your last line in /app/data/env is STORAGE_LOCAL_PATH=/app/data/local-storage and it gets appended to /run/twenty-server/.env it results in:

STORAGE_LOCAL_PATH=/app/data/local-storageIS_CONFIG_VARIABLES_IN_DB_ENABLED=false

so to ensure this never happens the adding a newline after the cat >> /run/twenty-server/.env <<EOT is enough.

Thank you, I will look into that!

@james said:

Hello @ekevu123

Since not everyone is comfortable using the cloudron cli maybe you could add a .env.sh handler like we do with many packages.
Many Cloudron users also know this flow from us, guess that is why @enerch tried that approach first.

I didn't know people use it usually like that, will do!

@sponch said:

thanks for it! Just tested. It connects to my caldav calendar shows the diefferent calendars but doesnt sync them. Any idea?

Which Caldav calendar are you using? And how do you assume it doesn't sync them?

Try using the Cloudron CLI to set these!

@andreasdueren said:

@ekevu123 Cool app, toying with it right now. One observation:

• when trying to connect to my nextcloud calendar, it connects and recognizes the different calendars but when I press Add integration, it returns Base url Must be a valid HTTP or HTTPS URL (e.g., https://example.com) nonetheless.

This is fixed in the next release coming up today!

I am not against AI content, if the quality is good.

Via a custom script - when I change a version, I have to do this in several places in the app, so I wrote a script where I specify the version number and it does this automatically.

Both. I want to understand if both are correct programmatically, but I can't test them against having an existing docker image, because I find that counter-intuitive - why would I build the docker image before knowing if everything is correct?

It works again. Something else was broken as well, it was a bit of trial-and-error, so some form of file verification would be really helpful before deploying.

cloudron appstore verify-manifest requires a docker image, doesn't it? It would be ideal to have a verifier for both cases that don't need that. My logic would be that I want to fix any issues before building the image? I just want to see if it technically works?

Fair enough - mine seems to be working fine, though, since I rewrote my test script, so I guess I triggered it myself on my end.

I would like to be able to validate the CloudronVersions.json via Cloudron CLI, ideally with a simple boolean response, it's either valid or it isn't, and if the latter, why. This would allow an app developer to validate the file without having to go into their own Cloudron and test it manually. This way, it could also be part of automated validation processes like a test suite.

Really, you were? My best guess right now was that a script I was running using the Radicale API synced too many events at the same time, and the issue seemed to have disappeared when I slowed it down. So, I guess it could have been me ...

I am on the newest version of Radicale and it keeps stopping to work after a few minutes, but starts working again when I restart the app. The logs only show this:

=> Healthcheck error: AbortError: The operation was aborted

I couldn't find anything else in the logs - it seems like at some point, the app crashes and stops logging, so the only error left is the healthcheck.

Anyone else facing this?

@LoudLemur said:

Wandering Monster packaging assessment: Verdict: Hard but feasible.

https://paste.wanderingmonster.dev/?388a7cbf9a2bb945#fBFMUA66gSSruwP7BXRSJvdeGW5LNKv8GaJynvwtuSL

Can you please stop posting these everywhere? This isn't a relevant contribution and rather senseless spam that should be reported to the forum admins.

@LoudLemur said:

WanderingMonster packaging report: Verdict: Moderate.

https://paste.wanderingmonster.dev/?968a273a702c96da#BheknpBPP1aTHG9TTBntKPht3fXBwBTJ1GXzLehfnPCg

Being the app developer, I must say the report is quite inaccurate and full of assumptions (e.g. "probably the backup size isn't big, but who knows").

I'd be surprised if anyone finds this helpful.

@LoudLemur said:

@ekevu123 https://forum.cloudron.io/topic/12472/please-use-this-template-to-make-an-app-wishlist-request/13

Thank you for pointing out the template, but when I posted this, this didn't exist yet and I didn't want to go through my posts retroactively.

There is a small UI bug in the resources section of any app. How to reproduce:

1. Go tot resources for any app
2. Resize the memory limit or rescale CPU limit
3. Wait until it's done

What should happen: The button Resize or Scale should be disabled once done when the targeted size is equal to what I have. (similar to when I open the menu at first without any pending change)
What is happening: The button allows me to click again

Why does this matter: It isn't entirely clear if I clicked the button already, prompting the user to resize / rescale again.

Easy to fix though.