I’m trying to get started with the new DigitalOcean Apps. Since I’m using a non-standard static site generator (jigsaw). I have problems finding solid documentation on how to set the static site build or output path.

I did find some documentation and samples showing a .do folder with an app.yaml and other yaml configuration, although trying to use the same did not work for me. It seemed like those config files got ignored by DO and I also couldn’t find any settings to add configuration on my own.

The error message I’m getting is the following:
=> Static site output directory is not explicitly set, attempting to look for static files
sitename | 15:34:47 Checking /workspace/_static
sitename | 15:34:47 Checking /workspace/dist
sitename | 15:34:47 Checking /workspace/public
sitename | 15:34:47 ! No static site build path was found

I’d be glad for any help. Thanks.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer

Hello @dirgl

By default, our system will look at the directory: static, dist, public at this time. You can explicitly set the output directory path for the rendered assets in the app specification with the API or doctl using the outputdir field.

Please note just creating the app.yaml file inside.do directory won’t update the app. In our sample apps, those files are created for reference. You have to create the app.yaml file locally and then apply it to your app using API or doctl.

Documentation links which might help:
https://www.digitalocean.com/docs/app-platform/references/app-specification-reference/
https://www.digitalocean.com/docs/app-platform/references/command-line/
https://www.digitalocean.com/docs/app-platform/references/api/

Tip: When submitting any questions related to App Platform please add the tag “DigitalOcean App Platform” which will filter the community questions to App Platform Specialists.

Cheers,

Dikshith

  • Request that DO add _site to the list of output directory paths, for built-in support of SSGs like Eleventy that use that. (I tried the doctl method with my repo but couldn’t get doctl -c to accept my chosen config YAML file.)

Submit an Answer