Start here: publish the app on GitHub Pages, configure your own Google app connection, then create your encrypted journal. All source code is included.
Set up your HijiBiji
You need a GitHub account, a Google account with available Drive storage, and a modern browser. No server, paid database, build tool, client secret, or credit card is part of this app's setup. Provider plans and policies can change. This package prepares the app; it does not create or authorize either account for you.
1. Keep your original journal safe
If you have already written in Stillroom:
- Open the original Stillroom file in the original browser/profile.
- Unlock it and open Privacy & backup.
- Download an encrypted backup and remember the password used for it.
- Keep the original app and backup until you have confirmed the import in HijiBiji.
The HTML source file does not contain the original journal data.
2. Put the source on GitHub
- Extract
HijiBiji.zipon your computer. - On GitHub, create a repository named HijiBiji. For GitHub Free Pages hosting, use a public repository. The code will be public; do not upload journal or backup JSON files.
- Open the repository and choose Add file → Upload files (for a new empty repository, use its upload-existing-files link).
- Upload the contents of the extracted HijiBiji folder to the repository root.
index.html,app.mjs, andstyles.cssmust be in the root, not inside an extra HijiBiji subfolder. Keep thetestsdirectory with its contents if uploading the complete source. - Commit the uploaded files.
- Open Settings → Pages → Build and deployment. Select Deploy from a branch, choose main and /(root), then save.
- Wait for GitHub to finish deployment. Open the actual Pages URL shown in Settings. Its usual form is
https://YOUR_USERNAME.github.io/HijiBiji/; use the exact URL GitHub returns. - Click Explore a fictional sample to inspect the app without writing personal data or setting up Google yet.
Files whose names begin with a dot may not appear in your file chooser. Include .nojekyll and .gitignore if your upload method supports them; the app's underscore-free assets also work with the normal branch publishing pipeline. Never add a real JSON backup to a public repository, even if encrypted. Do not paste private material into GitHub issues or screenshots.
3. Create your own Google app connection
This part is one-time account configuration. You do it in your own Google account.
- Open Google Cloud Console. Create a project named HijiBiji. Use this same project long term.
- Find APIs & Services → Library, search for Google Drive API, and enable it for this project. You do not need to provision a paid server or add a billing account for this app.
- Open Google Auth Platform (or OAuth consent screen, depending on the console layout). Configure branding with the app name HijiBiji, your user support email, and your developer contact email.
- Choose the External audience for a personal Google account. Start in Testing, and add your own Google email as a test user. This keeps authorization limited to your test-user list. Google may display an app-testing consent notice.
- In Data Access, add exactly this scope:
https://www.googleapis.com/auth/drive.appdata. HijiBiji needs its own app-data area, not your full Drive. - In Clients, create an OAuth client of type Web application. Name it HijiBiji Web.
- Add the origin of your Pages website under Authorized JavaScript origins. Example:
https://YOUR_USERNAME.github.io. An origin contains the scheme and hostname only; do not add/HijiBiji/, a file path, query, or trailing slash. For a custom domain, add that exact HTTPS origin instead. For development only, optionally addhttp://localhost:8000. - The app uses Google's browser popup token flow. It does not require a backend client secret or an authorized redirect URI for this flow.
- Copy the Client ID, which ends in
.apps.googleusercontent.com. Do not copy the client secret.
If Google asks for optional branding URLs before you have them, keep optional fields blank for the initial personal testing setup. Follow Google's current console instructions for any fields it requires; do not enter someone else's domain or invented details. Organizations may restrict OAuth apps even when configured correctly.
Official instructions: Google browser authorization, OAuth web setup, Drive app-data scope.
4. Connect and create your encrypted journal
- Open your actual HijiBiji GitHub Pages URL.
- Paste the public Client ID into the Google OAuth client ID field. You can alternatively edit
config.jsin GitHub and setgoogleClientIdto it; the ID is public configuration, not a secret. - Click Connect my Google Drive. If the app first loads Google's sign-in library, it will ask you to click Continue to Google once more so the browser permits the popup.
- Choose the same Google account you added as a test user and authorize the requested app-data permission. Google manages its own sign-in; never put your Google password in HijiBiji's journal password field.
- If this is a new journal, create a separate HijiBiji password of at least 12 characters and confirm it. Use a unique strong password that you can keep safely. There is no reset or recovery.
- Write a small test reflection. Wait until the status says Saved to Google Drive.
- Lock HijiBiji, reopen it, connect the same Google account, and unlock with the same journal password. Confirm the reflection is present before relying on it for your private writing.
- Open the site on another browser/device to confirm cloud access if desired. Finish saving and lock the first device before editing on the second.
Google stores this app's data in its hidden app-data area, not as an ordinary visible My Drive folder. HijiBiji retrieves it using the Drive API. Do not remove HijiBiji's saved app data from Google Drive settings unless you intend to erase it. Avoid changing to another Google Cloud project, which represents a different application storage area.
5. Bring over your Stillroom entries
- Unlock your new HijiBiji journal.
- Open Privacy & backup → Import missing pages.
- Select the encrypted backup JSON downloaded from Stillroom.
- Enter the password used by that backup in the masked backup-password dialog. It can differ from your new HijiBiji password.
- The app decrypts it in browser memory, encrypts its missing entries using your HijiBiji password, and saves the imported records to Drive.
- Keep the page open until saving completes. Check Past pages and Goals & plans.
- Download a complete HijiBiji encrypted backup. Keep the original Stillroom backup until you are satisfied.
Import is deliberately a merge: existing dates and goal IDs stay unchanged. To reconcile different text for the same date, view both versions and manually copy the text you want into the current reflection. Never upload backups to the public repository.
6. Use it for the coming years
- Bookmark your GitHub Pages URL. Use the same Google account and journal password on each device.
- Complete one editing session before starting another. This app is not a simultaneous multi-device editor.
- Wait for the Drive-save confirmation. If saving fails, keep the page open and use Reconnect & save. If you cannot reconnect, download an emergency encrypted copy of your loaded pages and unsaved edits.
- Download a complete encrypted backup periodically and keep a separate copy somewhere you control. An emergency copy is partial and does not replace the full journal backup.
- Google access tokens are short-lived. Reconnection is normal; it does not erase your data. Testing-mode authorizations also expire after seven days, so consent may be requested again. You can continue personal testing use with this maintenance. If you later change the app's publishing status, review Google's personal-use OAuth requirements first; do not assume “In Production” still restricts access to the test-user allowlist.
- Keep your Google account and the app's Cloud project active. Check provider policy or permission notices. No software can guarantee that free third-party service terms remain unchanged for three years.
- For best performance, use the date filters and normal paginated browsing. Searching the entire journal or exporting everything intentionally downloads more data and takes longer.
- If modifying the app, back up first, test with fictional data, then commit the updated source. The test command is
node --test tests/hijibiji.test.mjswith Node 22+.
If something goes wrong
| Message/problem | What to check |
|---|---|
| Client ID invalid | Use a Web application OAuth Client ID ending in .apps.googleusercontent.com, not a secret or project ID. |
| Origin mismatch | Add the exact HTTPS hostname origin, without the repository path, in Authorized JavaScript origins. Allow configuration changes time to propagate. |
| Google access denied | Check your test-user email, app audience, enabled Drive API, permission scope, and organization restrictions. |
| Google popup blocked | Allow the sign-in popup for your site and click Continue to Google directly. |
| No vault found on another device | Connect the same Google account and keep the same Cloud project/client configuration. |
| Incorrect journal password | The journal password is separate from Google's. There is no recovery or administrative decryption. |
| Google connection expired | Keep the page open; click Reconnect & save. |
| Another session changed a record | Export an emergency copy, reload, inspect the latest cloud text and manually reconcile conflicting dates. Do not force an overwrite. |
| Save interrupted | It may or may not have reached Drive. Preserve an emergency copy before reload. A version conflict after reconnect is a protective stop. |
| App is visible to other people | The website shell and source are public on free Pages. Your encrypted journal still needs the correct Google account authorization and journal password. |
| A page reload lost unsaved writing | Restore missing dates from an emergency backup if you downloaded one. Without saved cloud data or a backup, unsaved memory cannot be recovered. |
Primary references
- GitHub Pages publishing
- Google OAuth token model and expiry
- Google Drive application data
- Google OAuth personal-use verification exceptions
- Testing audience and seven-day authorization
Prepared November 15, 2026. Console wording and service policies may change.