Configuration System Overhaul - from MiroTalk SFU 1.8.00

[avatar1024]

Just to let everyone know this change in config has landed with MiroTalk SFU 1.8.00, but while the MiroTalk version has been updated on Cloudron, the new config approach is not yet the default on the Cloudron package. @staff, I'm sure you're aware of this change but is it on your radar to upgrade the package to make use of this, or not really and you expect / would like someone from the community to do it?

IMPORTANT UPDATE
Configuration System Overhaul
What's New?
We've revamped the configuration system for improved security, maintainability, and scalability!

Enhanced config.js Structure

✅ Modular Organization – Settings grouped by features (API, SFU, TURN, etc.).
✅ Type-Safe Defaults – Automatic validation for all configuration options.
✅ Self-Documenting – Clear descriptions for every parameter.
✅ Dev-Friendly – Pre-configured presets for local development.

New .env File

✅ Centralized Secrets – Sensitive data (API keys, credentials) now exclusively in .env.
✅ Docker/K8s Ready – Seamless integration for containerized deployments.
✅ 12-Factor App Compliance – Ideal for cloud-native environments.

Key Benefits

🔹 Security First – No more hardcoded secrets in JavaScript files.
🔹 Faster Debugging – Intuitive grouping reduces configuration headaches.
🔹 Scalability – Designed for CI/CD and orchestration tools like Kubernetes.

---

️ Migration Guide (not sure this is recommended for Cloudron)

Backup your existing config.js and .env files.
Copy the new templates:

cp app/src/config.example.js app/src/config.js
cp .env.template .env

Migrate secrets from your old config to .env.
Update docker-compose.yml with the new volumes:

volumes:
  - ./app/src/config.js:/src/app/src/config.js:ro
  - ./.env:/src/.env:ro

Restart your instance.

[nebulon]

The Cloudron package already ships mirotalk sfu 1.8.2 with adjusted configs. The Cloudron package had a custom config.js in place from the start, we might see how to support the env file approach in the future.

Would be good to have the links to such readme or release resources in the future instead of pasting here. This would avoid duplication and thus the risk to quickly have outdated info here.

[avatar1024]

@nebulon said in Configuration System Overhaul - MiroTalk SFU 1.8.00:

The Cloudron package had a custom config.js in place from the start, we might see how to support the env file approach in the future.

Thanks for the info and clarification.

@nebulon said in Configuration System Overhaul - MiroTalk SFU 1.8.00:

Would be good to have the links to such readme or release resources in the future instead of pasting here. This would avoid duplication and thus the risk to quickly have outdated info here.

MiroTalk posts announcement on a Discord channel so unfortunately there isn't another direct link to announcements. I posted this one here as it was a major change in config that could potentially affect Cloudron users (as it hadn't been rolled out as part of the usual update of Cloudron app package).

[nebulon]

Ah thanks for letting us know. I rarely hang out on discord these days, given my focus on mostly selfhosted things

[avatar1024]

@nebulon said in Configuration System Overhaul - MiroTalk SFU 1.8.00:

Ah thanks for letting us know. I rarely hang out on discord these days, given my focus on mostly selfhosted things

Very much the same, in fact I recreated a Discord account just to check out MiroTalk info as I had issues with my instance

Also I've updated the original post to make it clearer I'm pointing out to the change in config rather than the MiroTalk version that hasn't landed on Cloudron.

[canadaduane]

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.

[jdaviescoates]

@canadaduane FYI Nextcloud Talk does chat plus video meetings too.