Create a web interface

[bkeepers]

Should allow viewing workers, inspecting queues, and viewing and trying failures.

[DAddYE]

I suggest before webinterface a CLI for easily know running queues, status, etc. See i.e. http://github.com/daddye/foreverb

[bkeepers]

Interesting idea. Do you find a CLI interface useful on production servers? Seems like a web interface might be more helpful for monitoring on production servers, but I don't know.

[DAddYE]

A web interface is more simple, Im right, but I think it's more important a CLI, maybe can act as a api for a web interface.

[wjossey]

I've started working on this web interface a bit. Right now it's running in isolation, with me extending the different adapters to get state-of-the-qu information to render to the view. Would you rather I made these modifications to the adapters in qu w/pull requests?

[bkeepers]

@wjossey I want to warn you that I'm going to be very particular about the web interface. We've got a pretty high design standard at Ordered List (see Speaker Deck and Gaug.es). I know one of our designers started working on the web interface, but I don't know how far he got on it.

That being said, I don't want to discourage you from working on this. Any help is greatly appreciated, and even if the UI changes a little, I don't the the changes to Qu will differ that much. I would say make your changes directly to the backends and submit a pull request.

[wjossey]

Glad to hear that you've already got someone working on it. I'll wait for his UI to get pushed then make contributions to it. I'll try to pick on a few core things to work on in the meantime.

[bkeepers]

Ok. Like I said, I don't want to discourage you from working on it, just wanted to give fair warning.

[fbjork]

Any update on the web UI progress?

[bkeepers]

Nope, not yet. I'll post here when there is some progress.

[wjossey]

@fbjork I've got a private repo with just some basic redis support if you'd like a copy of it. It's not styled and is still highly experimental.

[fbjork]

Thanks for the update. I'm using MongoHQ's web dashboard as my web UI for now:)

[didip]

Hi all,

I'm currently reviewing this gem for work. At a glimpse, qu is simple and I love the decision of breaking up backends into their own gem.

I have a small feature request on the web interface: Please put it in separate gem.

We are unable to use Resque because of Sinatra dependency defined in Resque gemspec. And we can't use Sinatra because of Rack gem conflict.

[fbjork]

Apart from a web UI, is there additional work needed in the qu core library to support it?

[bkeepers]

@didip definitely. I agree it should be a separate gem.

@fbjork yeah, there will probably need to be some backend changes to support the web UI. Sorry I haven't been able to make progress on this. Feel free to work on it.

[jnunemaker]

We can steal some stuff from jnunemaker/flipper-ui to make this happen. I'm hoping to crack on it over the holidays. We'll see...

[Jonic]

Did anything ever come of this? It would be really handy for keeping an eye on my queue while developing apps!

[jnunemaker]

Not yet, but still on the list.

[thiensubs]

Please upgrade to Rails 4.2.1!