https://github.com/ckampfe/journal
Focus on the writing, not the reading.
https://github.com/ckampfe/journal
htmx journal obsidian roam roamresearch rust sqlite writing
Last synced: about 2 months ago
JSON representation
Focus on the writing, not the reading.
- Host: GitHub
- URL: https://github.com/ckampfe/journal
- Owner: ckampfe
- License: bsd-3-clause
- Created: 2025-06-28T22:19:14.000Z (12 months ago)
- Default Branch: main
- Last Pushed: 2025-09-26T04:42:00.000Z (9 months ago)
- Last Synced: 2025-10-28T16:38:04.347Z (8 months ago)
- Topics: htmx, journal, obsidian, roam, roamresearch, rust, sqlite, writing
- Language: Rust
- Homepage:
- Size: 30.3 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# journal
A thing to focus on the writing, not the reading. The anti-Obsidian, the anti-Roam.
## It looks like this
## Running
```sh
Usage: journal [OPTIONS]
Options:
--database-path [env: JOURNAL_DB_PATH=]
--port [env: PORT=] [default: 9999]
-h, --help Print help
```
## Building
`$ cargo build [--release]`
## Pro tips
Set up a keyboard shortcut to open `http://localhost:9999` or wherever you have this running.
Set up Caddy to give it a name, like:
```
# in Caddyfile
journal.localhost {
reverse_proxy :9999
}
```
## Motivation
My hypothesis is that Obsidian, Roam, and all of the "knowledge base" software popular these days see the reading vs. writing value breakdown as being something like 90:10%. I think it's the inverse. The main behaviors Obsidian/Roam/etc. encourage are making backlinks, tinkering with their settings, and trying to come up with a cogent directory structure. Accordingly, they're great for things like lists, or documents you need to frequently reference. They're bad for thinking or journaling, because the temptation to fritter around making backlinks and tweaking things that don't matter is too great due to what their designs incentivize.
## Implementation
Rust, Sqlite, Htmx