Different database connections on staging server vs production server

[mba]

Hi,

We have two cloud servers in Sisense: one for development (staging) and one for production.

• The staging server connects to our staging database.
• The production server connects to our production database.
• All cubes and dashboards are identical except for database connection strings and names.

Our Git branching strategy follows these steps:

1. Create a feature branch from staging.
2. Make changes and push them to the feature branch.
3. Open a pull request from the feature branch to staging.
4. Test changes in staging.
5. If approved, merge staging into master (production) to deploy changes.

The Issue

Git integration tracks database connection names, meaning both servers must either run on staging data or production data—this is not feasible for us.

Proposed Solution

We suggest implementing a decentralized environmental variable for storing database connections. For example:

• Use {database-server-name} as a placeholder in configurations.
• Set database-server-name = db_server_staging on staging.
• Set database-server-name = db_server_production on production.

This would allow the same codebase to dynamically connect to the appropriate database without manual adjustments.

Would love to hear your thoughts on this!

[DRay]

Hello @mba,

Thank you for sharing your idea and providing details.

We encourage people to continue to vote and comment. One of the ways we prioritize efforts is by community interest, so every vote and comment help turn a request into a reality.

Thank you again for sharing and being part of our community!