Cyber Week30% off Lifetime with code CYBER — it will never be this cheap againUntil 28 Nov, 10:00 CET

Ship & extend

Publishing & hosts

Publishing straight to Vercel, Netlify, Cloudflare or your web hosting, pushing to GitHub, previews, rolling back, and what your privacy policy has to name.

sitereal can put a site online two ways, and you can use both. It can publish straight to a host: the site is built on your computer and uploaded to Vercel, Netlify, Cloudflare or your own web hosting, with no repository and no build settings on the host’s side. Or it can push to GitHub, and a host that watches the repository builds the site there. Either way the site is plain Astro, so you can change hosts later without changing the site.

What Publish does

The Publish button in the top bar does what you chose under Publish settings, and nothing until you choose. A new project says Nothing is set up to publish yet with Choose now. There are two switches, and both can be on:

  • Push to GitHub commits what changed and pushes it, in one click. It keeps the version history, and it is what a host that builds from GitHub watches. It can be turned on once you are signed in to GitHub and the project has a repository there (Settings → Repository).
  • Publish to your host builds the site here and uploads it. It can be turned on once the host is connected and its account is on this computer.

A switch that cannot be turned on yet says what it is missing, like connect Netlify first or needs a GitHub repository. The same settings are at the top of Settings → Publish, which also holds the checks, recent publishes and the rest.

Choosing where the site goes

Publish settings → Hosting → Provider lists GitHub first, for a host that builds from your repository, and then the hosts sitereal publishes to directly:

HostHow you connectWhere the company is
VercelA token you make on Vercel’s Account → Tokens page and paste onceUSA
NetlifySign in with Netlify: the browser opens, you allow sitereal, done. A token is the fallback.USA
CloudflareSign in with Cloudflare, through Wrangler, Cloudflare’s own tool. A token made on Cloudflare’s page is the fallback.USA
Web hostingYour hosting’s server and login, over FTPS or SFTPwherever your hosting company is, often the EU

After the account comes the project on the host: an existing one, or a new one sitereal makes with the site’s name. On web hosting it is the folder the site goes into; sitereal opens public_html or a folder like it when the login has one.

Tokens and passwords stay on this computer. They go into the system keychain (the macOS Keychain, Windows’ own protected store, or the Linux secret service), never into the project, so a teammate who opens the project signs in with their own account. When VERCEL_TOKEN, NETLIFY_AUTH_TOKEN or CLOUDFLARE_API_TOKEN is set where sitereal runs, that one is used instead, for CI and password managers.

Vercel

Make the token on Vercel under Account → Tokens, scoped to the one team the site belongs to and with an expiry date: it can reach only what you scope it to. Vercel’s free Hobby plan is for personal, non-commercial projects, and its terms count any site someone is paid to make as commercial. A client’s site belongs on a Pro team. sitereal says so where the account is connected, and does not stop you.

A preview on Vercel opens only for people on your Vercel team. To show one to a client, use Share beside it: sitereal makes a link anyone can open, and Stop sharing ends every link given out.

Netlify

Sign in with Netlify opens Netlify in your browser; allow sitereal there and the sheet carries on. On Netlify’s free plan, every production publish costs 15 of the team’s 300 monthly credits, and running out pauses every site of the team until the month ends. The Publish button shows that cost before you press it. Previews cost nothing, so use Preview link while you are still changing things.

If visitors get Netlify’s login page instead of your site, the team has Netlify login for all sites switched on (under the team’s visitor access settings). The checks say so.

Cloudflare

Sign in with Cloudflare goes through Wrangler, Cloudflare’s own command-line tool, so Cloudflare’s page asks you to allow Wrangler. It asks to read your account and user and to change Workers scripts and Workers KV, nothing else, and it renews itself. The first sign-in fetches Wrangler, which takes a minute. The login is kept in sitereal’s own folder, apart from any Wrangler login of your own, and forgetting the account signs it out with Cloudflare.

With Use a token instead, Cloudflare’s token page opens with the permissions already chosen: Workers Scripts to edit, Account Settings to read, and Workers KV to edit. Pick your account under Account Resources, create it, and paste it.

The site is published as a Worker with its pages as static assets, on <name>.<your-subdomain>.workers.dev until you add your own domain on Cloudflare.

Web hosting

Any hosting with an FTP or SSH login works, including plans bought for WordPress with no Node anywhere near them. Enter the server and login, press Test connection, and pick the folder from what is there.

  • FTPS is what most hosting offers: FTP with encryption, signed in with a password. When the hosting’s certificate names another host (common on shared hosting), sitereal shows the certificate and you can trust it by its fingerprint.
  • SFTP runs over SSH. It signs in with this computer’s SSH key, whose public key you add in the hosting’s SSH settings (the sheet shows it when the server refuses it), or on macOS and Linux with the login’s SSH password. The server’s key is trusted the first time, and a key that changes later is refused and said.
  • FTP without encryption sends the password as it is. Use it only when the server offers nothing else.

Each publish uploads only what changed since the last one, sends .htaccess last, and deletes only files an earlier publish put there. Files you put there yourself stay.

Publishing

