Another idea I’ve had, if the nitro executable would be able to figure
out if it’s installed as a gem or not, it could in the second case take
care itself of setting the loadpath for nitro. That way when running
from the repo you wouldn’t have to juggle too many environment variables
and the likes, it would “just work”.
Ein Fuchs muÃŸ tun, was ein Fuchs tun muÃŸ