v3 Rasa UI

If you were or currently are a Rasa UI user, please read below.

As many of you are aware, Rasa has evolved rapidly over the past 2 years. Building a frontend which relies so heavily on the backend features and functions is not easy when everything is changing so frequently, and not being embedded in the Rasa team, we can only do so much to keep up with the very frequent release cycles. Rasa UI has been considerably more popular than I would have ever imagined, but I am really thankful to all the users, as well as all the contributors, which have helped make Rasa UI what it is today.

I would like to introduce you to the concept behind v3 of Rasa UI. Firstly, the whole goal of Rasa UI is to simplify the experience for Rasa users. We want the ability to manage our training data in a centralized location, we want the ability the train and load various models and test them - all without needing to use the CLI on our Rasa box. Additionally, we wanted Rasa UI users to be able to install the tool quickly without too many dependencies or prerequisites.

Version 3 of Rasa UI tries to accomplish these goals, as well as sets the foundation for some of the longer term visions. One of the bigger changes is that Rasa UI no longer requires Postgres, we have switched to SQLite to avoid users needing to setup and configure another (somewhat overkill) component of the stack. Additionally I removed multiple features which were added, but were not core to Rasa requirements. While this may have solved a small user base needs, this has over complicated the code base making it very unmanageable, if you were a contributer who added these features, my apologies, but it is for the best long term. Furthermore, I have temporarily removed the Rasa Core features. I will be rewriting the codebase for these components over the next few weeks and adding them back.

Rasa UI once again works with the "new" Rasa Framework, I would highly suggest checking out the "beta" release of v3 in the branches.