This repo is setup to be a small starter for deploying a static site as a Nsite using the Nsite-CLI. In general this repo is setup to auto deploy using Github action but also can be used with the CLI to deploy from the terminal.
This is build on top of the work of some great folks: Lez flox1an hzrd149
**~ 15 min guide**
The Nsite setup consists of two components/repositories:
- The Nsite – Contains the GitHub action deploy script.
- The Nsite Gateway – Resolves the site through its
npuband connects the domain.
- GitHub Account
Nsecin Hex format- Domain name (optional)
- Cloudflare or Vercel Account (GitHub Pages may also work)
Go to the Nsite-Upload GitHub Repo and select Use this template to clone it.
- Navigate to Settings in your repo.
- Under Secrets and variables, select Actions.
- Click Add a New Repository Secret.
- Name it:
NSITE_KEYSet the secret as yourNsecin hex format.
Once the secret is set:
- Go to the Actions tab in the repo.
- Because the deployment failed, click Re-run jobs to redeploy with the newly set
Nsec.
After deployment, the npx command will show the deployment details, including the live URL on Nsite.lol Gateway.
- Any changes made to
index.htmlwill be deployed automatically when pushed.
You might not have set any Blossom servers for your BUD-03 List.
- Visit Nsite Debug, enter your
npub, and check for missing configurations. - Set your Blossom Server List via Bouquet.
Alternatively, try deploying locally:
-
Download the repo to your local machine.
-
Install Node.js.
-
Set your
Nsecin.nsite/project.json. (Modify other settings if needed) -
Run in the terminal from the root directory:
npx nsite-cli upload www
- Nsite.lol has caching, so updates may not appear immediately.
- Try Nsite.cloud, which does not have caching and should reflect updates immediately. (Note: Nsite.cloud only supports simple single-page HTML sites.)
- The Blossom server might not serve the blob via public access.







