If you’re using a different Git provider like Bitbucket or GitLab, check out our guides for importing a GitHub repository into either git service:

• Import a Repository From GitHub to Bitbucket
• Import a Repository From GitHub to GitLab

Python

• Python
• Django
• Flask

Go

• Go

PHP

• PHP
• Laravel
• Statamic
• PHP to Send Emails

Node.js

• Node.js
• Node.js with a Dockerfile
• Node.js To Send Emails
• Node.js With Background Worker and API

Ruby

• Ruby on Rails
• Ruby on Rails with a Dockerfile

Java

• Java

Scala

• Scala

Other

• Deno
• NuxtJS

Static Sites

We are working on adding static site hosting services. Until that’s ready, you can use our Application Hosting with an appropriate setup to host static sites.

• Astro Static Site
• Cuttlebelle
• Docusaurus
• Eleventy
• Gatsby Static Site
• Jekyll
• Jigsaw Static Site
• Qwik
• VuePress

The post App Quick Start appeared first on Kinsta®.

Basic Details

This section shows the following details:

• Application name
• Git repository and branch
• Data center location
• Build path
• If automatic deployment is enabled or not

Edit Details

You can change the following by clicking Edit details:

• App name: This is the name of your application in MyKinsta.
• Branch: The Git repository branch.
• Automatic deployment on commit: When this box is checked, your application will automatically deploy each time a commit is made to the branch selected above.
• Build path: This only applies to buildpacks. This is the path in the repository to the files required to build the application. Most applications are built from the repository root, and the Build path defaults to this (.). If you have a different build path, specify it here. For example, if your application needs to be built from a subdirectory (e.g. app), enter that subdirectory path in the Build path field: app. This is also useful if you have a monorepo.
• Dockerfile path: This only applies to Dockerfiles. This is the path to your Dockerfile relative to the repository root. For example, if your Dockerfile is in the repository root, enter Dockerfile in that field. If your Dockerfile is in a subdirectory named app, enter the path to the Dockerfile: app/Dockerfile.
• Context: This only applies to Dockerfiles. This is the path in the repository we need access to so we can build your application. Most applications are built from the repository root, and you can enter the repository root (.) in the Context field. If your application needs to be built from a subdirectory (e.g. app), enter that subdirectory path in the Context field: app.

If you change anything beyond the application name, you must manually deploy your application again, which you can do on the Deployments page.

Buildpacks

In this section, you can view and manage your application’s buildpacks. If you add or edit buildpacks, you must manually deploy your application again, which you can do on the Deployments page.

Internal Connections

In the Internal connections section, you can view and manage your application’s internal connections with databases or other applications hosted at Kinsta. Do not copy and paste your internal connection details into your environment variables. Click Add connection and select the option to Add environment variables to access the database. This will automatically populate the environment variables from the database or other application you’re connecting to.

If you add or remove a connection, you must manually deploy your application again, which you can do on the Deployments page.

Environment Variables

Environment variables feed your application information from outside of the running of the application. They typically set things like database connection details and API keys. For more details, see our Environment Variables guide.

If you add, edit, or remove environment variables, you must manually deploy your application again, which you can do on the Deployments page.

Suspend or Resume Application

Suspending your application stops your application from running without deleting it. This doesn’t change or remove anything in the application itself. Connections to the application remain in place but will not work while the application is suspended. You will not incur any costs for the application during the suspension.

Click Suspend application and confirm the suspension by clicking Suspend application again in the modal/pop-up.

When you’re ready to restart your application, click Resume application and confirm the restart by clicking Resume application again in the modal/pop-up.

Delete Application

If you no longer need the application, click Delete application to completely remove it. The option to delete an application is only available when the application is running. If you suspend your application, you must resume it to delete it.

The post Application Settings appeared first on Kinsta®.

Details

In this section, you can see where the application is deploying from, including the branch, a link to the latest deployment, and if automatic deployments are enabled or not. If automatic deployment is enabled, the application deploys every time a commit is made to the branch in the GitHub repository. You can enable or disable automatic deployments in the application’s Settings.

To deploy the most recent commit again, click Redeploy.

To roll back to the most recent successful deployment, click Rollback.

History

In this section, you can see a list of all the previous deployments. You can also manually deploy the application by clicking Deploy now.

To deploy a previous commit again, click the kebab (three-dot) menu for that commit and click Redeploy.

Deployment Details

If you click on any of the previous deployments, you’ll be brought to a dedicated page that shows the Deployment details. This shows information about the deployment, including:

• The name of the GitHub repository and branch.
• The Commit ID, with a link to the commit on GitHub.
• Who initiated the deployment.
• The deployment start date and time.
• The time it takes for the deployment to finish (Deploy time).
• The commit message.

If you want to change the resource settings to increase or decrease the CPU and RAM for the build process, click Change settings. This takes you to the Processes page and opens the Update build modal/pop-up, which allows you to make those changes.

Deployment progress

To redeploy the application from this commit, click Redeploy.

The Build process shows the status of the build:

• Running: The build process is still running. If the build process takes a long time or you’ve made a change and want to stop the build, you can click Cancel build.

  

• Completed: The build process has finished and is successful.
• Failed: The build process has failed. In this case, check the build log to identify where the process may have failed.

You can click the Build process to expand it and see the build log.

The Rollout process shows the status of the rollout.

Deployment shows the deployment status. When the deployment is complete, it shows the URL of the application and a link to view the runtime logs.

The post Application Deployments appeared first on Kinsta®.