Own-code hosting reference

The rules Sitesfare applies to a site you bring yourself — every limit, every file type, what happens to each file, how caching works, and every message you can see, with what to do about it. For the step-by-step, start with Bring your own code.

Limits

Your plan adds its own allowances on top — storage, monthly bandwidth and deploys a day:

Deploys reset at midnight UTC. Bandwidth is measured daily; you are emailed at 80% and 100% of the month's allowance and the site stays up.

File types that are served

.htm pages are published as .html. Each file is served with the correct content type and X-Content-Type-Options: nosniff.

What happens to each file

Refused — the upload is stopped and nothing changes. These mean the upload is a project that needs a build or a server, not a website. The message lists the files.

• package and build files: package.json, lock files (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb), composer.json, requirements.txt, Pipfile, Gemfile, go.mod, Cargo.toml, Procfile, vercel.json, netlify.toml, wrangler.toml
• framework configuration: next.config.*, vite.config.*, astro.config.*, nuxt.config.*, svelte.config.*, webpack.config.*, rollup.config.*, gatsby.config.*, remix.config.*, angular.json, tsconfig.json
• source and server code: .ts .tsx .jsx .vue .svelte .astro .php .py .rb .go .java .cs
• scripts and executables: .sh .bat .cmd .ps1 .exe .dll .so .jar .war
• archives inside the upload: .zip .tar .gz .tgz .7z .rar
• secrets: any .env file
• folders: node_modules, server, api, functions, vendor, .next, .nuxt
• Dockerfile, docker-compose.yml

Skipped — left out and listed on the Code page; the rest is published.

• README, LICENSE, CHANGELOG, CONTRIBUTING and similar, and .md .yml .yaml .toml .lock .log files
• design files: .psd .sketch .fig .ai
• hidden files and folders (.htaccess, .git/, .DS_Store) and macOS __MACOSX folders
• .well-known/acme-challenge and .well-known/pki-validation (certificate files are Sitesfare's to serve)
• any other file type not in the list above — the Code page shows these in a yellow warning, because a site can depend on them. Tell us if you need one.

Published — everything else, after Sitesfare's last pass over your HTML pages: the canonical address, the analytics tracker, Search Console verification, and the Made with Sitesfare credit (unless removed). A robots.txt and sitemap.xml are added only if you did not ship your own.

Addresses

• / serves index.html; /about serves about/index.html (clean addresses); /about/ works too.
• 404.html at the top becomes your not-found page. Without one, visitors see a plain "Page not found".
• Sites are served over HTTPS only; http:// redirects.
• Service workers are not allowed on Sitesfare sites (a worker outlives its site and would keep answering for whoever gets the address next).
• Source maps (*.map) are served if you upload them, which shows your original source to anyone who looks. Delete them from the build (Vite: build.sourcemap: false) if you would rather not — it also makes the upload smaller.

Caching and updates

• A new version is served everywhere within about 15 seconds of the upload finishing.
• Files whose name carries a content hash (index-Coi9Kw88.js, main.3f2a1b9c.js) are cached by browsers for a year — a changed file always gets a new name, so this is safe and fast.
• Everything else (index.html, style.css, logo.png) is cached by browsers for up to 5 minutes. If you name files by hand, visitors who loaded the old version a moment ago may need to refresh.
• Each upload replaces the whole site at once: new files are written first, then old files the new version no longer has are removed.

Before payment, and after

The plan's website places are filled in this order: sites that have been live first, then sites waiting for payment, then drafts — oldest first within each. Each plan covers one website — another website needs another plan at its listed price (the waiting site's Code page offers it). If two of your sites are waiting for the same plan, the one created first goes live first; delete the one you do not want, or buy a plan for each.

Every message, and what to do

Something not covered here? Contact us.