Firebase Auth & Realtime Database Apps · Pelajaran

Memahami Sintaks Aturan Keamanan

Pahami sintaks dan struktur Firebase Realtime Database Security Rules untuk menentukan izin akses.

Memahami Sintaks Aturan Keamanan adalah pelajaran Firebase Auth & Realtime Database Apps gratis di CoddyKit. Ini adalah pelajaran 1 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Firebase Auth & Realtime Database Apps, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Firebase Auth & Realtime Database Apps mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

Why Security Rules?

Welcome to Realtime Database Security Rules! These rules are super important for keeping your data safe and controlling who can do what in your Firebase app.

Think of them as bouncers for your database: they check every request to read, write, or update data, and decide if it's allowed or not.

Your Rules File

Firebase Realtime Database Security Rules are defined in a JSON file, usually named rules.json. You'll upload this file to your Firebase project.

The entire set of rules is wrapped under a top-level "rules" key, like this:

{
  "rules": {
    // Your security rules go here!
  }
}

Default Open Rules

When you first create a Realtime Database, Firebase often provides a very open set of rules. This allows anyone to read and write data, which is great for getting started quickly, but terrible for production!

These rules look like this:

{
  "rules": {
    ".read": "true",
    ".write": "true"
  }
}

Targeting Data Paths

Rules are applied based on the path to your data. You nest rules within the "rules" object to target specific parts of your database, just like folders in a file system.

For example, to set rules for /users or /messages:

{
  "rules": {
    "users": {
      // Rules for data under /users
    },
    "messages": {
      // Rules for data under /messages
    }
  }
}

Basic Read Permissions

The ".read" rule determines who can retrieve data from a specific path. If a read request matches a path with ".read": "true", it's allowed. If it's "false", it's denied.

Here's how you might set read permissions:

{
  "rules": {
    "publicPosts": {
      ".read": "true" // Anyone can read blog posts
    },
    "secretDocs": {
      ".read": "false" // No one can read secret documents
    }
  }
}

Basic Write Permissions

Similarly, the ".write" rule controls who can create, update, or delete data at a given path. Setting it to "true" allows writes, and "false" denies them.

Let's look at some write rule examples:

{
  "rules": {
    "guestbook": {
      ".write": "true" // Anyone can sign the guestbook
    },
    "adminSettings": {
      ".write": "false" // No one can change admin settings yet
    }
  }
}

Combining Read & Write

You can define both ".read" and ".write" rules for the same path. Firebase evaluates them independently.

For example, to make a path readable by everyone but writable by no one (yet):

{
  "rules": {
    "announcements": {
      ".read": "true",  // Everyone can see announcements
      ".write": "false" // No one can post new announcements
    }
  }
}

Dynamic Paths with Wildcards

What if you have many items under a path, like individual user profiles (/users/user123, /users/user456)? You don't want to write a rule for each one!

Use a wildcard variable, prefixed with $, to match any child node. This variable can then be used within the rule itself.

{
  "rules": {
    "profileData": {
      "$userId": {
        ".read": "true",  // Anyone can read any user's profile
        ".write": "false" // But no one can edit them yet
      }
    }
  }
}

`auth` & `data`: Rule Helpers

When writing more advanced rules, you'll often need to check who is making the request or what data already exists. Firebase provides special variables for this:

auth: Contains information about the currently authenticated user (if any).
data: Refers to the data that already exists at the path being accessed.
newData: Refers to the data being written (only for write/validate rules).

These let you create smart rules, like "only the owner can edit their profile." We'll dive into these in upcoming lessons!

Syntax Check

Given the Firebase Realtime Database Security Rules below, which statement is true?

{
  "rules": {
    "posts": {
      ".read": "true",
      "comments": {
        ".write": "false"
      }
    },
    "users": {
      "$userId": {
        ".read": "true"
      }
    }
  }
}

Lesson Summary

Great job! In this lesson, we covered the foundational syntax of Firebase Realtime Database Security Rules:

Rules live in a rules.json file.
Rules are nested to target specific data paths.
".read" and ".write" control read and write access.
Wildcards ($variable) make rules dynamic for child nodes.
You got a sneak peek at context variables like auth and data.

Next, we'll dive deeper into using these rules for user-based access control!

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Memahami Sintaks Aturan Keamanan” gratis?

Ya — teks lengkap “Memahami Sintaks Aturan Keamanan” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Firebase Auth & Realtime Database Apps, upgrade ke CoddyKit PRO. Kursus Firebase Auth & Realtime Database Apps mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Memahami Sintaks Aturan Keamanan”?

Pahami sintaks dan struktur Firebase Realtime Database Security Rules untuk menentukan izin akses. Kamu berlatih Firebase Auth & Realtime Database Apps dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Firebase Auth & Realtime Database Apps?

Tidak diperlukan pengalaman sebelumnya. Firebase Auth & Realtime Database Apps di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 1 dari 4.

Berapa lama pelajaran “Memahami Sintaks Aturan Keamanan” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Firebase Auth & Realtime Database Apps ini?

Ya. Setiap pelajaran Firebase Auth & Realtime Database Apps menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

← Kembali ke Firebase Auth & Realtime Database Apps