99designs / 99designs/cmdstalk

Wildcard tube matching (incl new tubes)

Offen
#1 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Go
Sterne
76
Forks
14
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

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.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
go
Bereich
backend, cli
Issue-Typ
Feature
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Klar beschrieben
Anfängerfreundlichkeit
45/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.