fix: merge missing changes on GCS

Author: axelmarciano

README.md

@@ -40,30 +40,35 @@
 
 [![Deploy on Railway](https://railway.com/button.svg)](https://railway.com/deploy/MGW3k1?referralCode=OEHlEK&utm_medium=integration&utm_source=template&utm_campaign=generic)
 
-🚀 **An open-source Go implementation of the Expo Updates protocol, designed for production with support for cloud storage like S3 and CDN integration, delivering fast and reliable OTA updates for React Native apps.**
+Or with Docker:
 
-## ⚠️ Disclaimer
+```bash
+docker run -p 3000:3000 \
+  -e STORAGE_MODE=s3 \
+  -e S3_BUCKET_NAME=my-bucket \
+  -e AWS_REGION=us-east-1 \
+  axelmarciano/expo-open-ota
+```
 
-**Expo Open OTA is not officially supported or affiliated with [Expo](https://expo.dev/).**  
-This is an independent open-source project.
+Then configure your Expo app to point to your server — see the [full documentation](https://axelmarciano.github.io/expo-open-ota/).
 
-## 📖 Documentation
+## Storage Options
 
-The full documentation is available at:  
-➡️ [Documentation](https://axelmarciano.github.io/expo-open-ota/)
+| Provider | Mode | Asset Delivery |
+|----------|------|----------------|
+| **Amazon S3** | `STORAGE_MODE=s3` | Direct or CloudFront CDN |
+| **Google Cloud Storage** | `STORAGE_MODE=gcs` | GCS signed URLs |
+| **S3-compatible** (R2, MinIO, etc.) | `STORAGE_MODE=s3` + `AWS_BASE_ENDPOINT` | Direct |
+| **Local file system** | `STORAGE_MODE=local` | Direct (dev only) |
 
-## 🛠 Features
+## Disclaimer
 
-- **Self-hosted OTA update server** for Expo applications.
-- **Cloud storage support**: AWS S3, local storage, and more.
-- **CDN integration**: Optimized for CloudFront and other CDN providers.
-- **Secure key management**: Supports AWS Secrets Manager and environment-based key storage.
-- **Production-ready**: Designed for scalability and performance.
+Expo Open OTA is **not officially supported or affiliated with [Expo](https://expo.dev/)**. This is an independent open-source project.
 
-## 📜 License
+## License
 
-This project is licensed under the MIT License - see the [LICENSE](./LICENSE.md) file for details.
+MIT — see [LICENSE](./LICENSE.md).
 
 ## Contact
 
-✉️ [E-mail](mailto:expoopenota@gmail.com)
+[expoopenota@gmail.com](mailto:expoopenota@gmail.com)

apps/docs/docs/getting-started/introduction.mdx

@@ -4,7 +4,7 @@ sidebar_position: 1
 
 # Introduction
 
-**Expo Open OTA** is an open-source project that allows you to host your own updates server for your Expo application. It is a self-hosted alternative to the official Expo OTA service, implementing the [Expo Updates protocol](https://docs.expo.dev/technical-specs/expo-updates-1/).
+**Expo Open OTA** is an open-source, multi-cloud OTA update server for Expo and React Native applications. It implements the [Expo Updates protocol](https://docs.expo.dev/technical-specs/expo-updates-1/) and supports **AWS S3**, **Google Cloud Storage**, and any **S3-compatible** provider (Cloudflare R2, MinIO, DigitalOcean Spaces).
 
 :::warning
 **Expo Open OTA** is not affiliated with Expo. It is an independent open-source project.
@@ -30,10 +30,10 @@ When an update is available, a list of assets is sent back to the client. These
 - Signs and compresses the files.
 - Returns the required assets to the Expo client.
 
-If a CDN is configured, the returned URL is a pre-signed link pointing to a cdn endpoint. Otherwise, the server returns the asset directly.
+If a CDN is configured (CloudFront) or if using GCS, the returned URL is a pre-signed/signed link and the client downloads directly from the storage provider. Otherwise, the server returns the asset directly.
 
 ### 3. `/requestUploadUrl` & `/uploadLocalFile`
-These routes are used by the `eoas` package to publish updates to the chosen storage solution, whether it's S3 or a local file system.
+These routes are used by the `eoas` package to publish updates to the chosen storage solution, whether it's S3, Google Cloud Storage, or a local file system.
 `/uploadLocalFile` is used to upload the file to the server when [storage mode](/docs/server-configuration/storage?storage=local) is set to `local`.
 
 ## Why Self-Host Your OTA Update server?

apps/docs/docs/server-configuration/storage.mdx

@@ -74,13 +74,41 @@ import TabItem from '@theme/TabItem';
     ```bash title=".env"
     STORAGE_MODE=gcs
     GCS_BUCKET_NAME=your-bucket-name
+    GOOGLE_APPLICATION_CREDENTIALS_B64=<base64-encoded service account JSON>
     ```
 
-    To generate signed URLs for uploads and asset redirects, provide your service account credentials as a base64-encoded JSON:
-    ```bash title=".env"
-    GOOGLE_APPLICATION_CREDENTIALS_B64=<base64-encoded service account JSON>
+    #### Setting up GCP credentials
+
+    1. In the GCP Console, go to **IAM & Admin > Service Accounts**
+    2. Create a new service account (or use an existing one)
+    3. Go to your bucket in **Cloud Storage > Buckets**, open the **Permissions** tab
+    4. Click **Grant Access**, add your service account with the **Storage Admin** role
+    5. Back in Service Accounts, go to **Keys > Add Key > Create new key > JSON**
+    6. Encode the downloaded JSON file to base64:
+
+    ```bash
+    base64 -i /path/to/service-account.json | tr -d '\n'
     ```
 
-    The service account must have at minimum `storage.objectCreator` and `storage.objectAdmin` permissions on your bucket. You don't need to make objects public — the server generates short-lived signed URLs for all file access.
+    7. Set the output as `GOOGLE_APPLICATION_CREDENTIALS_B64` in your `.env`
+
+    :::tip
+    The base64 credential is used both for authenticating API calls (read, write, delete objects) and for generating signed URLs.
+    :::
+
+    #### How asset delivery works
+
+    Unlike S3 where you can optionally configure CloudFront as a CDN, GCS uses **direct signed URLs** for asset delivery. When a client requests an update asset, the server generates a short-lived signed URL (15 minutes) and redirects the client to download the file directly from GCS — the server never proxies the file content itself.
+
+    This is automatic when `GOOGLE_APPLICATION_CREDENTIALS_B64` is set. No additional CDN configuration is needed.
+
+    #### Permissions
+
+    The service account needs at minimum the **Storage Admin** role on your bucket. This covers:
+    - `storage.objects.get` — reading objects
+    - `storage.objects.list` — listing branches, runtime versions, and updates
+    - `storage.objects.create` — uploading new updates
+    - `storage.objects.delete` — removing updates
+    - Signed URL generation for asset delivery
   </TabItem>
 </Tabs>

apps/docs/docusaurus.config.ts

@@ -7,7 +7,7 @@ import type * as Preset from '@docusaurus/preset-classic';
 const config: Config = {
   title: 'Expo Open OTA',
   tagline:
-    'An open-source Go implementation of the Expo Updates protocol, designed for production with support for cloud storage like S3 and CDN integration, delivering fast and reliable OTA updates for React Native apps.',
+    'Self-hosted Expo updates for React Native. Multi-cloud (AWS S3, Google Cloud Storage), CDN-ready, and production-grade — an open-source Go server implementing the Expo Updates protocol.',
   favicon: 'img/favicon.ico',
   scripts: [
     {
@@ -48,7 +48,7 @@ const config: Config = {
           // Please change this to your repo.
           // Remove this to remove the "edit this page" links.
           editUrl:
-            'https://github.com/facebook/docusaurus/tree/main/packages/create-docusaurus/templates/shared/',
+            'https://github.com/axelmarciano/expo-open-ota/tree/main/apps/docs/',
         },
         blog: {
           showReadingTime: true,
@@ -59,7 +59,7 @@ const config: Config = {
           // Please change this to your repo.
           // Remove this to remove the "edit this page" links.
           editUrl:
-            'https://github.com/facebook/docusaurus/tree/main/packages/create-docusaurus/templates/shared/',
+            'https://github.com/axelmarciano/expo-open-ota/tree/main/apps/docs/',
           // Useful options to enforce blogging best practices
           onInlineTags: 'warn',
           onInlineAuthors: 'warn',

apps/docs/src/components/HomepageFeatures/index.tsx

@@ -10,30 +10,29 @@ type FeatureItem = {
 
 const FeatureList: FeatureItem[] = [
     {
-        title: '⚙️ Ready for production in 10 minutes',
+        title: '⚙️ Production-ready in 10 minutes',
         description: (
             <>
-                No database, no complex setup—Expo Open OTA is designed for seamless production use. It fully leverages Expo’s configuration, handling <strong>release channels</strong>, <strong>branches</strong>, and <strong>runtime version fingerprints</strong> out of the box. Just connect your cloud storage (S3) and you're ready to go!
+                No database, no complex setup. Connect your cloud storage — <strong>AWS S3</strong>, <strong>Google Cloud Storage</strong>, or any S3-compatible provider — and you’re live. Handles release channels, branches, and runtime versions out of the box.
             </>
         ),
     },
     {
-        title: '🚀 EOAS: One Command to Publish & Configure',
+        title: '🚀 One Command to Publish',
         description: (
             <>
-                Say goodbye to manual setup! Our <code>eoas</code> NPM package automates everything—run <code>npx eoas init</code> to configure your project, and <code>npx eoas publish</code> to push updates effortlessly from your CI/CD pipeline. No extra scripts, no hassle.
+                The <code>eoas</code> CLI automates everything — run <code>npx eoas init</code> to configure your project, and <code>npx eoas publish</code> to push updates from your CI/CD pipeline. No extra scripts, no hassle.
             </>
         ),
     },
     {
-        title: '⚡ CDN Delivery',
+        title: '⚡ Fast Asset Delivery',
         description: (
             <>
-                Your assets, delivered at lightning speed. Expo Open OTA serves static assets through a CDN for maximum performance. Currently supporting AWS CloudFront, with upcoming support for Cloudflare and more—so your users get updates instantly, wherever they are.
+                Assets served at the edge. Deliver updates via <strong>CloudFront CDN</strong> or <strong>GCS signed URLs</strong> — your users get updates instantly, wherever they are. No public bucket access needed.
             </>
         ),
     },
-
 ];
 
 

internal/auth/auth.go

@@ -5,8 +5,9 @@ import (
 	"expo-open-ota/config"
 	"expo-open-ota/internal/services"
 	"fmt"
-	"github.com/golang-jwt/jwt/v5"
 	"time"
+
+	"github.com/golang-jwt/jwt/v5"
 )
 
 type Auth struct {

internal/services/gcp.go

@@ -11,6 +11,7 @@ import (
 	"time"
 
 	"cloud.google.com/go/storage"
+	"google.golang.org/api/option"
 )
 
 var (
@@ -22,7 +23,17 @@ var (
 func GetGCSClient() (*storage.Client, error) {
 	initGCSClient.Do(func() {
 		ctx := context.Background()
-		gcsClient, gcsClientErr = storage.NewClient(ctx)
+		var opts []option.ClientOption
+		b64Creds := config.GetEnv("GOOGLE_APPLICATION_CREDENTIALS_B64")
+		if b64Creds != "" {
+			creds, err := base64.StdEncoding.DecodeString(b64Creds)
+			if err != nil {
+				gcsClientErr = fmt.Errorf("error decoding GOOGLE_APPLICATION_CREDENTIALS_B64: %w", err)
+				return
+			}
+			opts = append(opts, option.WithCredentialsJSON(creds))
+		}
+		gcsClient, gcsClientErr = storage.NewClient(ctx, opts...)
 		if gcsClientErr != nil {
 			gcsClientErr = fmt.Errorf("error initializing GCS client: %w", gcsClientErr)
 		}