Skip to content

Installation & Downloads

Notara 1.1.0 currently ships with the following downloadable installers and bundles:

Linux .deb

Debian and Ubuntu-friendly desktop package.

Linux .rpm

RPM package for Fedora, RHEL-family, and compatible distros.

Linux AppImage

Portable desktop build with no package manager required.

Windows installer

NSIS installer for Windows desktops.

OptionBest forNotes
Tauri .debDebian or Ubuntu usersNative desktop experience with automatic app-data workspace storage.
Tauri .rpmFedora or RPM-based systemsSame desktop feature set, packaged for RPM ecosystems.
Tauri AppImagePortable Linux installsUseful when you do not want system package integration.
Windows NSIS installerWindows desktopsNative installer path for the Tauri build.
Source installContributors or custom buildsRun the Vite app locally and optionally launch the Tauri shell.
DockerSelf-hosted browser runtimeServes the built SPA plus Pollinations proxy routes.
Terminal window
sudo dpkg -i Notara_1.1.0_amd64.deb
sudo apt-get install -f
Terminal window
sudo rpm -i Notara-1.1.0-1.x86_64.rpm
Terminal window
chmod +x Notara_1.1.0_amd64.AppImage
./Notara_1.1.0_amd64.AppImage

Run Notara_1.1.0_x64-setup.exe and follow the installer prompts.

  • Node.js 18+
  • npm or yarn
  • Git
  • Rust toolchain
  • On Debian or Ubuntu for desktop builds:
Terminal window
sudo apt-get update
sudo apt-get install -y libwebkit2gtk-4.1-dev libgtk-3-dev libayatana-appindicator3-dev librsvg2-dev patchelf
  1. Clone the repository.

    Terminal window
    git clone https://github.com/pinkpixel-dev/notara.git
    cd notara
  2. Install dependencies.

    Terminal window
    npm install
  3. Copy the example environment file.

    Terminal window
    cp .env.example .env
  4. Keep auth disabled unless you explicitly want the legacy Supabase flows.

    Terminal window
    VITE_ENABLE_AUTH=false
    VITE_POLLINATIONS_API_TOKEN=optional_pollinations_token
  5. Start the dev server.

    Terminal window
    npm run dev
  6. Open http://localhost:3489.

Run the Tauri shell against the local frontend:

Terminal window
npm run tauri:dev
Terminal window
npm run build
Terminal window
npm run tauri:build:linux

Artifacts are written to:

  • src-tauri/target/release/bundle/deb/
  • src-tauri/target/release/bundle/appimage/

Build the self-hosted web runtime:

Terminal window
docker build -t notara:latest .

Run it:

Terminal window
docker run --rm -p 3489:3489 \
-e POLLINATIONS_API_TOKEN=your_optional_pollinations_token \
notara:latest

Then open http://localhost:3489.

The Docker image serves both the production SPA and the /api/pollinations/* endpoints used by the web app, so AI chat and image generation still work through the container runtime.

If you deploy the web version to Cloudflare Pages, the repo already includes Pages Functions for the Pollinations routes. Mirror the optional token with:

Terminal window
wrangler secret put POLLINATIONS_API_TOKEN

The docs site under website/ has its own Pages config in website/wrangler.jsonc, separate from the root app config.

Terminal window
cd website
npx wrangler whoami
npm run deploy

For local Pages-style testing:

Terminal window
npm run cf:dev
VariableRequiredPurpose
VITE_ENABLE_AUTHNoEnables the legacy Supabase auth flow only when set to true.
VITE_POLLINATIONS_API_TOKENNoAdds an authorization header for authenticated Pollinations requests in browser builds.
VITE_SUPABASE_URLOnly if auth is enabledSupabase project URL.
VITE_SUPABASE_ANON_KEYOnly if auth is enabledSupabase anon key.
POLLINATIONS_API_TOKENOptional for Docker and CloudflareServer-side token used by proxy routes.

On some rolling-release Linux distros, AppImage packaging can fail because linuxdeploy can lag behind newer linker formats. The repository works around part of that by building with NO_STRIP=YES, and GitHub Actions on ubuntu-22.04 remain the most reliable path for AppImage output.