Napp Up!

  _   _                   _   _       _
 | \ | | __ _ _ __  _ __ | | | |_ __ | |
 |  \| |/ _` | '_ \| '_ \| | | | '_ \| |
 | |\  | (_| | |_) | |_) | |_| | |_) |_|
 |_| \_|\__,_| .__/| .__/ \___/| .__/(_)
             |_|   |_|         |_|

Napp Up! is a powerful CLI tool for developers to effortlessly upload and manage Nostr applications. Ship your decentralized apps to the Nostr network with a single command.

Usage

nappup [directory] [options]

Arguments

• [directory] The root directory of your application to upload. If omitted, defaults to the current working directory (.).

Options

Flag	Description
-s <secret_key>	Your Nostr secret key (hex, nsec, or bunker:// URL) used to sign the application event. See Authentication for alternatives.
-d <d_tag>	The identifier (d tag) for your application. Any UTF-8 text up to 260 characters. If omitted, defaults to the directory name. Avoid generic names like dist or build - use something unique among your other apps like mycoolapp.
-y	Skip confirmation prompt. Useful for CI/CD pipelines or automated scripts.
-r	Force re-upload. By default, Napp Up! might skip files that haven't changed. Use this flag to ensure everything is pushed fresh.
--main	Publish to the main release channel. This is the default behavior.
--next	Publish to the next release channel. Ideal for beta testing or staging builds.
--draft	Publish to the draft release channel. Use this for internal testing or work-in-progress builds.

Authentication

Napp Up! supports multiple ways to provide your Nostr secret key:

1. CLI flag: Pass your secret key (hex or nsec) directly via -s:

   nappup -s nsec1...

2. Remote signer (NIP-46): Pass a bunker:// URL to sign events via a remote signer like nak or Amber:

   nappup -s 'bunker://<pubkey>?relay=wss://relay.example.com&secret=<token>'

3. Environment variable: Set NOSTR_SECRET_KEY in your environment or a .env file (also supports bunker:// URLs):

   export NOSTR_SECRET_KEY=nsec1...
   nappup ./dist

4. Auto-generated key: If no key is provided, Napp Up! will generate a new keypair automatically and store it (as nsec) in your project's .env file for future use.

Examples

Upload the current directory to the main channel:

nappup -s nsec1...

Or using an environment variable:

NOSTR_SECRET_KEY=nsec1... nappup

Upload a specific dist folder with a custom identifier to the next channel:

nappup ./dist -s nsec1... -d "My App #1" --next

Force re-upload a draft:

nappup ~/my-repos/projectx/build/projectx --draft -r

Programmatic Usage

Napp Up! also exports a function that works in both Node.js and the browser, so you can integrate app uploads directly into your own tooling:

import publishApp from 'nappup'

await publishApp(fileList, signer, {
  dTag: 'my-app',
  channel: 'main',       // 'main' | 'next' | 'draft'
  shouldReupload: false,
  onEvent ({ type, progress }) {
    console.log(`${type} — ${progress}%`)
  }
})

• fileList — a FileList or array of File objects (each needs webkitRelativePath).
• signer — a NIP-07-compatible signer. In the browser, window.nostr is used automatically if omitted.
• onEvent — optional callback that receives progress events with a type ('init', 'file-uploaded', 'complete', 'error', …) and progress (0–100).