Environments

With Frontegg environments you can test all the Frontegg capabilities in a development environment and seamlessly deploy it live to production.

The flow for using Frontegg environments follows industry best practices.

You begin with setting up and testing Frontegg features and configurations in a development environment. This allows you to explore how things work and feel comfortable with it before using it with your customers.

Once ready, deploy it to a production environment so that you can use it live in your application.

When you deploy to production, the settings from the development environment are automatically copied over to the production environment.

Our environments setup eliminates the need to:

  1. have multiple workspaces for development, staging, and production
  2. manually copy settings from one to the other

🚧

Currently, Frontegg copies many of the settings from development to production but not all. Read below to learn what we copy over.

If you do not need a Frontegg development environment, do not worry!

Go from integration to production super fast and without effort.

Read below to learn more about how Frontegg environments work and how you can use them.

πŸ“˜

What happened to workspaces?

Frontegg environments replace the workspaces approach that we previously used. Therefore, you no longer need to create multiple workspaces and manually copy configurations from one to another.

Initial Frontegg Integration & The Development Environment

When you first integrate Frontegg into your application, you need to:

  • Select your tech stack
  • Select an environment
  • Go live

Learn about selecting your tech stack here and going live here.

When you select your environment, select the development environment and enter your application url.

Your app url is the address where you are running your development environment.

For instance, http://localhost:3000 or something like that.

πŸ“˜

We require that you start with the development environment. You cannot create a production environment as the first environment to integrate with.

It is super fast and easy to go straight to production. Read below.

Then choose whether you want to test it out first or go straight to production.

πŸ“˜

If you choose to move immediately to production, you will be prompted to input your application's production url. See below for the production flow.

If you choose to test it out before going to production, you get the full Frontegg experience in a development environment where you can test out how Frontegg works and play around with it just.

You can find your development environment in the Frontegg Portal sidebar.

From the sidebar, go to Environments ➜ Development.

On that page, you can configure Frontegg however you like.

For instance, you can set your authentication preferences, add and manage users, create and use webhooks, edit email templates, and more.

You can tell that you are in the development environment because it says so in the sidebar and at the top of the page.

You can see all the environments you are integrated with in the left navigation bar under Environments.

Deploy To a New Environment

When you are ready to start using Frontegg live in your application, effortlessly deploy your Frontegg development settings to a Frontegg production environment.

To deploy your development environment to production, go to your development environment.

Click the Publish button.

Confirm that you are ready to deploy it.

If it is your first time deploying the development to production, enter your production url.

You will see a loader. This is because the Frontegg API is waiting for your application to send a call to it from the url that you input.

To do that, in a separate browser window, go to your production application url and open the Frontegg login bog.

This makes a call from your application's production url to the Frontegg API.

πŸ“˜

If you do not send a message from your application to the Frontegg API, Frontegg cannot activate your production environment.

The easiest way is to just open the Frontegg login box from your application as described above.

After making the call, you should see a welcome to production message in your Frontegg Portal.

When you go to production, Frontegg automatically copies development environment configurations over to the production environment.

🚧

Currently, the environment configurations that Frontegg copies are: Social Logins, SSO / SAML, Captcha, ​Emails, ​Hooks.

This eliminates any need for you to do that manually.

πŸ“˜

Just the settings, not the data

Frontegg does not deploy the data from your development environment to your production environment.

This means that the tenants and users and other data you created and managed in your development environment will not be in your production environment.

You can find your production environment in the Frontegg Portal sidebar.

From the sidebar, go to Environments ➜ Production.

You should see your production environment.

The production environment looks virtually identical to the development environment.

You should see all the same configurations in production that you setup in the development environment.

You can also add a new environment from the side bar (check the gif bellow)
After clicking the + icon, you can select the environment and enter your App url, opening up a new environment to play with!

Although the environments look the same, you can tell that you are in the production environment because it says so in the sidebar and at the top of the page.

πŸ“˜

Because Frontegg does not move your tenant and user data from development to production, you will have different tenant and user data in your development and production environments.

Using Development After Integration

You can use the development environment and make changes to it after you deploy to production without worrying about impacting the production environment until you want to.

Go to your development environment. Make changes to your configurations there.

When you are ready, deploy the changes from your development environment to the existing production environment by clicking the Publish button again.

You will not be prompted to input a production url again because you already did it.


Did this page help you?