Open SeriousM opened 10 years ago
yeh, a settings.json. kadira does this pretty nicely, detecting Meteor.settings.kadira and using that if it exists
another reason for the config file is to turn this off, during test runs etc. i just started playing with velocity and it has trouble with settings.json tho ...
further, we usually have a few environments - dev/prod/staging/testers etc. often times the test server is used by testers but is not localhost. I would want to track that differently or just ignore it.
If possible I would like to use a configuration-option where I can decide if I want to connect to tail.sh at all and if, which project id I want to use. This would help to control development / test / production environments. The popup is not very nice for everyone (eg: #7, #9)
I would create a PR for that if you like the idea.