This repository includes the Next version of Orkestrator frontend for the arkitekt platform. It is currently under development and not ready for production.
Important
This version of Orkestrator is only working with the next version of the arkitekt platform. It is not compatible with the released version of the platform.
While the new version of Orkestrator is still under development, you can install it by downloading one of the releases from the release page fitting your operating system. We provide installers for Windows and MacOS, as well as an AppImage and deb package for Linux.
Note
We are working on providing a better installation experience, including automatic updates and a better installer. But for now, this is the best we can do. We will also provide a portable version of the application in the future.
We provide a both an AppImage and a deb package for Linux. The AppImage should work on most distributions, while the deb package is specifically for Debian based distributions like Ubuntu.
Because the application is not signed (because it freaking costs money and is a pain in the ...) you need to "dequarantine" the application before you will be able to open it. After installation you can do this by running the following command in your terminal (search "terminal" in spotlight):
xattr -c /Applications/orkestrator-next.app # or wherever you installed itThis will remove the quarantine attribute from the application and you should be able to open it. We are sorry for the inconvenience. Soon we will go the signing route, but for now this is the only way.
Just download the installer and run it. It should install the application and create a desktop shortcut for you. Windows might ask you if you really want to install the application, because it is not signed. You can safely ignore this warning and proceed with the installation. Follow the instructions here
Before the new version of Orkestrator can be merged into the main repository, the following features need to be implemented:
- Build around arkitekt-ts (instead of custom graphql clients)
- Move Basic UI to Shadcn/UI
- Move to Vite
- Move to React 18
- Move to Electron (Allows us to finally use SSL on the network)
- New Workflow Engine (Fluss)
- Integrate Kabinet App Store
- Move to new GraphQL Protocols (subscriptions based on graphql-ws, standardized error and param handling (pagination(filter))
- Basic UI Testing
- Documentation, Documentation, Documentation
- Lazy Load Modules (only if corresponding service in Deployment)
- Hosted Deployment (Discarded for electron app)
- CI/CD Pipeline
- User Management
- Advanced App and Config Management (around Fakts)
- Move to Mikro Next
- Establish "Views" as central concept
- Deprecated OMERO metadata support
- Lazy Renderer (similar to Vizarr)
- Establish new Workflow UI + Engine (typesafe, wizard, ...) (looks nice)
- Move to Fluss Next
- More tightly integrate Schedulers in UI
- Allow Resource Management in UI ( provisional UI for resource management)
- Move to Rekuest Next
- Build UI for scheduled tasks, and task management
- Hookify Rekuest (useNode, useTemplate, ...)
- Establish Kabinet
- Create App Store like Feature
- Create App Store UI
- Establish Kraph as the de facto "Knowledge Graph" for Arkitekt Services
- Create Knowledge Widgets
- Allow simple creation of new Graphs
- [ ]
- Improve Omero UI
- Allow metadata editing in UI
- Port is now deprecated for Kabinet
- Build Kluster UI
- Elaborate on Dask-Cluster integration
- Provide support for other cluster
- Implement basic trace visualization