BUILD & DEPLOY

Deploy Frontend Apps & Static Sites

Build on your computer, ZIP the generated output, and upload it. Linkyhost serves the resulting browser assets without running your framework or project source.

Asset-only by design. Linkyhost serves the files already present in your ZIP. It does not install dependencies, run a build, or provide Node.js, PHP, Python, Ruby, serverless functions, API routes, SSR, background jobs, or WebSockets.

Plan depends on the built files. Every multi-file website ZIP requires Pro, including HTML/CSS-only output and JavaScript framework builds. One standalone HTML page can use the Free plan.

React & Frontend Frameworks

Deploy browser-ready applications and static exports from React and related frameworks.

Next.js

Output: out/

React

Output: dist/ for Vite, or build/ for Create React App

Angular

Output: dist/<project>/browser/

Svelte

Output: dist/ for a Svelte app built with Vite

Gatsby

Output: public/

Remix

Output: build/client/ for Remix SPA mode

SvelteKit

Output: build/

Create React App

Output: build/

Preact

Output: dist/ for the standard Vite setup

Ember.js

Output: the generated directory that contains index.html

Backbone.js

Output: the generated directory that contains index.html

Qwik

Output: dist/ when using the Qwik static adapter

RedwoodJS

Output: web/dist/

Meteor

Output: the generated directory that contains index.html

Sapper

Output: the generated directory that contains index.html

Scully

Output: the generated directory that contains index.html

React Static

Output: the generated directory that contains index.html

Frontity

Output: the generated directory that contains index.html

UmiJS

Output: the generated directory that contains index.html

Stencil

Output: the generated directory that contains index.html

Webiny

Output: the generated directory that contains index.html

Prismic

Output: the generated directory that contains index.html

Phenomic

Output: the generated directory that contains index.html

Cuttlebelle

Output: the generated directory that contains index.html

Modern Frontend Frameworks

Deploy client-only production builds from modern web tooling.

SolidJS

Output: dist/ for a client-only Solid/Vite app

Vue Ecosystem

Deploy Vue applications and statically generated Vue sites.

Vue.js

Output: dist/ for the standard Vite setup

Nuxt.js

Output: .output/public/

Gridsome

Output: the generated directory that contains index.html

Quasar

Output: dist/spa/

VuePress

Output: docs/.vuepress/dist/

Saber

Output: the generated directory that contains index.html

Static Site Generators

Build content locally and deploy only the generated site.

Hugo

Output: public/

Jekyll

Output: _site/

Eleventy (11ty)

Output: _site/

Astro

Output: dist/

Hexo

Output: public/

Middleman

Output: build/

Bridgetown

Output: output/

Elder.js

Output: the generated directory that contains index.html

Statamic

Output: the generated directory that contains index.html

Sculpin

Output: the generated directory that contains index.html

Metalsmith

Output: the generated directory that contains index.html

Lume

Output: _site/

Hakyll

Output: _site/

Wintersmith

Output: the generated directory that contains index.html

DocPad

Output: the generated directory that contains index.html

Octopress

Output: the generated directory that contains index.html

Nanoc

Output: the generated directory that contains index.html

Jigsaw

Output: the generated directory that contains index.html

Harp

Output: the generated directory that contains index.html

Build Tools & Bundlers

Deploy the browser assets emitted by JavaScript build tools.

Storybook

Output: storybook-static/

Vite

Output: dist/

Parcel

Output: the generated directory that contains index.html

Webpack

Output: the generated directory that contains index.html

Brunch

Output: the generated directory that contains index.html

Silex

Output: the generated directory that contains index.html

CSS Frameworks

Deploy complete HTML sites styled with CSS frameworks and UI kits.

Tailwind CSS

Output: the generated directory that contains index.html

Bootstrap

Output: the generated directory that contains index.html

Bulma

Output: the generated directory that contains index.html

Foundation

Output: the generated directory that contains index.html

Documentation Tools

Deploy generated documentation and knowledge-base output.

VitePress

Output: docs/.vitepress/dist/

Docusaurus

Output: build/

MkDocs

Output: site/

GitBook

Output: the generated directory that contains index.html

Docsify

Output: the generated directory that contains index.html

Bookdown

Output: the generated directory that contains index.html

Slate

Output: the generated directory that contains index.html

Python Ecosystem

Run the generator locally, then deploy its static HTML output.

Pelican

Output: output/

Sphinx

Output: docs/_build/html/

Nikola

Output: the generated directory that contains index.html

Lektor

Output: the generated directory that contains index.html

Cactus

Output: the generated directory that contains index.html

Makesite.py

Output: the generated directory that contains index.html

Server-to-Static

Deploy an exported static copy; server-side source code is never executed.

PHP

Output: the export directory containing index.html

From Local Build to Live Site

Build Locally

Run the framework production build or static-export command on your computer.

ZIP the Output Contents

Open the generated output directory and ZIP its contents so index.html is at the ZIP root.

Upload and Review

Upload the ZIP, review detected output, routing, redirects, headers, and diagnostics, then deploy.

Routing and Response Configuration

Configuration is read from the built ZIP. Framework configuration that expects a server is not executed.

SPA fallback

/* /index.html 200

For a client-routed SPA, keep index.html at the output root. Linkyhost detects common browser-app builds automatically, or you can add /* /index.html 200 to _redirects. Exact assets and directory indexes always win before the fallback.

_redirects

/old /new 301

Put a _redirects file at the output root for deployment redirects. Use one rule per line, such as /old /new 301; supported redirect statuses are 301, 302, 307, and 308. Framework redirects that require a server are not executed.

_headers

/assets/*
  Cache-Control: public, max-age=31536000

Put a _headers file at the output root for path-specific response headers. Start each block with a path, then indent allowlisted Name: value lines. Unsafe or platform-owned headers are ignored and reported in deployment diagnostics.

Ready to Upload a Build?

ZIP the contents of your generated output directory. The uploader will inspect the archive before deployment and explain what it found.

Upload a Build ZIP