This is a little dashboard that tries to take care of you when you're using your terminal. It tells you cute, self care things, and tries not to stress you out. It shows:
- the last tweets from @tinycarebot, @selfcare_bot and @magicrealismbot. The first two tend to tweet reminders about taking breaks, drinking water and looking outside, and the latter tells you strange, whimsical stories. If you don't like these bots, they're configurable!
gitcommits from today and the last 7 days. When I get stressed out because I think I haven't done anything, it turns out that I only think about big and serious commits, and forget about all the tiny amounts of work I've actually done throughout. Hopefully this will help you too <3
- the weather, because you might get rained on.
It looks like this, and updates every 20 minutes.
Make it go
npm install -g tiny-care-terminal
yarn also works fine.)
2. Setting the environment variables
After installing the npm package, you need to set up the configuration in your Terminal.
Every OS and shell is different so I probably won't hit all of them, but the bottom line is that you should copy those environment variables wherever the rest of your system's variables live. For example,
- if you're using
zsh, that's probably in your home directory's
- if you're using
bash, that could be your
- if you're using
set -gx key valuein your
Note that the
export bit is pretty key, to make sure that they are globally available. To check that the variables have been set correctly, you can print them in the terminal -- for example,
Configure the dashboard
All the settings the dashboard looks at are in the sample file
sample.env. This file isn't used by the dashboard, it just lists the environment variables that you can copy in your
TTC_BOTSare the 3 twitter bots to check, comma separated. The first entry in this list will be displayed in the big party parrot box.
TTC_SAY_BOX = parrot | bunny | llama | cat | yeoman | mario | ironman | minions | panda, to party with a different parrot (or, more specifically: to have a different animal say a message in the big box). You can create your own custom art(.ansi file) here and download and supply it's absolute path to render it within box. (eg:
TTC_REPOS, a comma separated list of repos to look at for
TTC_REPOS_DEPTHis the max directory-depth to look for git repositories in the directories defined with
TTC_REPOS(by default 1). Note that the deeper the directory depth, the slower the results will be fetched.
TTC_WEATHER, the location to check the weather for. A zipcode doesn't always work, so if you can, use a location first (so prefer
TTC_CELSIUS(by default true)
TTC_APIKEYS-- set this to false if you don't want to use Twitter API keys and want to scrape the tweets instead.
TTC_UPDATE_INTERVAL, set this to change the update frequency in minutes, default is 20 minutes.
TTC_TERMINAL_TITLE-- set this to false if you don't want the terminal title to be changed on startup.
Set up Twitter API keys
The dashboard has two alternatives for reading tweets: using your API keys or scraping. API keys is preferred (because lol scraping), but if you're really not into that, then skip the next section and read the bit about setting
You need Twitter API keys for the tweets to work. It should be pretty easy to create a new app, and get these 4 values. After you've set them up, set these env variables (see the
sample.env for an example):
TTC_CONSUMER_KEY='...' TTC_CONSUMER_SECRET='...' TTC_ACCESS_TOKEN='...' TTC_ACCESS_TOKEN_SECRET='...'
You can exit the dashboard by pressing
q. You can refresh it manually by pressing
You can press 'p' to switch parrot box to pomodoro mode.
Other commands while in pomodoro mode:
s - start/pause/resume pomodoro e - stop pomodoro u - update pomodoro duration b - update break time
To change default pomodoro and break durations set following variables in minutes (these should be numbers):
Halp I don't see my commits
- did you forget to export your
TTC_REPOSenvironment variable? Open a new tab, and type
echo $TTC_REPOSto make sure it's not empty. Note that spaces inside the repo names are not supported right now
- also there seem to be problems sometimes if the paths you're using are not fully qualified -- that is, use
~/Codeand see if that helps.
- did you use
yarn? I know
yarnis cool, and I've seen it work with this, but can you double check that it still doesn't work with a basic
Take care of yourself, ok?