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

Wildcard tube matching (incl new tubes) #1

Open
lwc opened this issue Jul 31, 2014 · 3 comments
Open

Wildcard tube matching (incl new tubes) #1

lwc opened this issue Jul 31, 2014 · 3 comments

Comments

@lwc
Copy link
Member

lwc commented Jul 31, 2014

One drawback to our current docker setup is that services like mysql and beanstalk are not isolated between 99designs services (contests / swiftly etc).

This issue doesn't manifest for mysql, as (most) applications are isolated from each other at a database level. Unfortunately it does manifest for beanstalk, as cmdstalk, when run with -all will happily listen to queues from all applications.

While this problem is better addressed at a docker level, one feature that would alleviate this in the short term is wildcard tube matching.

Something like the following could listen to all present and future tubes starting with "contests_":
cmdstalk -cmd="/path/to/your/worker --your=flags --here" -tubes="contests_*"

Happy to pair with someone on it, for the go experience.

@pda
Copy link
Contributor

pda commented Jul 31, 2014

Yep — @harto and I were just discussing an idea like this yesterday.

I think I'd prefer matching on prefix rather than wildcard. It suits the use-case you've described without posing unnecessary questions like what does -tubes="contests**-hello-*" mean, and avoids cmdstalk competing with the shell to expand * chars.

@lwc
Copy link
Member Author

lwc commented Aug 1, 2014

Seems fair enough, prefix matching would solve my problem 👍

@joho
Copy link

joho commented Aug 1, 2014

👍 to prefixing

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

3 participants