Finally, follow the installation instructions to get the Jupiter scripts locally. I'll assume you did the Docker installation presented there.
To startup, you'll need a Notion account. It's free to setup, but you'll eventually need to sign up for the paid version if you want to use it properly. The first four months are free however, so you'll get a good feel for whether it's useful for you or not.
Once that's done, you'll need two crucial pieces of information - your space id, and a token for accessing the API. In order to do this, you'll need to:
- Go over to notion.so - the website. You should be seeing your space and anything you've setup there manually.
- Open your browser's inspector. Refresh the page and wait for things to calm down.
- Find the
/getPublicPageDataAPI call on the Network tab.
- The response for this will be a JSON object with a
spaceIdproperty. That's your space's id. Write it down somewhere.
- In the headers field there will be a
cookieset with the value
token. That's your token for accessing the API. Write it down somewhere.
The painful part should have passed. You're ready for the proper part.
You'll also need a timezone in the
Continent/City format, like those provided by the
tz database. This needs to be specified at the start,
and is used to properly configure task deadlines, etc.
Create A Workspace
The workspace is where all your work in Jupiter happens. You'll need to create one.
Go over and create a directory somewhere on your local machine. It's a good idea to have this be managed by Git. Up to you though here - Dropbox, Google Drive, etc. or just regular storage on your machine might be enough. It should look something like this:
$ mkdir my-workspaces $ cd my-workspace $ git init $ docker run \ -it --rm --name jupiter-app -v $(pwd):/data \ horia141/jupiter:latest workspace-init \ --name "Plans" \ --timezone "YOUR_TIMEZONE_HERE" \ --space-id="YOUR_SPACE_ID_HERE" \ --token="YOUR_TOKEN_HERE" $ git add . # Adds everything in the directory $ git commit -a -m "Initial commit"
You should now see a folder named
Plans in your Notion.so space. This is the Notion representation of the workspace
and it's here where you'll be doing most of the interacting with Jupiter.
Create A Project
Work in Jupiter is organised around projects. These contain an "Inbox", which is where your day-to-day tasks live. Both the ones you create and the ones the system creates. This is essentially a Trello/Jira like board, with some fancier capabilities. There are also "Recurring Tasks", which are templates for tasks that occur periodically - daily, weekly, monthly, quarterly, or yearly. Think chores and habits. Finally there are "Big Plans", which are longer-term projects, usually taking 1-6 months. They're made up of tasks too, and these tasks will appear in the Inbox. There's more to say here, but as always, check the docs.
To create a project you need to run the
project-create command, like so:
$ docker run \ -it --rm --name jupiter-app -v $(pwd):/data \ horia141/jupiter:latest project-create \ --key my-work \ --name "My Work" [ Some output here ] $ git add . $ git commit -a -m "Created project 'My Work'"
The first argument is a "project key", which must be unique to your workspace and which will be used to reference the project later. This will create a bunch of structures in Notion under your plan, looking like so:
The inbox at this point will look something like this:
So it's basically a blank canvas waiting for your work. The recurring task view and the big plans view will look the same.
Create A Recurring Task
In this section you'll create a recurring task and generate instances of it corresponding to various times in the inbox.
To start go to the "Recurring Tasks" view and add a new recurring monthly task named "Clean Drogon's lair". You need to click the "New" button, or the "+" button under the "Monthly" column. Complete the task as follows:
Notice that "Period" is set to "Monthly" (one of five valid choices). As expected this determines the "periodicity" of the recurring task, or when a new task will appear in the Inbox. For the monthly choice, you'll get one "Clean Drogon's lair" task every month.
Before we move on to generation, you need to synchronise Notion with the local state by running a
This is needed because (at this moment), there's no way for Jupiter to know about changes that happen in Notion
automatically. So you have to instruct it like so:
$ docker run \ -it --rm --name jupiter-app -v $(pwd):/data \ horia141/jupiter:latest sync [ Some output here ] $ git add . $ git commit -a -m "Synced some remote tasks" $ docker run \ -it --rm --name jupiter-app -v $(pwd):/data \ horia141/jupiter:latest recurring-tasks-show \ --project my-work [ Some output here ] Army maintenance: id=0 Clean Drogon's lair period=monthly $ docker run \ -it --rm --name jupiter-app -v $(pwd):/data \ horia141/jupiter:latest recurring-tasks-show \ --project my-work \ --id 0 [ Some output here ] id=10 Clean Drogon's lair period=monthly eisen="" difficulty=none skip_rule=none suspended=False must_do=False due_at_time=none due_at_day=none due_at_month=none
Note: the above can just as easily be done via the
recurring-tasks-createcommand. You won't have to run a separate sync step there, as the command will take care of creating the tasks on Notion side for you.
To generate the tasks, you can run:
$ docker run \ -it --rm --name jupiter-app -v $(pwd):/data \ horia141/jupiter:latest gen --period monthly [ Some output here ]
This will leave the inbox looking like:
You can set another date to run the generation for, like so:
$ docker run \ -it --rm --name jupiter-app -v $(pwd):/data \ horia141/jupiter:latest gen --period monthly \ --date=2020-05-01 [ Some output here ]
And get a final output of the sort:
This concludes this short introduction to Jupiter.