Changelog_

Appwrite Sites can now deploy server-rendered apps straight from a monorepo. Sites build from the root of the repository and deploy just the app they're set up for, together with the shared packages it imports, while the other apps in the repo stay out.

• npm, pnpm, and Bun workspaces are all supported.
• It works with every JavaScript SSR framework: Next.js, Nuxt, Astro, SvelteKit, Remix, TanStack Start, Angular, and Analog.
• Next.js standalone output works inside a monorepo too.

Monorepo support is available on Appwrite Cloud today.

Appwrite Sites and Functions now stream their responses. Each chunk your code writes reaches the browser as soon as it is produced, so server-rendered pages show their ready parts first and AI output appears while the model is still writing.

• Server-rendered sites stream with no configuration. Frameworks that stream HTML, such as Next.js with Suspense, send the page shell first and fill in slower sections as their data loads.
• Functions stream their response when they return res.sendStream().
• Streamed responses are still compressed with gzip or Brotli when the browser supports it.

Appwrite Push is a new push provider in Appwrite Messaging. It sends notifications to your apps straight from Appwrite, so you don't need a Firebase project or your users' device tokens.

With Appwrite Push:

• You create the provider in the Console without any credentials.
• Your app subscribes with the Appwrite SDK after the user signs in.
• A message you send to a user reaches every device they're signed in on. If the user also has FCM or APNs targets, register an Appwrite push target on one of their devices.
• Devices that were offline get the messages they missed when they reconnect, for up to 7 days.
• On Android, messages arrive even while the app is closed. On iOS, Appwrite Push works with APNs to show messages while the app is suspended.

Appwrite Push works with the Web, Flutter, React Native, Android, and Apple SDKs, and you send messages the same way you send them through FCM or APNs.

Run appwrite init apns in your iOS project and the Appwrite CLI sets up push notifications in one command. It:

• Creates the production and sandbox APNs providers.
• Adds the push entitlement and background mode to your Xcode target.
• Adds an Apple platform for your bundle ID.
• Checks with Apple that your App ID has Push Notifications on.
• Creates the APNs key for you with --create-key, so you can skip the Apple Developer portal.

The CLI reads the bundle ID, team ID, and key ID from your project, so there's nothing to copy by hand, and you can safely run the command again at any time.

Appwrite 2.7.1 is now available for self-hosting. This is a security release for the 2.7 line with several security fixes, including the fix for the runtime vulnerability described in our November 1st incident report. We strongly recommend upgrading your instance.

Upgrading from 2.7.0 only replaces the images. Read the upgrade notes before you upgrade.