Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration #10

Open
SeriousM opened this issue Sep 12, 2014 · 2 comments
Open

Configuration #10

SeriousM opened this issue Sep 12, 2014 · 2 comments

Comments

@SeriousM
Copy link

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.

@dcsan
Copy link

dcsan commented Oct 30, 2014

yeh, a settings.json.
kadira does this pretty nicely, detecting Meteor.settings.kadira and using that if it exists

@dcsan
Copy link

dcsan commented Oct 31, 2014

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants