How does the app creation process determine whether a source is static?

I used npm to make a website, but I don’t need to run a node server to run the site – it is static since all I have to do is open the index.html and I get all my functionality (lots of clientside js). So when I connect the repo with this site I want DO to detect that the site is static so I don’t have to pay to host it. But static/start plan is not an option.

How does the app creation process determine whether the source I’m providing is static? Is it because there’s a package.json file that it assumes I must need to run a node server in order to serve the website? What am I missing?

Submit an answer
Answer a question...

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Accepted Answer

Hi there,

In the App Platform, a static site is a type of resource that only consists of a build process that produces static assets.

These assets are not served by an application runtime (such as Ruby, Python, or PHP), but instead are served by a simple HTTP server. Static sites therefore have no run command.

Common static site generators include Jekyll, Hugo, and Gatsby, all of which have samples available in Sample Apps.

Is your repository public? If so can you share it here so I could check it out?