search

theunraveler / taskwarrior-web

A web interface for the Taskwarrior todo application. Because being a neckbeard is only fun sometimes.
http://theunraveler.github.com/taskwarrior-web
MIT License
527 stars 63 forks source link

executable not created during install #83

Open mvdw opened 7 years ago

mvdw commented 7 years ago

As instructed, I did

michiel@Janus:~> gem install taskwarrior-web Fetching: taskwarrior-web-1.1.11.gem (100%) ERROR: While executing gem ... (Gem::FilePermissionError) You don't have write permissions for the /usr/lib64/ruby/gems/2.1.0 directory. ... etc.`

So, I run as root:

michiel@Janus:~> sudo !! sudo gem install taskwarrior-web root's password: Successfully installed taskwarrior-web-1.1.11 Parsing documentation for taskwarrior-web-1.1.11 Done installing documentation for taskwarrior-web after 0 seconds 1 gem installed

Then I tried to run it:

michiel@Janus:~> task-web If 'task-web' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf task-web

Hmmm...

michiel@Janus:~> which task-web which: no task-web in (/home/michiel/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games) michiel@Janus:~>

How come?

(ruby 2.1, I am not a ruby programmer)

mattdf commented 7 years ago

You probably don't have the directory where it gets stored in your PATH.

See if you can find it by running find /usr -name "task-web" and then add that directory to your PATH.

mvdw commented 7 years ago

Thanks!

michiel@Janus:~> find /usr -name "task-web" /usr/lib64/ruby/gems/2.1.0/gems/taskwarrior-web-1.1.11/bin/task-web michiel@Janus:~>

This is enough for me to start testing. Still strange there is no link created in one of my path directories.

mvdw commented 7 years ago

It works! Starting the "task-web" at the command line, the browser did not open. but it was easy to figure out that I had to browse to http://localhost:5678.

At first sight: The UI is very nice!

So, the executable WAS created. Only problem: no link was created in one of the folders in my path. Do I keep this issue open to solve that?

mattdf commented 7 years ago

Not sure if it's default behaviour or not, but you can always just run "gem list" or "gen environment" to see where things are installed. I need to update the gem anyway - I'll close this issue once I've rebuilt the rubygem.