cPFence Exactly, the smaller user base does add some complications. I think it might be a good idea for them to open up beta testing for clients who are willing to participate. Switching from Docker to systemd is a bold move by the Enhance team, but they’re talented developers and, given enough time, I’m confident they’ll pull it off. During discussions with my team about how to adapt to systemd, we realized that the possibilities for Enhance are much greater now. This shift will allow for new features and integrations that were previously delayed or difficult to implement due to Docker’s limitations.

Like i said in earlier posts, you plan and push smaller things first so when you have to revamp whole architecture you can do that in peace without users dancing on shoulders bcz by taking care of necessary things first, user do not poke you about new features and you take your sweet time to work on big changes.. but here everyone gets triggered by this approach so now only thing you can do is wait patiently!

    cPFence I think it might be a good idea for them to open up beta testing for clients who are willing to participate.

    +1 for opening up a beta testing branch, DA and other panels have it as well as alpha, may also speed up the release times for features the panel desperately need like catchall email, wildcard options for blocking, and improved usage stats,.

    These channels are helpful for real world testing to filter out any bugs that can be reported and test compatibility with specific environments.

    1. Developers of apps for enhance will benefit ahead of time rather than having to wait for a full release to explore what they need to update in their code.

    2. Hosting providers / Web designers that host customer sites also benefit as well to test new versions and what to expect on upgrading to a newer release.

    These are only a couple of the off of my head.

        ecknz +1 for opening up a beta testing branch, DA and other panels have it as well as alpha, may also speed up the release times for features the panel desperately need like catchall email, wildcard options for blocking, and improved usage stats,.

        These channels are helpful for real world testing to filter out any bugs that can be reported and test compatibility with specific environments.

        Developers of apps for enhance will benefit ahead of time rather than having to wait for a full release to explore what they need to update in their code.

        Hosting providers / Web designers that host customer sites also benefit as well to test new versions and what to expect on upgrading to a newer release.

        These are only a couple of the off of my head.

        I also agree with this approach..

          cPFence Could you please elaborate on the transition process from Docker to Systemd?

              Looking at a roadmap and knowing that the release date won't be met is, without a doubt, frustrating. However, comparing Enhance with another control panel is overly simplistic – we all know there’s room for improvement. But this update is massive and needs to be thoroughly tested. If the team releases something with flaws, we’ll all pay the price and face serious issues. So, the best we can do right now is wait! Rushing won't help.

              I’ve personally been working on the PT-BR language update for months and won’t release it until I’m certain everything’s working perfectly.

              I know this isn’t just a simple language update – it’s something essential. Even if it takes another month, I’ll be satisfied as long as the release is safe for my business. In the meantime, I’ll make do with what I have.

              And a phrase that sums up my feelings is: "Better to wait for excellence than to rush with mediocrity." I already have a solid base of clients on Enhance, and the only thing that’s causing a bit of frustration for me is the S3 backups, which aren’t working well with Backblaze in my case.

                alenguav Could you please elaborate on the transition process from Docker to Systemd?

                The transition from Docker-based services to systemd-managed services can indeed be complex, especially for production environments. I wish I had beta access to v12 so I could know more, but my guess is that Enhance will likely release an update script to automate the process. I also expect that their CLI upgrade might involve transitioning each service incrementally and verifying each before switching off Docker. This approach could help mitigate downtime since each service would only briefly disconnect.

                If it were up to me, I’d definitely consider beta testing for this update to gather real-world feedback, but I trust the Enhance team’s expertise. They’ve built an impressive platform, and given their track record, I’m confident they’ll implement the best approach for a seamless transition.

                  xyzulu From what I understand, backing up backups isn’t effective. I checked with Adam on this, and he confirmed there’s no real benefit to it. Enhance won’t recognize backups restored this way if you try to set up a new backup server to replace a failed one. Please let me know if I’ve misunderstood anything.

                  • Rich replied to this.

                      ivansalloum It might not export back to the backup server, which your correct being BTRFS snapshot based... however, having a full copy elsewhere is a mitigation strategy. There's nothing stopping you manually extracting the archives you've taken, rsyncing them to the app server and letting the backups resume as normal again.

                      This of course suggests both app server failed and backup server failed and your using your 3rd copy to recover from.

                      That said it could also be for long term storage, enhance backups have a limit before there recycled. You might need to recover an email that was in someones inbox from 6 months ago, that no longer lives on the email server, or within the backups that are shorter than that.

                        DracoBlue Watch out for Wasabis 'Time deleted storage' terms. They charge to delete storage... Advertise $6usd per 1TB, but charge $30usd to delete retention backups......

                            DracoBlue I moved to storj.io, and the prices are much better.

                            Their pricing is 4$ / 1 TB just to store it, and if you want to download it, it will cost you 7$ / 1 TB !?
                            I don't get it. isn't this more expensive ?

                                adil Wasabi rounds it up to 1TB, even if you don't use it all. Storj charges based on actual usage. I was paying $7 for Wasabi, while for Storj, I’m paying $1.

                                    DracoBlue
                                    I see, so you are not storing much, Yes indeed it will be cheaper on Storj.

                                        DracoBlue Wasabi makes you pay that extra storing fee even when you delete files. So i got rid of it. My backups were going upto 5TB because of this.. 🙁

                                          So is there any update to the roadmap? any delays? are we still due for this month?

                                            Follow @enhancecp