Cloudron Forum

The reason I changed the database variables is that I’m using a centralized managed database hosted on AWS. It provides additional security and encryption features, along with capabilities such as Point-in-Time Recovery (PITR) for backup and disaster recovery purposes. It also offers high availability and improved reliability compared to a locally hosted database.

The reason I changed the database variables is that I’m using a managed database hosted on AWS/Azure.

The variables I changed are:

DB_CONNECTION=mysql
DB_HOST=here
DB_PORT=3306
DB_DATABASE=here
DB_USERNAME=here
DB_PASSWORD=here

Hello Cloudron Support,

I have deployed FreeScout on Cloudron and I am experiencing an issue with the .env file configuration.

Whenever I modify the .env file and restart the application (or the app restarts automatically), all changes are discarded and the .env file is reset back to the default configuration.

This behavior prevents persistent configuration changes and makes it difficult to manage custom environment settings.

Steps to reproduce:

Open the app terminal / filesystem.
Modify values in the .env file.
Restart the application.
Observe that the .env file is reverted to the default state.

Expected behavior:

Changes made to the .env file should persist after application restarts.

Actual behavior:

The .env file is overwritten/reset during restart.

Could you please advise:

Whether this is expected behavior in the Cloudron FreeScout package.
The correct method/location for persisting custom environment variables.
If there is a supported way to prevent the .env file from being regenerated.

Thank you.