A fast, fully client-side Progressive Web App (PWA) for modern notaries. It features offline support, highly secure local encryption, ID scanning, signature capture, and print-ready NNA-compliant journal PDFs.

Because this app is purely frontend (with no backend server), it can be hosted anywhere for free.

If you've cloned this repository and want to host your own instance of the Notary Journal PWA for $0/month, the easiest beginner path is Zo Computer. Netlify, Cloudflare Pages, and Hostinger are also supported if you prefer a traditional static host.

Zo Computer gives you a personal cloud computer with hosting and cloud storage. The free plan includes 100GB storage and one hosted service.

After deployment, Zo MUST output:

1. Public App URL: https://notary-log-{your-handle}.zocomputer.io
2. Backup API URL: https://notary-log-{your-handle}.zocomputer.io/api/backup
3. Backup Key: Generated secret token
4. Backup Storage: Documents/Notary Journal/backups/

Without these outputs, Backup & Restore won't work.

Copy/paste this exact prompt into Zo or any deployment AI:

Deploy https://github.com/SillyHippy/Notary-log on Zo Computer as ONE public HTTP service named notary-log.

Hard rules:
- Use one name everywhere: notary-log.
- Create exactly ONE service named notary-log.
- Do not create a second service.
- Do not create a service named notary-journal.
- Do not create a Zo Space API route.
- Do not clone into Trash.
- Do not duplicate the repo folder.
- Do not replace the app's storage with /home/workspace/notary-data.json.
- The app and backup API must run together from the same service.

Commands to run from /home/workspace:
if [ -d notary-log ]; then
  cd notary-log
  git pull
else
  git clone https://github.com/SillyHippy/Notary-log notary-log
  cd notary-log
fi
bun install
bun run build

If a service named notary-log already exists, update/restart that exact service.
If no service named notary-log exists, create it:
zo service create --mode http --port 3000 --public true --entrypoint "bun run prod" --label notary-log

After deployment, stop and output only:
1. Public App URL
2. Backup API URL, which must be the Public App URL plus /api/backup
3. Backup Key printed by bun run prod
4. Backup Storage: Documents/Notary Journal/backups/

Before reporting success, test the one service:
curl -I [Public App URL]
curl -H "Authorization: Bearer [Backup Key]" [Public App URL]/api/backup

To enable the "Auto-Backup to Google Drive" feature in your self-hosted version, you need to create a free Google Cloud project to get a Client ID.

1. Go to the Google Cloud Console.
2. Create a new project (e.g., notary-journal-app).
3. Enable the Drive API: Go to APIs & Services > Library, search for Google Drive API, and click Enable.
4. Go to APIs & Services > Credentials.
5. Click Create Credentials -> OAuth client ID.
6. Choose Web application as the application type.
7. Under Authorized JavaScript origins, add the URL where you will host the app (e.g., https://your-app.netlify.app or https://your-app.pages.dev). Note: You may need to come back and add this after you deploy.
8. Copy your Client ID (it looks like 123456789-abcxyz.apps.googleusercontent.com).

You will need to paste this as an Environment Variable (VITE_GOOGLE_CLIENT_ID) when setting up your hosting in the next steps.

Netlify is incredibly easy to use and automatically builds your app every time you push changes to GitHub.

1. Create an account: Go to Netlify.com and sign up using your GitHub account.
2. Add new site: In your dashboard, click "Add new site" -> "Import an existing project".
3. Connect GitHub: Authorize GitHub and select your repository.
4. Configure Build Settings (Crucial Step): Because the app is located in a subfolder, fill out the build settings exactly like this:
   • Base directory: artifacts/notary-journal
   • Build command: pnpm run build (or npm run build)
   • Publish directory: artifacts/notary-journal/dist/public
5. Add Environment Variables:
   • Click Add environment variables.
   • Key: NODE_VERSION | Value: 22
   • Key: VITE_GOOGLE_CLIENT_ID | Value: [paste the Client ID from the optional Google setup section]
6. Deploy: Click "Deploy site". Netlify will take a minute or two to build the app.
7. Custom Domains & SSL: Netlify will give you a free .netlify.app URL. If you want to use your own domain, go to Domain Management, add your custom domain, and follow their DNS instructions. Netlify provides free automatic SSL certificates.

Cloudflare Pages is also completely free and leverages Cloudflare's massive global CDN network, making your app load blazingly fast anywhere in the world.

1. Create an account: Go to Cloudflare.com and sign up.
2. Navigate to Pages: On the left sidebar, click "Workers & Pages", then click the "Pages" tab.
3. Connect GitHub: Click "Connect to Git", authorize your GitHub account, and select your repository.
4. Configure Build Settings: Set it up exactly like this to handle the workspace structure:
   • Framework preset: None
   • Build command: pnpm --filter @workspace/notary-journal... run build
   • Build output directory: artifacts/notary-journal/dist/public
   • Root directory: (leave blank)
5. Add Environment Variables:
   • Scroll down to Variables and secrets and click Add.
   • Name: NODE_VERSION | Value: 22
   • Name: VITE_GOOGLE_CLIENT_ID | Value: [paste the Client ID from the optional Google setup section]
6. Deploy: Click "Save and Deploy".
7. Custom Domains: Cloudflare provides a free .pages.dev URL. If you want a custom domain, go to the Custom Domains tab on your Pages project. Since you are already in Cloudflare, managing the DNS is seamless and SSL is automatically applied.

If you are using Hostinger, cPanel, or another standard shared hosting provider (which typically use Apache or LiteSpeed servers), you can easily host this PWA.

1. Build locally: You will need to build the app on your own computer first.

   export VITE_GOOGLE_CLIENT_ID="[paste the Client ID you got from Step 1]" 
   pnpm --filter @workspace/notary-journal run build

2. Add an .htaccess file: Inside the newly built artifacts/notary-journal/dist/public folder, create a file named .htaccess with these contents to handle SPA routing:

   <IfModule mod_rewrite.c>
     RewriteEngine On
     RewriteBase /
     RewriteRule ^index\.html$ - [L]
     RewriteCond %{REQUEST_FILENAME} !-f
     RewriteCond %{REQUEST_FILENAME} !-d
     RewriteRule . /index.html [L]
   </IfModule>

3. Upload & Extract: Zip up the contents of the dist/public folder (including the new .htaccess file). Log into your Hostinger File Manager (or connect via FTP), upload the zip to your public_html directory, and extract the files directly there.

(For more advanced deployment details and cache troubleshooting, see the DEPLOYMENT.md file included in this repository).

If your app deploys successfully on either platform but shows a completely blank white screen, it means the hosting provider is serving the wrong folder. Ensure your Publish/Output directory was set exactly to dist/public and not just dist.