The server version car also disappears, so that would also be another nice to have.
The logic would need to be changed to climb up the tree until it found a server or a Git repo. Two potential issues with that-- the performance overhead (we’d need to test) and if it would find random servers or Git repos in higher directories that you didn’t want it to find.
Since bullet train is a separate module and not part of the CommandBox core, the logic is here:
Ok. I’m going to give it a shot. For now, I’m going to directly modify the installed bullet train module in my home commandbox directory. I know I can use “reload” to keep testing my changes.
I guess this issue can be closed here and I’ll submit a pull request on github?
Well, this really isn’t the right place for the ticket, but we don’t really have a dedicated issue tracker for the little modules like that.
As far as dev, do this:
uninstall your local bullet train
clone the bullet train repo
run “install” in it
run “link” in it
now, you can develop and use ‘reload’ to test. When you like it, just commit the repo. After you’re done, you can run “unlink” and then reinstall the main package again.
Thanks Bro. Here is the pull request.