Static by default
How to publish a Hexo site
Hexo generates a finished blog into a folder. The generate step is the one that matters here; the deploy step it ships is for other targets.
- Build command
- npx hexo generate
- Folder to upload
- public
Free plan, free SSL, no credit card.
-
Build the project
Run npx hexo generate in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build.
-
Find the output folder
The build writes a finished site to public. That folder, not the project folder, is what gets uploaded.
-
Drag it in
Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL.
Worth knowing about Hexo
Use
hexo generate, nothexo deploy. The deploy command pushes to a configured target such as a Git remote; here you want the folder it generated.The output folder is
public, andpublic_dirin _config.yml can change it.Set
urlin _config.yml to the address the site will actually live at, and leaverootas/. Arootleft pointing at a subfolder breaks every asset path on a subdomain.
Did an AI tool build this project?
Hosting an AI-generated website covers the question that comes before the build command: whether what you are holding is a single file or a project, and which of the two every tool actually hands back.