Press Publish. sitereal checks the site against the host, builds it here, uploads it and says when it is live, with its address. What you have not committed goes too, and the button says so every time; the publish remembers the commit it came from, so recent publishes can show it.

A file the host will not take, like a video over Cloudflare’s 25 MiB limit, or more files than a plan allows, stops the publish before anything is uploaded and names the file. A refusal from the host comes back in plain words with what to do, like Reconnect when a token has expired.

Use as site address, under Advanced in Publish settings, makes the address it went live on the site’s address for share cards and the sitemap. A domain of your own is added on the host’s side.

Previews

Preview link puts a copy online at an address of its own, without touching the live site, so you or a client can look before it goes live. Publish replaces the live site when you are ready.

HostA preview isWho can open it
Vercela deployment that is not productionyour Vercel team; anyone with a shared link
Netlifya draft deploy, free of creditsanyone with the link
Cloudflarea version of the Worker that is not deployedanyone with the link
Web hostingnot offered: the folder holds one site—

On Cloudflare a preview works before the first publish too: sitereal turns on the Worker’s preview addresses and leaves its main address off until you publish.

Recent publishes and rolling back

Settings → Publish → Recent publishes is the host’s own list, so a deploy made on the host’s dashboard shows too: which one is live, which were previews, when, and the commit each came from. Roll back puts an earlier publish back live with the host’s own call, nothing rebuilt, in seconds. The next Publish brings the site forward again. Web hosting keeps no history: the folder holds one site.

Sites with a server

A form endpoint, a page rendered on request or an API route needs the host’s Astro adapter. The checks say when it is missing, and Add beside it runs Astro’s own astro add for that host, which writes astro.config.mjs. Then each host takes the server its way: Vercel as a function, Cloudflare as the Worker’s own code, Netlify through its own command-line tool.

The variables the live site reads (a mail key, a database address) are listed under the checks with Set them on the host, which sends them from your .env by name, on that click only. A site that reads Astro’s sessions gets a KV store on Cloudflare, made for it on the first publish.

Web hosting runs no Node, so a site with a server cannot go there. A sitereal form on web hosting is sent through a small PHP endpoint the export writes instead.

Building from GitHub instead

Choose GitHub as the provider when a host should build the site from your repository: Cloudflare Pages, a server of your own, or Netlify or Vercel set up on their side. Publish then pushes, and Settings → Publish shows the steps to connect the repository on the host and what to enter there, and afterwards whether the build went live. Which host builds it changes nothing in sitereal.

Uploading and building from GitHub on the same host project work against each other: the next push replaces an upload, and an upload replaces what a push built. The checks warn when both point at one project.

Replacing a WordPress site on the same hosting

A hosting plan bought for WordPress can keep its client: publish to it over FTPS or SFTP. The upload carries a .htaccess with the 404 page, compression, cache headers for the hashed files and your redirects (Settings → Redirects), each wrapped so a server missing a module skips it instead of failing. Before the first publish:

  1. Back up the whole hosting, files and database.
  2. Remove the WordPress from the web folder: wp-admin/, wp-includes/, wp-content/, wp-*.php, xmlrpc.php and the old .htaccess. An old WordPress left on the internet is how sites get taken over after they are replaced.
  3. Publish into that folder.
  4. Uncomment the HTTPS block at the end of .htaccess once the certificate is installed and https:// loads. It ships commented out because forcing HTTPS before the certificate exists takes the site down.

To check that .htaccess is read, open an address the site does not have. You should see your own 404 page; the hosting company’s default page means the file is not being read, and the host has to allow it (AllowOverride).

With no login sitereal can use, Settings → Publish → Export static site still hands you a zip of the finished site with the same .htaccess, to upload with an FTP program. Switch on hidden files there first: .htaccess starts with a dot, and most programs hide it.

What your privacy policy has to name

A host keeps logs with your visitors’ IP addresses, so it processes personal data for whoever runs the site, and the privacy policy has to name it. sitereal writes no legal text, but it checks your own privacy page for the host’s name and says when it is missing.

  • Vercel, Netlify and Cloudflare are US companies. Name the company and its address, and the transfer to the USA. All three are on the EU–US Data Privacy Framework list (look up their entries at dataprivacyframework.gov), and each has a data processing agreement that applies without signing anything.
  • Whose account it is matters. A client’s site in the client’s own host account means the client contracts with the host directly. In your agency’s account, you become the client’s processor and need an agreement with them that names the host.
  • When a client asks for EU-only hosting, publish to web hosting with a company in the EU.

What a host adds that the consent scan cannot see:

  • Vercel shows its toolbar on preview deployments; switch it off in the project’s settings on Vercel if previews go to clients.
  • Cloudflare, on a domain it proxies, sets its bot cookie (__cf_bm) and can inject scripts such as Rocket Loader or Email Obfuscation when they are switched on for the zone. Switch those off, or name them.
  • Netlify adds nothing to the pages by default. Its analytics and forms, if you switch them on there, belong in the policy too.

This is what the hosts’ terms and the GDPR ask of a site, not legal advice. When in doubt, have the privacy policy checked by someone who answers for it.