You can use ‘paper config’ to specify the working directory, then all the journals will be saved to that path.
10 karma · joined February 29, 2020
You can use ‘paper config’ to specify the working directory, then all the journals will be saved to that path.
The API & web app components will definitely remain private, but the CLI tool itself can be open source.
If you run ‘paper config’ today, you will still see that you can configure the “sync url” - basically that allows you to sync your content to your own hosting provider.
I spent non-trivial thought on this topic during development, but then ended up with a conclusion that I should just make it private for now to speed up feature development. Otherwise I would need to think really hard on the interface & contract design.
Give it a try and let me know your feedback if there’s any!
Hope you will enjoy it!
I published the CLI tool with the sourcemap enabled prev-v1.0.0
That's why you can see the source code.
We are all ears!
Yes, `paper import` handles this. just point it at the folder your daily notes live in:
``` paper import <your-path-to-journals> --dry-run ```
Comment: 1. I personally keep all my Obsidian journals in a journal folder, so that's easy for me to do 2. highly recommend you to use the `--dry-run` option if you are not sure what files will be imported
Two things worth knowing. 1. It reads every `.md` and `.txt` inside that folder 2. file with no date in its name is still imported, and last modified date will become its filename in "paper".
You can read more about its logic in the "Importing existing notes" section on the npm page: https://www.npmjs.com/package/@rewrlution/paper-cli
Hope it works and hope you will enjoy it!
Here's the link to the npm package: https://www.npmjs.com/package/@rewrlution/paper-cli
Worse, about two weeks ago it recommended a command and assured me it was safe. I pushed back and asked it to double-check, and it confirmed again that it was safe. I trusted that and ran it — and it wiped out weeks of my data.
I don't have hard proof, but I can't shake the feeling that Anthropic is doing what Apple does: rolling out a new model while letting the old one degrade, whether on purpose or just as a side effect (like how iOS updates quietly eat more resources and slow down older phones). Lately I feel like I'm constantly fighting with Opus (not Fable, because my Fable quota burns through way too fast).
If you can record some gif and embed it in the README.md, it'd be better