Step 1. Create a service
Step 2. Select the project to deploy
If you are logged in to Hostman with your GitHub, GitLab or Bitbucket account, at this point you will see the repository with your projects, including the private ones.
To access a different repository, click Connect another repository.
If you didn’t use your Git account credentials to log in, you’ll be able to access the necessary account now, and then select the project.
Step 3. Configure the build settings
Next, the Website customization window will appear.
Choose the Static website option from the list of frameworks.
The Directory with app points at the directory that will contain the project's files after the build. For Ember.js the directory is dist.
The standard build command will be:
You can modify the build command if needed. You can enter multiple commands separated by &&.
Step 4. Deploy
Click Deploy to start the build process.
Once it starts, you will enter the deployment log. If there are any issues with the code, you will get warning or error messages in the log, specifying the cause of the problem.
Usually the log contains all the debugging data you'll need, but we are also here to help you solve the issues, so do not hesitate to contact us via chat.
When the deployment is complete, you will receive an e-mail notification and also see a similar log entry:
Your project is up and ready.
npm ERR! enoent ENOENT: no such file or directory, open '/opt/build/package.json'
This error means that you don't have a package.json file in a build directory.
To solve this, you need to update your build command so it includes the name of the directory where the package.json file is located:
cd directory_name && yarn i && yarn run build