Wed, 1 Feb, 2023

Create

Instructions on Creating Environment in 01Cloud

Introduction

This article aims to provide a comprehensive guide on how to create an environment in 01Cloud. It is important to note that there are three different types of environments available in 01Cloud, namely custom, template, and container registry. Although the steps involved in creating these environments are similar, it’s worth noting that some custom installation options may not be available for template and container registry environments. We’ll walk you through each step of the process to ensure that you have a clear understanding of how to create an environment in 01Cloud.

Step 1: Access the Application

From the front page of the application, click the CREATE ENVIRONMENT button to begin the environment creation process.

front page

Step 2: Select the Environment Version

On the next page, you will be prompted to choose the version of the environment you wish to create and click CONTINUE button.

Note: Environment Version can only be selected for Template and Custom Environment

Create your environment

Step 3: Choose Quick or Custom Installation

You will have two options: Quick Installation and Custom Installation. If you choose Quick Installation, all fields will be set to default values during the environment creation process.

quick installation

If you choose Custom Installation, you will have various options for customizing the environment.

custom installation

Step 4: Customize the Environment

There are several options available for customizing your environment, including:

Note: Environment Variables, Deployment Strategy, Scripts and Startup Job Options are only available for Custom and Container Registry Environment. Triggers Option is only available for Custom environment.

  • System Variables

    System variables are used by the environment to run the system. You can add two system variables in a environment: Custom Domain and Running Port. The Custom Domain allows you to specify a custom domain for the environment, while the Running Port indicates the port on which the application or environment will run.

    system variables

  • Environment Variables

    Environment variables are used to pass configuration parameters to containers and provide information about the environment in which the containers are running. They also allow for secure management of sensitive information.

    environment variables

    When you click the ADD VARIABLE button, you can add a user variable and value to set the environment variable. There is also a “Secret” checkbox that, when checked, stores the environment variable as a secret.

    add environment variables

  • External Secrets

    The External Secrets tab allows you to access the external secret feature, which allows you to use secrets from external secret providers (e.g. AWS, HashiCorp, GCP) in 01Cloud environments. You can learn more about the external secret feature in this article: External Secret feature in 01Cloud .

    external secrets

  • Triggers

    The Triggers section provides three available options, as depicted in the following illustration:

    triggers

    • Prevent build on create
      • This option allows users to add the necessary add-ons and configurations to the environment without triggering the CI/CD process. They can manually initiate the CI/CD process from the CI/CD tab.
    • Push
      • This option automatically triggers the CI/CD process when code is pushed into the branch from which the environment is built.
    • Tag
      • This option automatically triggers the CI/CD process when code is tagged for release.
  • Deployment Strategy

    Deployment strategies refer to the methods used to release new versions of software into production environments. There are several deployment strategies available in 01Cloud that organizations can use, depending on their needs and requirements.

    • AB-Testing Deployment Strategy

      AB testing deployment strategy

      In this strategy, a small portion of users are redirected to the new version of the software while the rest of the users continue to use the old version. This allows organizations to test the new version before releasing it to all users.

    • Blue-Green Deployment Strategy

      Blue-Green Deployment Strategy

      In this strategy, two identical production environments are created, one for the current version of the software (blue) and one for the new version (green). When the new version is ready, all traffic is redirected to the green environment, and the blue environment becomes the backup. This approach minimizes downtime and allows for easy rollback in case of issues.

    • Canary Deployment Strategy

      canary deployment strategy

      In this strategy, a small portion of users are redirected to the new version of the software, similar to AB-Testing. The difference is that in this approach, the new version is deployed to a limited number of servers, rather than a limited number of users.

    • Rolling Update

      rolling update deployment strategy

      In this strategy, the new version of the software is gradually rolled out to the servers, one at a time. This allows organizations to deploy new features without causing downtime or disrupting users. The update process is typically automated, and rollback is possible if issues are detected.

  • Scripts

    Scripts are automated programs that simplify repetitive tasks and processes. They are written in a scripting language and executed by a scripting engine or interpreter.

    scripts

    Build scripts automate the process of building a software application. They compile the source code, link libraries, and create the final executable, making the build process repeatable and reliable.

    Run scripts automate the process of running a software application. They set up the environment and launch the application, making it easy to run and ensuring consistent and reliable execution, even on different machines or environments.

  • Startup Job

    The Startup Job creates an initialization container that is executed before the entire environment. You can specify the name of the job, along with the image options such as Alpine or Busybox, and specify the code you wish to run as a startup job prior to launching your environment.

    startup job

  • External Logger

    The option to enable an external logger is also available, giving you the capability to store the logs of your environment in any external logging service provider. Currently, 01Cloud supports S3, Cloudwatch, Elastic, Loki, Kafka, and GCP. You can explore more about external logging feature in here .

    external logger

Step 5: Continuing the Environment Creation Process

After customizing your environment, continue with the environment creation process by clicking the CONTINUE button.

continue and back

Step 6: Providing Environment Details

Now provide a name for the environment. The default name is development and you can select the branch of your code you want to create the environment for. You can also select the amount of resources you want your environment to use.

create environment with branch

Step 7: Configuring Auto Scaling

If auto scaling is enabled, you will be presented with auto scaling options. You can set the maximum and minimum replicas for your environment and specify the CPU and memory usage of the environment.

auto scaling options

In the advanced settings, there are two columns: Scale Up and Scale Down. Scale Up adds replicas and Scale Down decreases replicas. The advanced settings include:

auto scaling advance settings

  • Average Usage Interval: Scales up or down the replicas if the usage threshold is reached for the defined amount of time.

  • Change by: Specifies the number of replicas to add or remove while scaling your environment.

  • Average Change Interval: Specifies the average time between adjustments made to the number of replicas in a deployment to match changes in demand.

Step 8: Initiating Environment Creation

Click the CREATE ENVIRONMENT button to start the environment creation process.

Step 9: CI/CD Tab

At first, you will be directed to the CI/CD tab inside the environment where the CI/CD process will be completed.

Note: You will be directed to the CI/CD tab only in Custom environment.

ci/cd tab

Step 10: CI/CD Completion

After the completion of the CI/CD process, the environment status will change from Pending to Creating.

Note: Only in Custom Environment.

ci/cd completion

Step 11: Overview Tab

You can view the activity log and other basic environment status in the Overview tab.

environment overview

Step 12: Running Environment

Once all processes are successful, the environment will be running.

running environment

Step 13: Accessing Your Application

You can access and use your application from the domain provided by 01Cloud in the status section. Simply click the link to run your application.

node chat website

Conclusion

Now, you have successfully created a environment on 01Cloud. You can now explore different tabs in the environment, such as the CI/CD tab, the Overview tab, and others, to understand their functions and make the most out of your environment. For a more detailed understanding of the different tabs in the environment, you can view the documentation available on the 01Cloud website.


On this page: