Configuration options
After deploying an application, you may need to adjust how it's configured. This page explains the types of settings available and how to change them.
Two levels of configuration
Clouve applications have two distinct levels of configuration:
| Level | Where to configure | Examples |
|---|---|---|
| Platform settings | Clouve dashboard | Deployment name, resource allocation, environment settings |
| Application settings | Inside the application itself | User accounts, site name, features, integrations |
Most day-to-day configuration happens inside the application, not in the Clouve dashboard. Platform settings control how the deployment runs; application settings control how it behaves.
Platform configuration (Clouve dashboard)
Deployment name
Each deployment has a name that identifies it in your dashboard. You can change it from the deployment settings page.
Environment variables
Some applications let you update environment variables after deployment. These control application-level settings that the application developer defined as user-configurable.
To view and update environment variables:
- Go to your deployment in the dashboard
- Click Settings or Configuration
- Find the Environment section
- Update the variables and save
Not every variable can be changed after deployment. Variables the developer typed as static are fixed; variables typed as userConfigurable can be updated.
Changing environment variables typically restarts the application, which interrupts service briefly (usually 30 to 60 seconds). Plan changes for off-peak hours.
Application credentials
Your application's admin username and password are set at deployment time. The platform stores them encrypted in Kubernetes Secrets, and nobody can view them, including Clouve platform administrators.
To reset credentials after deployment, log in to the application and change the password from within its user or account settings. The platform stores the initial password as a one-time value and does not use it for ongoing authentication.
Application configuration (inside the app)
Most application-specific settings are configured from within the application itself, after logging in as an administrator. This is intentional: the application is yours to configure, and the platform does not restrict how you run it.
Common configuration tasks for specific applications:
WordPress
After logging in at /wp-admin:
- Site name and tagline: Settings → General
- User management: Users → Add New
- Plugins: Plugins → Add New
- Themes: Appearance → Themes
- Email configuration: Settings → Email (or a plugin like WP Mail SMTP)
Moodle
After logging in, go to Site Administration → General:
- Site name: Site Administration → Front Page → Front Page Settings
- User creation: Site Administration → Users → Add a New User
- Courses: Click "Add a New Course" from the dashboard
- Language: Site Administration → Language → Language Settings
SuiteCRM
After logging in:
- Organization settings: Admin → Company Details
- Users: Admin → User Management
- Currency: Admin → Currencies
- Email server: Admin → Email Settings
Odoo
After logging in:
- Company profile: Settings → General Settings → Companies
- User management: Settings → Users & Companies → Users
- Language and timezone: Settings → General Settings → Language
What can be configured at deployment vs after
| Setting | At deployment | After deployment |
|---|---|---|
| Admin username | Yes (set once) | No (change inside the app) |
| Admin password | Yes (set once) | Yes (change inside the app) |
| Admin email | Yes (set once) | Yes (change inside the app) |
| Site/organization name | Yes (set at deployment) | Yes (change inside the app) |
| Language and locale | Application-dependent | Yes (usually inside the app) |
| Custom domain | Yes, on a paid plan | Yes, on a paid plan |
| Storage size | Not configurable | Contact administrator |
| Resource limits (CPU/memory) | Not self-service | Contact administrator |
Custom domain configuration
By default, your application is accessible at a clouve.dev subdomain (e.g., https://mycompany.clouve.dev). On a paid plan you can add your own domain (e.g., https://intranet.mycompany.com). Free trials run on the Clouve address only.
Custom domain setup involves:
- Turning on Custom Domain in the deployment form and entering your domain
- Creating the DNS record the form describes at your domain registrar (your IT team may do this); the form checks the record
- The platform configures TLS automatically for the new domain
This process typically takes 24 to 48 hours for DNS propagation.
Common configuration mistakes
Setting a weak admin password Application passwords are your responsibility. The platform stores them securely, but a weak password leaves your application vulnerable. Use a strong, unique one.
Using a personal email for the admin account
Use a shared organizational email (e.g., it-admin@mycompany.com) so admin notifications aren't tied to a single person who might leave the organization.
Not completing first-run setup Some applications (Moodle, Odoo) show additional setup wizards after first login. Complete these before inviting users.
Changing critical settings without a backup Before making significant configuration changes, note the current settings so you can revert if needed.
Getting help with application-specific configuration
For configuration help specific to an application (not the platform):
- WordPress: wordpress.org/support
- Moodle: moodle.org/support
- SuiteCRM: docs.suitecrm.com
- Odoo: help.odoo.com
For platform-level configuration help, see Support →.
Next steps
- Managing deployments →: day-to-day operations
- Support →: get help if something isn't working