Book Image

Firebase Cookbook

By : Houssem Yahiaoui
Book Image

Firebase Cookbook

By: Houssem Yahiaoui

Overview of this book

Do you feel tired just thinking or even hearing about backend technologies, authentication or the tedious task of deployment? Firebase is here to change the way you develop and make your app a first-class citizen of the cloud. This books takes a solution based approach by providing you recipes that would help you understand the features of Firebase and implement them in your existing web or mobile applications. We start-off by creating our first Firebase application and integrating its services into different platforms and environments for mobile as well as web applications. Then we deep dive into Real-time Database and Firebase Storage that allows your users to access data across various devices with realtive ease. With each chapter you will gradually create the building blocks of your application from securing your data with Firebase Rules to authenticating your users with O-Auth. Moving along we would explore modern application development techniques such as creating serverless applications with Firebase Cloud Functions or turning your traditional applications into progressive apps with Service workers. Finally you will learn how to create cross-platform mobile apps, integrate Firebase in native platforms, and learn how to monetize your mobile applications using Admob for Android and iOS.
Table of Contents (15 chapters)
Firebase Cloud FireStore

Configuring storage files security rules

File upload service or Firebase Storage service security is highly essential, which means that we don't want any security breaches that can simply delete our file storage or jeopardize the good presence of our files. In this recipe, we're going to see how we can implement/configure our storage security.

Getting ready

In order to secure the Firebase Cloud files, we will need to use the Firebase security rules for Cloud Storage, those rules will be declared to maintain who has access to what, also those rules will define how data is structured and how metadata is saved.

This means that we're going to use a different language then the Bolt one. Also, for these rules to work...