Where communities thrive
your own community
Explore more communities
A node process manager that isn't spanners all the way down
i know - minimum viable, right?
having second thoughts about pushing this multi kill/restart into the daemon
the beauty of connecting to the remote process is that it verifies the user has access to do the action
we lose that knowledge telling the daemon to do it...
sorry, took me a while to realise this!
quick question -
does there have to be an account with the same name on the machine you’re adding the user on?
otherwise the unix permissions thing falls over
Do you think it would be rude of the daemon to create the group it's supposed to be running as on first start?
just trying to think about the first use experience
the default group is 'staff' which is fine for dev on os x but on linux can cause problems
debian etc has a 'staff' group by default but it has no members
was thinking of changing the default group to 'boss' instead
I figure there's sort of precedent - if I apt-get install apache, i get a www/apache group along with it
i think is fine
i think is good practice
you could prompt?
do the "right thing" by default for them that wouldn't do it themselves
allow the wizards to opt out it really offends them
as you say, apt has been doing it without ruffling too many feathers forever
had an odd one last night
bs stop [pid]
something you ate?
boss would kill the proc
but then start it back up
and inc the restart count
and then i ate it