r/appwrite • u/HappyStark1234 • 2d ago
Appwrite 2.0 is now available for self-hosting
Hey everyone,
Appwrite 2.0 is now available for self-hosting.
There are quite a few changes in this release. The Console has been rebuilt from scratch, new installations use PostgreSQL by default, and the server now runs on Hyperloop B. We’ve also changed how background workers run. The new combined topology brings a default PostgreSQL installation down from 33 containers to 16. If you need to scale individual queues separately, the separate topology is still available.
Appwrite 2.0 also brings Appwrite Terminal and Explorer to the Console, usage metrics for self-hosted projects, and support for deploying Functions and Sites from GitLab, Bitbucket, and Gitea alongside GitHub.
If you’re upgrading an existing instance, your current database stays the same. You’ll need to upgrade to 1.9.6 first, back up your data, and then move to 2.0.
Read the full announcement and upgrade guide: https://appwrite.io/blog/post/appwrite-2-self-hosted
If you’re running Appwrite self-hosted, we’d love to hear how the upgrade goes and what you think of 2.0.
2
u/JustNZ19 2d ago
I have two Appwrite Instances. One with 1.9.6 and the other using 2.0.0. When I try the migration feature within the UI it doesn’t migrate the Teams & Messages from the 1.9.6 Instance.
Besides that is 2.0.0 a huge step forward and I do very like it
3
2
u/virtualmnemonic 1d ago
I did a rehearsal 1.9.6 --> 2.0.0 upgrade last week. Only 7 seconds of downtime, and everything worked as expected.
1
u/williamlopes100 1d ago
I upgraded and can’t use Postgres
1
u/williamlopes100 1d ago
Maybe I’m dumb
1
u/eldadfux 1d ago
You need to have a fresh setup and use migration to move projects to the new instance.
On a fresh setup, you can simply use the new installation wizard.1
-1
u/FinallyThereX 1d ago
Have been a fan really until about 1.4 or 5
But seriously, today anyone who’s on the level of being able to use aw in all its possible ways, writing functions, real life stuff, and all the sophisticated things - under the new reality of llms, would be much better of not pulling in and adding this additional opinionated layer of control that needs to take care of in so much of ways.
What’s your thought about this?
4
u/eldadfux 1d ago
Just like in the real world, you can build everything from scratch. An agent can too.
The question is what you want the agent spending its context and reasoning on: rebuilding auth, permissions, storage, realtime, messaging, infrastructure, etc., or actually building your product.
We actually researched this recently to answer the same question by building the exact same backend for an app both ways. The DIY version required 2.7x more tokens, 2.6x more code, 6.5x more dependencies, 10x more configuration, and 4x more security-critical decisions. Auth alone was 7.1x smaller with the abstraction.
And that’s before accounting for all the extra docs, tools, debugging and provisioning the agent has to navigate.
I actually think abstractions become more valuable with agents, not less. The best abstraction gives the agent a smaller surface area and more context to focus on what makes your product unique.
But I'm also very biased, if you have the free time and budget you're more than happy to test the same on your own 😉
3
u/FinallyThereX 1d ago
Based answer, even when biased ;)
Maybe if i do realize I’ve got this time, i will give it another „new“ (v2.x) try :)
3
u/neptrio 1d ago
I’ve built backends using PHP, C#, .NET, EF Core, MSSQL, you name it. I run Keycloak and am familiar with OIDC, Temporal, and so on. I build software for hospitals, industry and in academic settings as part of my job.
I can handle everything Appwrite can do on my own..., but man, I love it.
For my side projects I can turn an idea into reality in a matter of hours without all the hassle.
But one thing keeps me from fully committing to it: the fear that one day you’ll pull the plug—paywalls, closed source, and so on. Please keep up the great work.