Summary: The All-in-One container deployment method is now deprecated and won't be supported in the future.
After several discussions and some consideration we have decided to deprecate the All-In-One-Container Docker
deployment method. We'll explain the reasons for this in this blog post But first: don't panic! If you are running the All-In-One-Container for your Funkwhale instance, you won't be facing this change alone!
## We will support your migration
Firstly, there will be builds of the AIO-Container for the next few releases. Funkwhale 1.3.x will
still be available for you without any change. Secondly, we will provide a guide how to migrate your
installation to the multi container deployment. Thirdly, if you are experiencing any issues with the migration,
we will provide support in our chat rooms and forums. We can manage this transition together 😄
## Reasons
There are several reasons for this decision and I'll try to explain them here.
Funkwhale has a quite broad feature set and several deployment methods. Its hard to maintain all of this. We do
think it's important to cover as many use cases as possible, but there are some limits. The AIO-Container
previously was maintained by [@michaelmob](https://github.com/michaelmob). Sadly, they seemed to stop working on this and some of our updates
have caused builds to fail. We took over the project to make sure the builds work, but we don't have the
resources to maintain this in the long-term. We want to focus on proper support of the multi container and ansible
setup as well as spending more time improving Funkwhale itself.
On a technical level the AIO-Container goes against the idea of a Docker deployment. Usually each service
lives in its own container, which allows scaling and is quite robust against the whole stack failing. This method
is supported by our multi container setup and works quite well.
If you have any questions or want to help creating a migration guide, get in touch through our