Application Launcher

Node JS

Getting started

Node JS

Getting started

In Front End Hosting - Basic, one Static Site application such as Static Site Generator (SSG) is provisioned with three environments:

Viewing an application

Sign in to the Cloud Platform user interface.
In the top menu, click Develop.
Select your organization.
Select an application.
Click View <application name>.
New environments are provisioned with the default content page.
To verify that a site is working correctly, visit the default URL of a specific environment.

In Front End Hosting - Basic, one Static Site application such as Static Site Generator (SSG) is provisioned with three environments:

Sign in to the Cloud Platform user interface.
In the top menu, click Develop.
Select your organization.
Select an application.
Click View <application name>.
New environments are provisioned with the default content page.
To verify that a site is working correctly, visit the default URL of a specific environment.

In Front End Hosting - Basic, one Static Site application such as Static Site Generator (SSG) is provisioned with three environments:

Sign in to the Cloud Platform user interface.
In the top menu, click Develop.
Select your organization.
Select an application.
Click View <application name>.
New environments are provisioned with the default content page.
To verify that a site is working correctly, visit the default URL of a specific environment.

Add a public key to your Acquia profile.
Clone the application’s repository.
Configure acquia_config.yaml or acquia_config.yml.
The acquia_config.yaml or acquia_config.yml file must be located in root folder of your project containing the following configuration:
```
output_directory: "out/"
root_directory: "./"
```
Configuration properties:
- Output directory: This output directory contains build outputs such as HTML, CSS, and JavaScript files, which are served for the Front End Hosting - Basic hosting. The default output directory is html/. This directory can be overridden by specifying the output directory in the acquia_config.yaml or acquia_config.yml file.
- Root directory: The main directory of your project may not always align with your application's build root. For example, a repository might have a frontend directory, which contains a stand-alone Next.js application. Therefore, you must set the root directory to ensure that the commands are executed from the correct directory of your project.
Create a new branch and push your deployable artifact along with acquia_config.yaml or acquia_config.yml.
Deploy the branch <new-branch> from the Cloud UI.
For more information, visit Deploying code in the same environment.

For information about viewing your subscription details, visit Viewing subscriptions.

The acquia_config.yaml or acquia_config.yml file must be located in root folder of your project containing the following configuration:

output_directory: "out/"
root_directory: "./"

Configuration properties:

Output directory: This output directory contains build outputs such as HTML, CSS, and JavaScript files, which are served for the Front End Hosting - Basic hosting. The default output directory is html/. This directory can be overridden by specifying the output directory in the acquia_config.yaml or acquia_config.yml file.
Root directory: The main directory of your project may not always align with your application's build root. For example, a repository might have a frontend directory, which contains a stand-alone Next.js application. Therefore, you must set the root directory to ensure that the commands are executed from the correct directory of your project.

Create a new branch and push your deployable artifact along with acquia_config.yaml or acquia_config.yml.

Deploy the branch <new-branch> from the Cloud UI.

For information about viewing your subscription details, visit Viewing subscriptions.

If this content did not answer your questions, try searching or contacting our support team for further assistance.

If this content did not answer your questions, try searching or contacting our support team for further assistance.