> For the complete documentation index, see [llms.txt](https://faisalaffan.gitbook.io/design-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faisalaffan.gitbook.io/design-system/id/06-penyimpanan/google-drive.md).

# Google Drive

Hierarki file dan folder dengan riwayat versi immutable dan izin berbagi tingkat pengguna.

Port **8090** | Paket `google-drive/`

***

## Arsitektur

```mermaid
%%{init: {"theme": "base", "themeVariables": {"background": "#ffffff"}}}%%
sequenceDiagram
    participant Client
    participant Handler as DriveHandler
    participant Store as MemoryStore
    participant Versions as Version History
    
    Client->>Handler: POST /files?name=doc.txt&owner_id=alice
    Handler->>Store: CreateFile(name, mime, parent, owner, content)
    Store->>Store: Create File metadata
    Store->>Versions: Append v1 (content)
    Store-->>Handler: File
    Handler-->>Client: {file: {id: "file_1", ...}}
    
    Client->>Handler: PUT /files/file_1 (raw body: new content)
    Handler->>Store: UpdateFile(id, newContent)
    Store->>Versions: Append v2 (new content, previous preserved)
    Store-->>Handler: File (updated_at refreshed)
    Handler-->>Client: {file: {id: "file_1", ...}}
    
    Client->>Handler: GET /files/file_1/versions
    Handler->>Store: GetFileVersions(id)
    Store-->>Handler: [v1, v2]
    Handler-->>Client: {versions: [{version: 1, ...}, {version: 2, ...}]}
    
    Client->>Handler: POST /files/file_1/share
    Handler->>Store: ShareFile(id, user, permission)
    Store->>Store: f.SharedWith[user] = permission
    Handler-->>Client: {shared: true}
    
    Client->>Handler: GET /folders/folder_1/children
    Handler->>Store: GetFolderChildren(id)
    Store->>Store: Lookup child file/folder IDs
    Store-->>Handler: [files[], folders[]]
    Handler-->>Client: {children: [...]}
```

### Riwayat Versi Immutable

Setiap pembaruan file menambahkan versi baru alih-alih menimpa. Seluruh riwayat dipertahankan dan dapat ditanyakan:

```go
type FileVersion struct {
    Version   int    `json:"version"`
    Content   []byte `json:"content"`
    Size      int64  `json:"size"`
    CreatedAt int64  `json:"created_at"`
}
```

```go
func (s *MemoryStore) UpdateFile(id string, content []byte) (*File, error) {
    f, ok := s.files[id]
    if !ok {
        return nil, fmt.Errorf("file not found")
    }

    versions := s.fileData[id]
    newVersion := len(versions) + 1
    s.fileData[id] = append(versions, &FileVersion{
        Version:   newVersion,
        Content:   content,
        Size:      int64(len(content)),
        CreatedAt: time.Now().UnixMilli(),
    })

    f.Size = int64(len(content))
    f.UpdatedAt = time.Now().UnixMilli()
    return f, nil
}
```

### Hirarki Folder

File dan folder membentuk pohon melalui `parentID`. Map `folderChildren` melacak keanggotaan anak untuk pencatatan yang efisien:

```go
type Folder struct {
    ID        string `json:"id"`
    Name      string `json:"name"`
    ParentID  string `json:"parent_id"`
    OwnerID   string `json:"owner_id"`
    CreatedAt int64  `json:"created_at"`
}
```

```go
func (s *MemoryStore) GetFolderChildren(folderID string) []interface{} {
    var children []interface{}
    for _, childID := range s.folderChildren[folderID] {
        if f, ok := s.files[childID]; ok {
            children = append(children, f)
        } else if f, ok := s.folders[childID]; ok {
            children = append(children, f)
        }
    }
    return children
}
```

### Izin Berbagi

```go
func (s *MemoryStore) ShareFile(fileID, userID, permission string) error {
    f, ok := s.files[fileID]
    if !ok {
        return fmt.Errorf("file not found")
    }
    f.SharedWith[userID] = permission
    return nil
}
```

***

## API Endpoints

| Method   | Path                                   | Deskripsi                                                 |
| -------- | -------------------------------------- | --------------------------------------------------------- |
| `POST`   | `/files?name=N&owner_id=O&parent_id=P` | Membuat file baru (body: raw content atau multipart)      |
| `GET`    | `/files/:id`                           | Mendapatkan metadata file dan ukuran konten               |
| `GET`    | `/files/:id/download`                  | Mengunduh konten file mentah                              |
| `PUT`    | `/files/:id`                           | Memperbarui konten file (menambahkan versi baru)          |
| `DELETE` | `/files/:id`                           | Menghapus file dan semua versi                            |
| `GET`    | `/files/:id/versions`                  | Mendaftar semua versi file                                |
| `POST`   | `/files/:id/share`                     | Berbagi file dengan pengguna (body: user\_id, permission) |
| `POST`   | `/folders`                             | Membuat folder (body: name, owner\_id, parent\_id)        |
| `GET`    | `/folders/:id/children`                | Mendaftar file dan sub-folder dalam folder                |

### POST /files/:id/share

```json
{
    "user_id": "bob",
    "permission": "read"
}
```

Nilai izin: `"read"` atau `"write"`.

### POST /folders

```json
{
    "name": "Documents",
    "owner_id": "alice",
    "parent_id": ""
}
```

### GET /folders/:id/children

```json
{
    "children": [
        {"id": "file_1", "name": "doc.txt", "mime_type": "text/plain", ...},
        {"id": "folder_2", "name": "Photos", ...}
    ]
}
```

***

## Keputusan Teknis

### Riwayat Versi Immutable

Setiap `PUT /files/:id` menambahkan `FileVersion` baru daripada mengubah yang sebelumnya. Ini berarti:

* **Jejak audit lengkap**: semua konten sebelumnya dapat dipulihkan.
* **Time travel**: klien dapat mengambil versi historis mana pun.
* **Biaya penyimpanan**: tumbuh secara linear dengan jumlah pembaruan. Sistem produksi akan menambahkan kebijakan kompaksi atau batas retensi.

### Unifikasi File dan Folder

Handler mengembalikan file dan folder dari `GetFolderChildren`. Secara internal mereka disimpan dalam map terpisah, tetapi API menyajikan tampilan terpadu -- mirip dengan cara Google Drive memperlakukan folder sebagai tipe file khusus.

### Model Izin

Izin disimpan sebagai `map[string]string` pada setiap file (`userID -> "read"|"write"`). Ini adalah daftar kontrol akses (ACL) datar. Sistem produksi menambahkan:

* **Warisan**: anak mewarisi izin folder induk.
* **Grup**: izin ditetapkan ke grup daripada pengguna individu.
* **Hapus khusus pemilik**: hanya pemilik file yang dapat menghapus.

### Penyimpanan Konten

Konten file dan metadata disimpan secara terpisah. Map `fileData` menyimpan konten berversi sementara map `files` menyimpan metadata. Dalam produksi, konten akan disimpan di object store (S3, GCS) dengan metadata di basis data relasional.

***

## File Kunci

| File                 | Tujuan                                                        |
| -------------------- | ------------------------------------------------------------- |
| `store/store.go`     | Model File, Folder, FileVersion; CRUD; riwayat versi; berbagi |
| `handler/handler.go` | HTTP handlers untuk file, folder, versi, berbagi, unduh       |

## Source Code

[View on GitHub](https://github.com/faisalaffan/faisalaffan-design-system/blob/dev/services/google-drive/main.go)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://faisalaffan.gitbook.io/design-system/id/06-penyimpanan/google-drive.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.