Set up configurations per environment

Main > Using Liquid for building your application > Set up configuration per environment

Liquid structures the way platform components and common (util) services are set up and parameterized for providing high level (abstract) common behavior.

Take a look at related key concepts of Liquid
Platform Abstraction Layer

Likewise, each project type has configuration files considering the following environments:

• Development (default file): used for development and test on local machines (developer's);
• Integration (.Integration file): used for doing automatic continuous integration (CI) and continuous testing (CT) on centralized machines with test data;
• Quality Assurance (.Testing file): used for doing automated and exploratory system tests on centralized machines with test data;
• Staging (.Staging file): used for doing automated smoke system tests and installation tests on centralized, production-like machines and data;
• Production (.Production file): used for doing continuous delivery (CD) on centralized, production machines and data.

See how to configure each Liquid service and specific platform components:

Service	On Azure	On AWS*	On Google
ApiWrapper	-	-
Authentication	-	-
CORS	-	-
LightApi	-	-
MediaStorage	AzureBlob	S3	GoogleStorage
MessageBus	ServiceBus	SqsSns	GooglePubSub
Repository	CosmosDB	DynamoDB	GoogleFireStore
Swagger (OpenAPI)	-	-

TO BE NOTED: .NET Core configuration is stored in appsettings*.json files, Angular's in environment*.ts and React's in environment*.js.

See how this is done in both front-end and back-end of Liquid Hotel360 sample application.

(*) Currently only Azure services have Liquid cartridges released. See Roadmap for further information.