How It Works

When you connect your Github, Gitlab or Bitbucket repository, Hostman does the following:

1. Sets up a cloud server with all the necessary software, such as a web server, Docker service, and others. It also sets up all security and performance settings following best practices.
2. Pulls the code from your Github, Gitlab or Bitbucket repository.
3. Installs all dependencies stored in special files, such as requirements.txt for Python or package.json for Node.JS.
4. Builds the code and checks whether it was built correctly. It also provides you with a build log, which you can easily check if anything goes wrong during the build process.
5. Launches a Docker container for backend apps with the necessary environment and runs your application inside it.
6. Creates a Hostman subdomain for your application. You can use this domain for testing purposes or for requests inside the app, if it works for you. Of course, for production we recommend buying your own domain.
7. Configures Nginx to proxy your domain to the application.
8. Installs a Let’s Encrypt SSL certificate to make sure all the data is reliably protected. Hostman uses an SSL connection between all the services in its architecture.

When you push a new commit to your Git repository, the same cycle is repeated again: Hostman pulls the code, installs dependencies, builds the application, and so on. This includes launching a new Docker container, which will have no data from the previous container. This way we ensure a clean deployment.

Deploying frontend applications has one important difference from backend applications: after the build we do not create a Docker container, the application is stored in a directory on the server. However, with Hostman you don’t have to configure the server environment because, as with the backend applications, we will do everything for you:

• pull the code from the repository, 

• install dependencies and software, 

• configure Nginx, 

• issue an SSL certificate,

• build your application.

Hostman will automatically deploy the changes if you leave the autodeploy option enabled.