You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be very useful to add a dura status command.
This should probably include whether or not the dura serve process is running, and it’s PID; a list of currently-watched git repos; and potentially the date/time (and tag?) of the most recent automatic commit done by dura serve, for each watched repository.
I'm not sure how that last part could be done without "knowing" the location of the log file (I run dura by using dura serve > $HOME/dura.log & so could extract it from ps, but presumably that won't always be the case).
Possible output assuming it's running, showing the time stamp but not the commit tag:
dura serve is running as PID 2756
Watching git repos:
“/home/user/repo1, last commit: 2022-02-15 14:20:35”
“/home/user/repo2, last commit: 2022-02-14 18:45:55”
If it's not running, then a line stating that, or just a non-zero status could be used.
--Paul.
The text was updated successfully, but these errors were encountered:
Todo for later: Check if running dura serve twice doesn't make issues.
It may at the moment, there's some discussion/ideas about preventing it in #2.
I like the idea, but I think we need to be careful what goes into the command. The daemon status should mostly be down to the OS's service manager (systemd or whatever), and I think we should avoid overlap here. Info like the list of watched services would be fine.
PJC-64
changed the title
Feature Request: status command
Feature Request: dura status command
Feb 15, 2022
I think it would be very useful to add a
dura status
command.This should probably include whether or not the
dura serve
process is running, and it’s PID; a list of currently-watched git repos; and potentially the date/time (and tag?) of the most recent automatic commit done by dura serve, for each watched repository.I'm not sure how that last part could be done without "knowing" the location of the log file (I run dura by using
dura serve > $HOME/dura.log &
so could extract it from ps, but presumably that won't always be the case).Possible output assuming it's running, showing the time stamp but not the commit tag:
If it's not running, then a line stating that, or just a non-zero status could be used.
--Paul.
The text was updated successfully, but these errors were encountered: