appwrite-php

Implements server-side Appwrite integrations in PHP covering users, databases, storage, and functions.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/aadilmallick/myfitness-pal-clone --skill appwrite-php-aadilmallick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: appwrite-php
Source: https://github.com/aadilmallick/myfitness-pal-clone/tree/main/.agents/skills/appwrite-php
Command: npx skills add https://github.com/aadilmallick/myfitness-pal-clone --skill appwrite-php-aadilmallick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires appwrite/appwrite.

What problem does it solve? Building server-side PHP applications with Appwrite requires knowing the correct SDK patterns for authentication, database operations, file storage, and permissions, and mistakes like using deprecated classes or missing permission strings cause broken or insecure backends. ## Core Features & Use Cases - Full SDK Coverage: Provides working PHP examples for user management, TablesDB CRUD, file storage, teams, and serverless function execution via API keys. - SSR Authentication Patterns: Implements admin and session client separation for Laravel and Symfony apps, including email/password login, OAuth2 flows, and secure cookie handling. - Permissions & Error Handling: Documents the Permission and Role helper model, common HTTP error codes, and AppwriteException handling to prevent inaccessible resources. - Use Case: A developer building a Laravel backend can use this Skill to create users, query rows with filters, upload files with per-user permissions, and manage session cookies correctly on the first attempt. ## Quick Start Ask the AI to write PHP code using the Appwrite SDK to create a database table and insert a row with user-specific read permissions.

Frequently Asked Questions about appwrite-php

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use the Appwrite PHP SDK for server-side apps?

Install it with composer require appwrite/appwrite, then configure a Client with your endpoint, project ID, and API key. From there you instantiate services like Users, TablesDB, Storage, and Functions to perform backend operations.

How to query rows in Appwrite TablesDB with PHP?

Use the TablesDB service with Query helper methods such as Query::equal, Query::greaterThan, Query::orderDesc, and Query::limit. Pass an array of queries to listRows along with the database and table IDs to filter, sort, and paginate results.

Should I use Databases or TablesDB in the Appwrite PHP SDK?

Use TablesDB for all new code, since the Databases class is deprecated. Only use Databases when maintaining an existing codebase that already relies on it or when explicitly required.

How does Appwrite SSR authentication work in Laravel or Symfony?

SSR auth uses two clients: an admin client with an API key that creates sessions, and a per-request session client that reads the a_session_<PROJECT_ID> cookie. Set the cookie with httpOnly, secure, and sameSite strict flags after creating the session.

Why is my Appwrite resource inaccessible after creation?

Appwrite grants no access by default, so resources without explicit permissions are inaccessible to everyone including the creator. Pass Permission and Role strings, such as Permission::read(Role::user($userId)), when creating rows or files.

What string column types does Appwrite TablesDB support?

Appwrite supports varchar, text, mediumtext, and longtext column types, replacing the deprecated generic string type. Varchar is stored inline and fully indexable up to 768 bytes, while the text variants are stored off-page and support prefix indexing only.