FAQs
This page details the FAQs that are specific to Front End Hosting - Basic.
How do I configure the acquia_config.yaml or acquia_config.yml file?
The Front End Hosting - Basic offering supports both .yaml and .yml extensions.
To configure the acquia_config file, insert the following configuration details at the root level of your acquia_config.yaml or acquia_config.yml file:
output_directory: "out/"
root_directory: "./"To avoid syntax errors, ensure that you add new properties or settings in the yaml format.
How do I configure the output directory for Front End Hosting - Basic applications?
To configure the output directory for Front End Hosting - Basic applications:
- In the root directory of your project, locate and open the
acquia_config.yamloracquia_config.ymlfile. Configure the
output_directoryparameter to specify the output directory.The following are the ways to specify output directory formats:
Output Directory at SVN Repo Root Directory:
To set the output directory at the root of your SVN repository, use the following format:
output_directory: "output_dir"Output Directory with absolute directory path relative to acquia_config.yaml or acquia_config.yml:
To set the absolute directory path relative to
acquia_config.yamloracquia_config.ymlfor the output directory, use the following format:output_directory: "./output_dir"Nested Directory path:
If the output directory is within other directories, use the following format:
output_directory: "path/to/output_directory"
What is the importance of providing additional parameters in the acquia_config.yaml or acquia_config.yml file?
Providing necessary parameters or ensuring that the artifact is in the default directory is important. If you do not provide additional parameters in the acquia_config.yaml or acquia_config.yml file, the Front End Hosting - Basic application defaults to searching for the SSG artifact within the html directory. If the application does not find the artifact in the html directory, the deployment fails.
Does Front End Hosting - Basic support Node.js site hosting?
Front End Hosting - Basic does not support Node.js site hosting.
Does Front End Hosting - Basic support SSR/ISR features?
Front End Hosting - Basic does not support SSR/ISR features.
Which Node.js versions are supported by Front End Hosting - Basic?
Front End Hosting - Basic currently supports Node.js versions that are in the active Long-Term Support (LTS) stage. These versions receive ongoing community updates to ensure stable and secure operations for your projects. For more information on the Node.js supported versions, visit Resources.
Which frameworks are supported by Front End Hosting - Basic?
Front End Hosting - Basic supports any NPM-compatible JavaScript framework that generates static content serviceable by an HTTP server such as Nginx.
The following table lists the frameworks that are currently compatible with Front End Hosting - Basic:
Framework | Default output directory |
|---|---|
Angular | dist |
Astro | dist |
Brunch | public |
Docusaurus(v1) | build |
Docusaurus(v2) | build |
Eleventy | _site |
EmberJS | dist |
Gatsby | public |
Hexo | public |
Ionic Angular | www |
Ionic React | build |
NextJS | out |
NuxtJS | .output/public |
Parcel | dist |
PolymerJS | build/es*-bundled |
Preact | build |
React | build |
Sanity | dist |
Sapper | __sapper__/export |
Scully | dist/static |
Stencil | www |
Storybook | storybook-static |
Svelte | public |
SvelteKit (v1) | output/static |
UmiJs | dist |
Vite | dist |
Vitepress | docs/.vitepress/dist |
VueJS | dist |
Vuepress | src/.vuepress/dist |
How do I deal with deployment failures or errors?
The following table lists the errors and their resolution:
| Error | Resolution |
|---|---|
| Deployment failed: The output directory specified in acquia_config.yaml/acquia_config.yml does not exist in the current branch. Please verify that the directory is present and try the deployment again. | Ensure the <output_directory> indicated for the output is present at the root of the SVN repository. |
| Deployment failed: The static content file (index.html) was not found in the output directory specified in acquia_config.yaml/acquia_config.yml. Please verify your build process and ensure the artifact exists before redeploying. | Ensure that the SSG artifact is in the <output_directory> as defined in the |
| Deployment failed: Output directory is not defined in acquia_config.yaml/acquia_config.yml. Default output directory does not exist in current branch. Please verify that the directory is present and try the deployment again. | Ensure that the SSG artifact is located within the html directory after a successful build, or ensure that the correct output directory is specified in the acquia_config.yaml file by adding the necessary output_directory parameters. |
| Deployment failed: Output directory is not defined in acquia_config.yaml/acquia_config.yml. The static content file (index.html) was not found in default output directory. Please verify your build process and ensure the artifact exists before redeploying. | Ensure the SSG artifact is located in the html directory denoted as the default output directory. If a different output directory is being used, add or update the acquia_config.yaml file to include the required output_directory parameter pointing to the correct artifact location. |
| Deployment failed: Output directory size exceeds 10GiB. | Limitation: Front End Hosting - Basic does not support SSG artifacts larger than 10GiB. Artifacts exceeding this size are not compatible. |
How do I download logs?
To download logs:
- Navigate to the required environment and select Logs.
- Click the Download tab.
- Find the log list and click the kabab menu besides the entry that you want to download.
Click Download.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.