99designs / 99designs/cmdstalk

Wildcard tube matching (incl new tubes)

オープン
#1 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る
主要言語
Go
スター
76
フォーク
14
PR マージ指標
30日以内にマージされた PR はありません

説明

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.

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
go
領域
backend, cli
issue の種類
機能追加
難易度
3/5
見積もり時間
1〜2日
活発さ
停滞
明瞭さ
明確に書かれている
初心者へのやさしさ
45/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。