Cloudron Forum

@nostrdev That's what API keys are for, no?

Agreed, this was a major pain when creating 100s of users then having to clean up all this cruft. The space saved was significant too.

@Lonkle I think it's waiting on your PR

They now have a new domain at https://sim.ai

https://github.com/dkarlovi/fileferry

FileFerry — media organizer (short)

FileFerry is a small CLI that organizes image and video files into target folders using metadata and filename patterns.

What it does

• Scan one or more source directories (profiles) for media files.
• Extract metadata from filenames, EXIF (images) or ffprobe (videos) when available.
• Render a per-profile target path template and move files (dry-run by default).

Quick examples

Build and dry-run with your config file:

go build -o fileferry .
./fileferry config.yaml # dry-run: shows what would move
./fileferry config.yaml --ack # actually move files

Example (anonymized) config.yaml excerpt:

profiles:
Videos:
sources:
- path: /path/to/videos
recurse: true
types: [video]
patterns:
- "{meta.taken.date} {meta.taken.time}.mkv"
- "{meta.taken.date}-{meta.taken.time}.mkv"
target:
path: /organized/videos/{meta.taken.year}/{meta.taken.date}/{meta.taken.datetime}.{file.extension}

Pictures:
sources:
- path: /path/to/pictures
recurse: false
types: [image]
target:
path: /organized/pictures/{meta.taken.year}/{meta.taken.date}/{meta.taken.datetime}.{file.extension}

Config contract (short)

• profiles is a map of profile names -> profile config.
• A ProfileConfig contains: sources (list), optional patterns (filename patterns used to extract metadata), and target.path (template used to build destination path).
• SourceConfig has path, recurse, types and optional filenames.

Template variables

• {meta.taken.year}, {meta.taken.date}, {meta.taken.datetime}
• {meta.camera.maker}, {meta.camera.model}
• {file.extension} (no leading dot)

Notes: filename patterns are anchored and must match the filename exactly (e.g. 2025-06-02 15-21-02.mkv). Patterns support tokens like {meta.taken.date} and {meta.taken.time} which map to regex rules.

If you're up for a challenge, look into the forum for sysbox which allows for stronger docker isolation so you can experiment with portainer in a more isolated container on Cloudron.

Make sure to try them with CCAI

@webliska logins are session based.

You can change the password all you like, as long as the session is active, it doesn't prevent access.

The logs may be misleading in printing the user logged in, when it's really just checking for an active session.

Hence the button exists.

As the message says, Cloudron has no app configured for this domain.

You may want to install an App Proxy Cloudron App and configure it to what you need.

It's at the top right of the App Store, next to the search bar.

Use the bottom right button from your screenshot to log them out.

See: https://forum.cloudron.io/post/52997

Can you add a bit about how you did your Ghost integration as an example?

@timconsidine how about a wget that grabs the master apps-config.json during any install/visit?

@david.opalia Yes, you can make a custom package and submit it to the Cloudron App store.

What is Microsoft code doing there?

This could be installed in the LAMP app

@timconsidine that button seems to be a list of tasks, instead of a chat.

Relaunching the app still steals my command button, so off it goes ;-/

@DidierMalenfant test with command line tools to see if there are any formatting issues that might be causing this.

@timconsidine thanks for the screen shots, however I didn't see you open the chat icon as mentioned.

I happened to create a second user in addition to the admin and could see each in that side window. There were no actions possible from it.

Also I noticed that the client hijacked my command button away from the Brave browser I am typing this on. I use it command-<- to navigate back in the forum, and strangely it only navigated back in the sync-in client, even though it didn't have window focus! Insane.

@timconsidine the UI suggests there is a chat function just underneath the notifications bell on the right, but it doesn't look functional.

MacOS Client looks exactly like the web interface, so what's the benefit?