Deploy to Render

Render ↗ (opens in a new tab) is a cloud platform that simplifies and accelerates the deployment and scaling of web applications, databases, and other services. It offers a range of features including one-click deployments, automatic scaling, support for multiple programming languages, and seamless integration with popular development tools and frameworks.

The project includes a render.yaml configuration file that outlines all the essential services required to operate the platform. This encompasses the database service, the pgbouncer service, and, lastly, the Feature Flags dashboard. This configuration has been meticulously designed to streamline the deployment process on Render, ensuring a seamless setup.

Getting started

(opens in a new tab)

Here are the steps to deploy the platform on Render.com:

1. Fork the platform to your GitHub account.
2. Log in to Render.com ↗ (opens in a new tab).
3. Click the New + button, then select Blueprint from the menu.
4. Connect your GitHub account and choose the forked platform repository.
5. Follow the on-screen instructions to set up the necessary Environment Variables and click "Apply."
6. Your services will be automatically built and started. Each git push will trigger a new deployment.

Environment Variables

To ensure a successful deployment on Render, the platform requires a minimum set of environment variables. Below is the list of environment variables that you must fill in. For the complete list of Environment Variables, please refer to the Configuration Page.

What's next?

Begin by familiarizing yourself with the platform. Create projects, add new feature flags, invite members, and implement the feature flags in your product using our official SDKs.

Lastly, stay tuned about updates, including new features and bug fixes. To ensure your platform is always up-to-date with the latest improvements, refer to our guide on updating the platform by visiting the Updates Page.

Troubleshooting

How to Retrieve the Project URL for NEXTAUTH_URL and Github OAuth App?

If you don't have a domain yet, feel free to leave the fields below empty or use dummy information. Proceed with the deployment as usual. Once the deployment is complete, Render will generate a URL for your project.

Copy this URL and update the information in your Github ↗ (opens in a new tab) OAuth App (opens in a new tab). Next, modify the environment variables in the project settings on Render and initiate a new deployment on Render once again.

Environment Variables:

• NEXTAUTH_URL

Github OAuth App (opens in a new tab) Fields:

• Homepage URL
• Authorization callback URL

How to Retrieve the DATABASE_URL via the pgbouncer Service?

To obtain the DATABASE_URL for your applications, simply head over to the pgbouncer service. You can connect using the internal connection string, substituting the database host with the internal hostname of your PgBouncer instance: postgres://USER:PASSWORD@PGBOUNCER_HOST:PORT/DATABASE.

In the example below, we will demonstrate how to collect the following fields:

• PGBOUNCER_HOST
• USER
• PASSWORD
• PORT

To build the following connection: postgres://USER:PASSWORD@PGBOUNCER_HOST:PORT/DATABASE, please follow these steps:

To initiate the connection, please access the address of the Connection Pooling service you just created. Refer to the image below to see how to copy this address, which includes the PGBOUNCER_HOST and PORT fields.

After obtaining the address, you'll need to include the USER and PASSWORD fields. Refer to the image below to see how to retrieve this information.

After collecting all the required information, you'll have the necessary fields to construct the connection string, which should look something like this:

postgres://basestack_feature_flags_db_wh3p_user:wvQf5EZ6XciDmdDSoQrp7AqCyXlq1ixc@basestack-feature-flags-db-pgbouncer:5432/basestack_feature_flags_db_wh3p

Finally, copy the connection string and update the environment variables in the service running the Feature Flags dashboard instance.