Skip to main content

Configurations

This documentation explains how to update the configuration settings that control how Hostless builds and deploys your application code. These settings define various aspects of your application's deployment pipeline, including:

  • Source Code Location: Specify the location of your application's source code repository.
  • Build System: Define the tools and commands used to build and package your application before deployment.
  • Start Command: Indicate the command used to start your application within the Hostless environment.

Configuration Parameters​

The core configuration parameters for your Hostless application typically include:

  • Github Account: The username associated with your Github account that holds the application code repository.
  • Repository: The name of the specific repository within your Github account that contains your application code.
  • Branch: The branch within the repository that Hostless should use for deployments. By default, Hostless might use the "main" branch, but you can configure it to use a different branch for deployments (e.g., "development" or "release").
  • Build System: Specify the build system or toolchain used to prepare your application for deployment. Hostless supports two build systems. Nixpicks(Automatically detects programming language) and Dockerfile. The Dockerfile should define the specific commands required to build and potentially package your application.
  • Build Command: This setting specifies the command Hostless should execute to build your application before deployment. The build command is responsible for compiling, packaging, or otherwise preparing your code for deployment. It should generate the necessary artifacts (e.g., binaries, executables) that can then be deployed to the target environment.
  • Post-Build Command: This setting specifies the command Hostless should execute after the build of your application or before deployment. These commands allow you to automate essential operations such as running migrations, clearing caches, seeding databases, or performing custom setup scripts. By integrating post-build commands, you can ensure your app is fully prepared for deployment, reducing manual intervention and streamlining the deployment pipeline.
  • Start Command: This setting defines the command Hostless should execute to start your application within the deployed environment. This command typically launches the main process of your application.

Note: The specific terminology and user interface for managing these configurations might vary slightly depending on the Hostless version you are using.

Updating Configurations​

Hostless provides a user interface or configuration management tools to update these settings. The general process typically involves:

  • Accessing the Hostless application settings or configuration management interface.
  • Locating the section for deployment or application settings.

Updating the desired configuration parameters:​

  • Github Account: Enter the username for your Github account.
  • Repository: Specify the name of the application code repository within your Github account.
  • Branch: Select the branch you want Hostless to use for deployments.
  • Build System: Choose the appropriate build system for your application.
  • Build Command: Specify the command Hostless should execute to build your application before deployment.
  • Post Build Command: Specify the command Hostless should execute after your build is complete or before deployment of your application.
  • Start Command: Provide the command to start your application within Hostless.
  • Saving the changes to the configuration.

Please note: Changes to certain configuration parameters, like the branch or build system, might trigger a new deployment depending on your Hostless settings.