Introduction

The Update Database page allows you to modify the settings of an existing database. This feature is essential for maintaining the configuration and performance of your database as your application evolves.

On this page, you can update various settings such as the database name and password. Please note that while the database username and name are automatically generated during creation, you can update these settings as needed. Be mindful of the security implications of changing the database password and ensure that any connected applications are updated with the new credentials.

Ensure you review the current configuration of your database and have all necessary information before making changes. This will help prevent disruptions and maintain the integrity of your data.

Name

The name of the application. This field is required and must be unique within your account. It will help you identify your application among others in your Ghusn Cloud Services dashboard.

Host

This field specifies the host name for your application. It can either be a subdomain under "sahapapp.com" or your personal root domain, such as "example.com". The field must follow a specific pattern to ensure valid host names. If you are using a subdomain, it will automatically be appended to "sahapapp.com".

Note: The host name should not contain consecutive hyphens, should start and end with an alphanumeric character, and the top-level domain should have between 2 to 10 characters.

App Package

This field is visible only if the application type is ASP.NET Core (not WordPress). It allows you to upload a new version of your application. The uploaded file must be a ZIP containing the application files directly in its root, without any subfolders. Ensure that the package complies with the settings used during the initial creation (e.g., Linux-64x, framework-dependent, .NET version).

Important: Make sure your ZIP file does not contain a folder that encapsulates the application files. It should have only the root application files directly.

Environment Variables

These are optional key-value pairs that can influence how your application runs. Environment variables can be used to configure database connection strings, API keys, and other runtime settings. Keys must be unique within the application environment, and there should be no duplicate keys to avoid conflicts.

Example:

• DATABASE_URL=your_database_url
• API_KEY=your_api_key