tatter / firebase
Firebase integration for CodeIgniter 4
Fund package maintenance!
tattersoftware
paypal.me/tatter
Installs: 6 581
Dependents: 0
Suggesters: 0
Security: 0
Stars: 28
Watchers: 3
Forks: 8
Open Issues: 2
Requires
- php: ^7.4 || ^8.0
- google/cloud-firestore: ^1.10
- google/protobuf: ^3.3
- grpc/grpc: ^1.1
- kreait/firebase-php: ^5.0 || ^6.0
Requires (Dev)
- codeigniter4/framework: ^4.1.0
- tatter/tools: ^2.0
- dev-develop
- v2.x-dev
- v2.0.0-rc.2
- v2.0.0-rc.1
- v2.0.0-beta.4
- v2.0.0-beta.3
- v2.0.0-beta.2
- v2.0.0-beta.1
- v1.4.0
- v1.3.0
- v1.2.2
- v1.2.1
- v1.2
- v1.1.2
- v1.1.1
- v1.1.0
- v1.0.12
- v1.0.11
- v1.0.10
- v1.0.9
- v1.0.8
- v1.0.7
- v1.0.6
- v1.0.5
- v1.0.4
- v1.0.3
- v1.0.2
- v1.0.1
- v1.0.0
- dev-dependabot/github_actions/actions/cache-4
- dev-dependabot/github_actions/actions/setup-node-4
- dev-master
- dev-database
This package is auto-updated.
Last update: 2024-11-18 00:54:37 UTC
README
Firebase integration for CodeIgniter 4
Quick Start
- Install with Composer:
> composer require tatter/firebase
- Edit .env and add the path to your Firebase credentials:
GOOGLE_APPLICATION_CREDENTIALS = ../credentials/keyfile.json
- Access components via the service:
$authentication = service('firebase')->auth;
- Use the Firestore
Collection
andEntity
to model your data:$widget = collection(WidgetCollection::class)->get($widgetId);
Description
This is a CodeIgniter 4 integration of Kreait\Firebase
, the "Unofficial Firebase Admin
SDK for PHP":
It provides a convenience service and custom Firestore classes to use your Firebase project within CodeIgniter 4. Please pay attention to the requirements of the underlying services:
Notably, you must have the gRPC PHP extension and the credentials file to a Service Account with the Project -> Editor or Project -> Owner role.
Installation
Install easily via Composer to take advantage of CodeIgniter 4's autoloading capabilities and always be up-to-date:
composer require tatter/firebase
Or, install manually by downloading the source files and adding the directory to app/Config/Autoload.php.
Note: As of February 5, 2022 this library fully supports PHP 8.1, however Google's Protobuf has an incompatibility (hopefully fixed soon: protocolbuffers/protobuf#9293).
Credentials
You must provide a key file with your application's service account credentials. The standard way to do this is to add keyfile.json to your project and edit .env to its path (relative to public/):
GOOGLE_APPLICATION_CREDENTIALS = ../keyfile.json
WARNING Make sure you exclude the key file from any repository updates!
To generate a key file from your Firebase project:
- Firebase Project Home
- Project Settings (gear)
- Service Accounts
- Firebase Admin SDK
- Generate new private key
For more info on acquiring credentials see the Firestore Quick Start Guide
For more information on credential specification see the SDK setup docs
Usage
Load the Firebase service:
$firebase = service('firebase');
The service will handle creating and caching each component as you need them. Access components by their name:
$storage = $firebase->storage; $bucket = $storage->getBucket('my-bucket');
You can also use the service to access all the functions of Kreait\Firebase\Factory
directly, for example if you wanted a separate component instance:
$shareClient = $firebase->auth; $altClient = $firebase->createAuth();
See the SDK docs for a list of supported components. Available at the time of this writing:
- Auth
- Database
- Firestore
- Messaging
- RemoteConfig
- Storage
- Caller
Caller
While not yet officially supported by the Firebase SDK, this library includes a component for Firebase callable functions. A simple example shows all its features:
// Get the component $caller = service('firebase')->caller; // Set the UID of the user making the call $caller->setUid($user->uid); // Make the call $data = ['customerId' => 7, 'charge' => 3.50]; $response = $caller->call('https://us-central1-myproject.cloudfunctions.net/addCharge', $data); if ($response === null) { echo implode(' ', $caller->getErrors()); } else { print_r($response); }
Firestore
This library provides access to the Firestore database directly via FirestoreClient
.
Use the helper function for direct access to a shared instance of the client:
helper('firestore'); $document = firestore()->collection('users')->document('lovelace'); $document->set([ 'first' => 'Ada', 'last' => 'Lovelace', 'born' => 1815 ]); printf('Added data to the "lovelace" document in the users collection.');
Since the SDK and Google classes already represent a full database implementation there is no need for a framework database layer. You can interact directly with the Firestore classes according to Google's User Guide.
Collection
The Collection
class is inspired by the framework's Model
and handles most of the pre-
and post-processing that developers are used to. All you need to supply is the name of the
collection and the Entity type to use:
<?php namespace App\Collections; use App\Entities\Widget; use Tatter\Firebase\Firestore\Collection; final class WidgetCollection extends Collection { public const NAME = 'widgets'; public const ENTITY = Widget::class; }
Instantiating
You can create your collection instances just like you would a Model
. The Firestore
Helper also contains a helper function to create and manage shared instances, just like
the framework's model()
helper:
$widgets = new WidgetCollection();
// OR
helper('firestore');
$widgets = collection(WidgetCollection::class);
By default a new Collection will create a CollectionReference
to the top-level collection
matching it's NAME
constant. Alternatively you may pass in a CollectionReference
directly
for it to use. Use the second parameter to the collection()
function to make instant
subcollections of any Firestore\Entity
or DocumentReference
:
$user = collection(UserCollection::class)->get($userId); $userWidgets = collection(WidgetCollection::class, $user); foreach ($userWidgets->list() as $widget) { echo "{$user->name}: {$widget->name}"; }
Methods
Collection
supplies the following CRUD methods:
add(array|Entity $entity): Entity
update(Entity $entity, array $data): Entity
remove(Entity|string $entity): void
get(DocumentReference|string $reference): ?Entity
list($source = null): Traversable
Read more below
And support methods:
fromSnapshot(DocumentSnapshot $snapshot): Entity
fake(array<string, mixed> array $overrides = []): Entity
make(array<string, mixed> array $overrides = []): Entity
*Same asfake()
but inserts the document
Additionally, these methods access metadata about the underlying Firestore (sub)collection:
collection(): CollectionReference
parent(): ?DocumentReference
id(): string
name(): string
path(): string
And finally some familiar Model
-inspired validation methods:
setValidation(ValidationInterface $validation): self
skipValidation(bool $skip = true)
validate(array $data, bool $cleanValidationRules = true): bool
getValidationRules(array $options = []): array
getErrors(): array
Retrieving Documents
You may use the Firestore client directly to return snapshots and convert them to your Entity
of choice with fromSnapshot()
, but Collection
also allows specifying an overriding state
for list()
. This can be an explicit CollectionReference
or (more helpful) an instance of
Google\Cloud\Firestore\Query
, which opens up the possibility of using filters, sorts, and
limits as well as traversing collection groups:
// Using filters $widgets = new WidgetCollection(); $query = $widgets->collection()->where('color', '=', 'purple'); // returns Query foreach ($widgets->list($query) as $widget) { echo $widget->weight; } // Grouped collections (traverses all collections and subcollections named "widgets") $group = firestore()->collectionGroup('widgets'); foreach ($widgets->list($group) as $widget) { echo $widget->color; }
To make this even easier, Collection
will "pass through" the following method calls to
the underlying collection:
endAt()
,endBefore()
,limit()
,limitToLast()
,offset()
,orderBy()
,select()
,startAfter()
,startAt()
,where()
This allows for even easier method chaining:
$result = $widgets->list($widgets->orderBy('color')->limit(5));
Note that
list()
always returns aTraversable
so documents are only retrieved and converted ot Entities as they are actually needed
Entity
This library also comes with its own Firestore Entity
that handles Google's timestamp
conversions and these methods to access metadata about the underlying Firestore document:
document(?DocumentReference $document = null): ?DocumentReference
Gets or sets the documentid(): string
super(): ?DocumentReference
Gets an Entity's parent Entity, if it is from a subcollection