sorentwo

sorentwo

Oban Core Team

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:

  1. 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.
  2. 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.
  3. 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. :yellow_heart:

Most Liked

sorentwo

sorentwo

Oban Core Team

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 :yellow_heart:.

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

sorentwo

Oban Core Team

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 verbose setting to control log levels. This command mirrors the behavior in Oban and is respected by all queries.

  • Deprecate stats configuration. 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 the stats option pointless.

  • Add stats_interval to control how often node and queue counts are refreshed. The default value is every 1s (you shouldn’t need to change this)

  • Add tick_interval to 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

Eiji

Challenge accepted! :077:

Array.from(document.querySelectorAll(".btn--destructive")).forEach((el) => el.click())

                                                    A few attempts later …


Well … good job! :smiley:

It’s why I love fault-tolerant so much!

Where Next?

Popular in News & Updates Top

fhunleth
It looks like it’s finally safe to announce that Nerves supports Erlang/OTP 26 and Elixir 1.15! We’ve updated dozens of Nerves and close...
New
DominikWolek
After years of developing our framework, we have a release candidate for Membrane Core 1.0! :tada: The new version introduces children g...
New
mobileoverlord
New versions of the Kiosk systems are out. These systems update official Nerves systems with a local web browser for rendering user inter...
New
bartblast
Hologram v0.7.0 is out! This is a milestone release for the Elixir-to-JavaScript porting initiative. 49 contributors ported 150 Erlang fu...
New
zachdaniel
Hey folks! We’re starting a new weekly newsletter with the goings on of the various Ash packages and other interesting news from myself a...
New
hugobarauna
Hugging Face is a platform for building, sharing, and collaborating on machine learning applications. This blog post explains how to run...
New
zachdaniel
Hey everyone! What I’ll cover in this post: Major refactors The future of Ash.Flow Current state of atomics and bulk actions Whats nex...
New
fhunleth
Nerves systems provide the operating system, libraries and other tools for building firmware for specific hardware. The Nerves Core Team ...
New
hwuethrich
Hi! I’m happy to share my first Elixir library. But first some … Background As an Elixir company from a country with 4 official languag...
New
zachdaniel
Working with nested forms in Ash was already great, but it’s even better now with a the new features that will be in the next release of ...
New

Other popular topics Top

Harrisonl
We have an ECS cluster with 4 services, where each task joins a single cluster, via discovery ECS discovery service. Currently when I de...
New
JeremM34
Hello, how can I check the Phoenix version ? Thanks !
New
fireproofsocks
Forgive me if this is obvious, but how does one delete a database record WITHOUT selecting it first? Ecto.Repo — Ecto v3.14.0 has exampl...
New
chrismccord
This release brings a number of exciting features, including integration with the new Phoenix LiveDashboard and Phoenix LiveView. There h...
New
josevalim
Hi everyone, One of the features added to Elixir early on to help integration with Erlang code was the idea of overridable function defi...
New
alice
Hey, Just curious what are the main benefits of Elixir compared to Clojure? When is Elixir more useful than Clojure and vice versa? Th...
New
jason.o
In the code below, if the create action is not set to accept “extra_key” as an input, it errors out with a message shown above. Is there ...
New
dblack
I’ve got an issue with an app and I’ve no idea of how to troubleshoot it. I’m hoping someone here might have seen something similar. I p...
New
jononomo
For some reason my phoenix channels are working for me in my local dev environment, but as soon as I deploy via Docker, I get a 403 error...
New
svb
Hi! Currently I want to submit a form by pressing the Enter key. However, since my input field is of type “textarea” this is just adds a...
New

We're in Beta

About us Mission Statement