Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/davep/journey2md
Simple tool to turn a Journey export into Obsidian-friendly Markdown
https://github.com/davep/journey2md
cli export import journal journey obsidian obsidian-md python
Last synced: 10 days ago
JSON representation
Simple tool to turn a Journey export into Obsidian-friendly Markdown
- Host: GitHub
- URL: https://github.com/davep/journey2md
- Owner: davep
- License: gpl-3.0
- Created: 2024-10-12T16:07:49.000Z (3 months ago)
- Default Branch: main
- Last Pushed: 2024-10-17T13:27:11.000Z (3 months ago)
- Last Synced: 2025-01-11T21:55:43.707Z (10 days ago)
- Topics: cli, export, import, journal, journey, obsidian, obsidian-md, python
- Language: Python
- Homepage: https://pypi.org/project/journey2md/
- Size: 44.9 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# journey2md
## Introduction
This is a simple command line tool that can be used to extract journal
entries from [Journey](https://journey.cloud) and turn them into a
collection of Markdown files. In this tool's case the Markdown collection is
built so it can easily be used as an [Obsidian](https://obsidian.md) Vault.
## Installing
### pipx
The package can be installed using [`pipx`](https://pypa.github.io/pipx/):
```sh
$ pipx install journey2md
```
### Homebrew
The package is available via Homebrew. Use the following commands to install:
```sh
$ brew tap davep/homebrew
$ brew install journey2md
```
## Usage
### Getting ready to use
The first thing you will need to do is [create a full ZIP export of your
Journey
data](https://help.journey.cloud/en/article/archive-journal-entries-to-zip-format-v6dsvi/),
once you've done that unzip the export file into a directory, so that all
the JSON data and photo attachments are individually available.
### Assumptions for the "Vault"
As mentioned earlier, this tool assumes that you're going to be making an
Obsidian Vault with the resulting Markdown. With this in mind the tool makes
the following assumptions:
- You wish to have a `YYYY/MM/DD` folder hierarchy for the entries.
- You prefer to have all attachments held in a `attachments` folder below
the location of the entry the attachments are for.
These are my preferences, if yours differ it should be simple enough to
modify the code to taste (or, if what you prefer seems like it could be a
reasonable configuration option, create an issue in the repo and tell me all
about it).
### Create the target "Vault"
Create a directory where the "Vault" will be created. Note that `journey2md`
creates all directories and files *within* this directory.
### Perform the conversion
With all the above done and in mind, run the tool like this:
```sh
journey2md journey-data markdown-vault
```
where `journey-data` is the path to the directory that holds all of the
extracted Journey files, and where `markdown-vault` is the directory you
created that will be the Vault.
## Getting help
If you need help please feel free to [raise an
issue](https://github.com/davep/journey2md/issues).
[//]: # (README.md ends here)