Skip to main content

Applications

An application is a logical unit typically linked to a repository or, in the case of a mono-repo, to a folder within it. Applications are organized into namespaces, which often represent teams or functional areas (e.g., checkout, billing).

Create a new application​

Whether you are starting a new application from scratch or migrating an existing application to nullplatform, you have to create a new application. To do this:

  1. Go to your namespace's home page and click + Create application.

  2. Give your application a descriptive name.

  3. Choose to create a new repository or import an existing one.

    You can either create a new repository from a template or import an existing one. In both cases nullplatform integrates with your repository provider (GitHub, GitLab, Azure DevOps, etc.) to:

    • For new repositories: Create the repository using the selected template.
    • For new and imported repositories: Add an API key for CI workflows to push assets, builds, releases, and metadata.

How repositories are named​

When you create a new application from scratch, we automatically generate a repository for you using this naming convention:

  • https://my-git-provider/my-organization/${namespace-slug}-${application-slug}.

Example:

If your organization is acme-corp and you're setting up a transactions api application within the wallet namespace, the repository URL would look like this: https://github.com/acme-corp/wallet-transactions-api.

Customizing repository naming patterns

You can define custom naming patterns for repositories to better align with your organization's conventions.
To learn how, see Setting custom naming patterns.

Continuous Integration​

Any application created from a nullplatform template is already set up with a working CI pipeline that will build, test, and upload the assets to the right location for deployment (e.g., Docker images in case of server instances, zip packages for serverless functions).

While we recommend not altering the CI pipeline and maintaining it as simple as possible, you can change it in any way you want as long as you keep the steps that communicate with nullplatform and with the cloud provider.

Importing an existing repository​

If you're migrating an existing codebase, you'll want to create a new application by importing an existing repository.

In this case, you will enter the repository name, and we will automatically:

  1. Create the application in nullplatform
  2. Inject the required secrets into your repository so you can set up the CI pipeline.
Create a branch for your new CI pipeline

When migrating an application, consider creating a new branch where you can test your new CI pipeline without disturbing the main branch where production code resides.

Once the application has been created on nullplatform, you will have to:

  1. Adapt your CI pipeline to deliver the assets to the right location. You can read about nullplatform CI/CD integration here
  2. (Server-based Applications) Make sure the application is listening on port 8080 and that it is returning a 200 OK status code for the health url (the default is /health).

Once you start committing to your application, you'll be able to see the builds in the Build section of your application's dashboard.