sorentwo
Oban Web: Private Beta
Many months ago when I originally announced Oban I mentioned that a LiveView powered UI would be available for it soon. Well, the “soon” part wasn’t especially accurate, but I am pleased to announce that the Oban UI is now in private beta.
You can see a live version of the UI running at https://oban.dev/oban. The demo runs semi-constant stream of random jobs and doesn’t contain any actual personal information. Feel free to discard or delete jobs, it will just make more.
Now on to the “private” part.
Why is it private?
Oban itself has taken a ton of time to develop and support. I absolutely love the project, adore working on it, and am stunned by the positive response it has received. The UI requires even more work to get right and make into a truly useful tool for production applications. This is something I want to focus on and give proper attention—eventually I hope to sustain the project and by charging for a UI license.
Please note that Oban itself will always be entirely open source. There will never be an “enterprise” version with gated features.
Why is it a beta?
There are a few reasons:
- Installing it can be tricky. The package is largely stand alone, but it needs to be routed and configured from within a phoenix application. I expect that it will take some time to refine the installation steps and work out the kinks.
- The UI is missing some important features, has some known bugs and definitely needs polishing. That will take time, and I want to ensure that the initial users are willing to give meaningful and helpful feedback.
- There aren’t any proper support channels yet, it’s all a bit ad-hoc.
How does the UI integrate into my app?
The package is named oban_web and it is a published privately under the oban organization on hex.pm. The package is entirely self contained—it doesn’t hook into your asset pipeline at all. Just mount the live module in your router, pass some configuration, run some migrations and its up.
What’s on the roadmap?
As new features are added and bugs are fixed I’ll post about them here. Here are some of the bigger planned fixes/features currently:
- Sidebar Accuracy
- Pagination
- Details View (with error details, unique information)
- Queue Controls (scale up, down, pause from the UI)
- Bulk Actions
- Node Information
- Live & Historic Metrics
How do I get into the beta?
Anybody wanting to join the beta now please go to https://oban.dev
The site has a little more info and a tiny little signup form for the beta.
Thank you to everybody that has expressed interest and offered support. If you have any questions or comments please leave them here. ![]()
Most Liked
sorentwo
I’m pleased to announce that the UI is no longer in beta and is now generally available through a paid license. There are new installation docs, an faq, a changelog and a public roadmap is in the works. This is still just the beginning for the product!
Thank you to everyone that participated in the beta! You’ve been extremely helpful and I’m grateful for your support and all of the feedback
.
There will be a two week grace period for existing beta users (in addition to the 7 day trial). You can access your current license key and subscribe to a plan through your account page by signing in with your existing email. If you have any questions please reach out here, on slack, or by sending an email.
sorentwo
ObanWeb v1.1.0 is out today with a fix for verbose logging and overhauled stats tracking. It now uses less resources when nobody is connected to the dashboard.
Changes
-
Add
verbosesetting to control log levels. This command mirrors the behavior in Oban and is respected by all queries. -
Deprecate
statsconfiguration. The stats module is entirely overhauled so that it only refreshes when one or more users are connected. That prevents it from using any connections or performing any queries while testing, which renders thestatsoption pointless. -
Add
stats_intervalto control how often node and queue counts are refreshed. The default value is every 1s (you shouldn’t need to change this) -
Add
tick_intervalto control how often the jobs table and job details are refreshed. The default value is every 500ms (you shouldn’t need to change this)
Eiji
Challenge accepted! ![]()
Array.from(document.querySelectorAll(".btn--destructive")).forEach((el) => el.click())
A few attempts later …
Well … good job! ![]()
It’s why I love fault-tolerant so much!
Popular in News & Updates
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #hex









