Hye Ararat Beta 4 is now available

Howdy everyone,

Hye Ararat Beta 4 is now available. The release is available here: Release Hye Ararat v3.0.0 Beta 4 · hyecompany/ararat-web · GitHub

For context to those new: Ararat is a modern web interface native to Incus currently in development. You can learn more here: Introducing Hye Ararat: A Web UI native to Incus , and installation instructions are available on our GitHub.


In the Beta 3 announcement, I stated that Beta 4 would introduce storage pools as our first primitive beyond instances. After a community member did some experimentation with authorization and reported several issues, I found some large changes would need to be made to support that in the future. I decided that rather than pushing storage pools through now, it would be better to harden the foundation & delay storage pools to Beta 5. You can read more here: Hye Ararat Beta 3 is now available - #4 by Hye-Dev

Some new information: since Beta 5 will already present a large refactor, I’ve decided to also go after some other areas that have been on my mind. Most notably, Ararat will no longer be built on Next.JS, and will be moving to a Vite stack. This is more compatible with the SPA + client-side nature of Ararat. These changes are well underway on my local machine, and will be on the repo in the coming days.

Thank y’all for the continued testing & feedback! These decisions would have never been made without y’all. As I said in Ararat’s introduction post, the community-driven nature of Incus is what makes it the best, and it’s absolutely amazing to already see this transformation in Ararat at such an early stage.

These architectural changes are not present in this release and will debut in Beta 5 alongside storage pools. That being said, Beta 4 still made significant progress that warrants some announcement & excitement!

What’s New

New File Manager

The file manager now includes:

  • Dedicated search tool
  • Directory count
  • Persistent go to (ctrl/cmd + k as well!) / path copy actions

The file manager is now also significantly faster, taking advantage of the new caching system introduced in Beta 3 last week (see Hye Ararat Beta 3 is now available ). It also now actually informs you when a directory is empty, rather than just showing a generic blank screen! (groundbreaking I know!)

The file editor has also received various improvements, now featuring a theme consistent with the rest of the interface:

I also have expanded the syntax highlighting support, now also supporting C, C++, and Go.

Ararat also now automatically detects what files can be opened in the editor, and what must be downloaded by automatically inspecting the file for binary data before deciding to open. Any text files just open seamlessly, and everything else downloads straight to the disk.

New Instance Tab Design & View Transitions

The new caching system introduced in Beta 3 made data appear pretty much instantaneously, removing the display of a loading spinner most of the time.

Usually, a loading spinner serves as the natural transition between pages, however, after Beta 3, data just appeared immediately, which didn’t feel quite natural, so I’ve employed view transitions across the instance interface to bring back the natural fluid feel Ararat previous gave.

You can also see the instance tabs have been redesigned, they just didn’t feel quite right before. I hope y’all like them, these will be re-used across other primitives.

Additional Notable Changes

Instance logs have been moved to their own dedicated tab, rather than within the instance management dialog. The visual mode is also now properly virtualized, so a 20K line file will no longer lag out your computer!

Several of you reported a bug where Ararat reported that the “path” parameter was required, preventing the attachment of non-filesystem storage volumes. This has been fixed. You can now attach your non-filesystem volumes with no artificial blockers.

Side note:

I’m aware of some issues introduced by the data fetching layer re-write back in Beta 3. While this release did address some of those, there are still some present.

For example, the instance table may not properly detect its stale from the cache unless a change is made while Ararat is open, and CPU usage calculation always outputs 0%. These are all caching issues that will be addressed early-on in Beta 5’s development.

The reason I note this is data fetching is used literally everywhere, and Beta 5 is Ararat’s monthly “large” release, so it leaves the normal weekly cadence for a release date of May 24th, which is a little far out for something that can get pretty annoying.

Usually, I would merge the same fix for an issue like this from the bleeding edge into the active beta channel, however, since Beta 5 is structurally different, the fix does not overlap at all (the layer was effectively re-written again). Therefore, I recommend for the most stable experience, actually sticking to the bleeding edge builds until then. You can think of this as a using Windows Vista vs. Windows 7 Beta situation. Apologies!