Skip to main content

Deploy Your First Container

Deploying your first container on Inteleto is quick and seamless. Follow these steps to set up your deployment and get your application running in minutes.

Have a Configured Dockerfile​

Before deploying your application on Inteleto, you need a Dockerfile in your repository that generates a working Docker image. This method is widely used across various platforms and services, ensuring compatibility and ease of deployment.

A Dockerfile is a script that defines the steps to build a Linux-based container with all the necessary dependencies, configurations, and commands to run your application in a production environment.

If you're new to Docker, there are many resources available online to help you create a Dockerfile for your specific technology stack. You can search for guides like "How to Create a Dockerfile for a Node.js Express App?" or "Dockerfile Setup for a Python Flask Application."

Ensure Your Dockerfile Works Locally​

Once you have created a Dockerfile in the root of your repository, test it locally to confirm that your application runs correctly inside a container:

docker build . -t myimage:latest
docker run --rm -p 8080:8080 myimage:latest

Replace 8080:8080 with the port your application uses. Then, open your browser and navigate to http://localhost:8080 (or the appropriate port) to verify that your application is accessible.

If everything works as expected, you are ready to move on to the next steps in the deployment process.

Access Your Account​

Log in to your Inteleto account and navigate to the Apps menu.

Apps page

Deploy a New App​

Click on the Deploy new App button to start the deployment process.

Deploying via GitHub​

Click on Connect to Github. After that, you'll be asked to set up the GitHub App that connects Inteleto to your repositorues. Click on the button Allow access. You will be prompted to install the Inteleto GitHub App.
When installing, you can grant access only to the repositories you want to deploy.

Install GitHub app step 1

Install GitHub app step 2

Once authorized, you will see a list of repositories that you have allowed access to. Note that there's also a button to manage access to the repositories connected to GitHub.

Connected repositories

Configure Your Deployment​

Configure deployment

Select the repository you want to deploy from the list and configure:

  • Name: The name of the application. This should be unique and contain only letters, numbers and "-". It must start with an alphabetic letter and end with an alphabetic letter or a number.
  • Production branch: The branch that will be automatically deployed when a new commit is pushed into it (e.g., main or master).
  • Container type: The specs of the contaniers that will run your application (they differ mainly on CPU, RAM and Cost). For new applications, we recommend starting with the type "Basic I", and upgrade it later.
  • Deployment preset: Represents the method used to build the application. The option Dockerfile will be selected by default.
  • HTTP port number: The port number of the application running inside the Docker container. There should be a HTTP server listening on that port inside your container. All of the traffic will be redirected to it to access your application externally.

After configuring, you can click on deploy.

Deployment​

Once confirmed, Inteleto will automatically build the Docker image and deploy your application. This process could take some time. Next, proceed to access and configure your newly deployed application.

App building

info

If your application fails to deploy, please follow the steps to debug your deployment.

Containers use ephemeral storage​

Containers in Inteleto use ephemeral storage, which means any data written to the container's filesystem is temporary and will be lost when the container stops, restarts, or is relocated to another host. This includes:

  • Files created or modified during runtime
  • Logs written to the filesystem
  • Uploaded files stored locally
  • Any other data saved to the container's disk

For data that needs to persist between container restarts or deployments, you should use databases, block storage and external services.

This ensures your application remains stateless and can scale horizontally without data loss concerns.