Skip to content

Latest commit

 

History

History
67 lines (39 loc) · 2.01 KB

README.md

File metadata and controls

67 lines (39 loc) · 2.01 KB
Raw

dock-warrior

Docker environment for taskwarrior/timewarrior/etc.

HISTORY

So, taskwarrior + timewarrior + bugwarrior and other stuff runs my business. I just do the coding. In 2022, I had to abruptly switch to a backup system. Rather than reinstall everything yet again and migrate the data, I thought I'd dockerize everything.

HOWTO

Build with docker build -t srl295/dock-warrior:dev .

Then run with (script alias recommended!)

$ export DOCK_WARRIOR_CONFIG=/somewhere/config
$ export DOCK_WARRIOR_DATA=/somewhere/data
$ alias dock-warrior="docker run -v ${DOCK_WARRIOR_CONFIG}:/config:ro -v ${DOCK_WARRIOR_DATA}:/data:rw --"
$ alias dock-warrior-task="dock-warrior task"

now if you do dock-warrior-task it runs task inside of the container.

SETUP

data

The /data volume has subdirectories for each component:

  • task/ (this is the TASKDATA variable)
  • timew/ (this is the TIMEWARRIORDB variable)

config

The /config volume is intended to be mounted readonly, and has subdirectories for each component:

  • task/

The file /config/task/taskrc (no initial dot) is used as the TASKRC

  • timew/

This isn't currently used, because timew keeps the data and config in the same spot.

  • bugwarrior/bugwarriorrc

Bugwarrior is setup to look for its config file here.

MIGRATING

to migrate from a 'desktop' installation:

  1. create the data and config directories
  2. copy ~/.taskrc to config/task/taskrc
  3. edit taskrc to set data.location=/data/task
  4. you might want to disable any task hooks for now (TODO)
  5. copy ~/.task/ directory to become data/task/
  6. copy ~/.timewarrior/ directory to become data/timew/

task-time integration

  • for now I modified the standard hook to have '/opt/bin/timew' as the path instead of 'timew' - TODO need to fix the container's search path

AUTHOR

Steven R. Loomis, @srl295 of @codehivetx