99designs / 99designs/cmdstalk
Wildcard tube matching (incl new tubes)
- Lingua principale
- Go
- Stelle
- 76
- Fork
- 14
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
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.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Look at the tube matching logic in the cmdstalk source code, likely in the main.go or a dedicated parsing file. Understand how the -tubes flag currently works and where tube names are filtered. The change involves adding wildcard pattern matching (like 'contests_*') to listen to present and future tubes. Test by running cmdstalk with the new flag against a beanstalkd instance.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- go
- Ambito
- backend, cli
- Tipo di issue
- Funzionalità
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Specificata chiaramente
- Idoneità per principianti
- 45/100