DEV Community

Cover image for How to Sync Mobile Workspaces Directly to GitHub (Without a Backend)
Cyrus Bye
Cyrus Bye

Posted on

How to Sync Mobile Workspaces Directly to GitHub (Without a Backend)

DemonZ Deployer glowing cat logo
If you have ever tried doing serious development work on a mobile device—whether building web apps or running Python scripts in Termux—you know the absolute nightmare that is version control on the go.

Writing the code on your phone is the easy part. But trying to push hundreds of files, nested folders, and assets to a GitHub repository via a mobile web browser? It usually results in crashes, payload limitations, and immense frustration.

I got tired of fighting mobile browsers, so I built a frictionless, zero-cost solution.

Enter DemonZ Deployer.

⚡ The Concept: Serverless Workspace Sync

DemonZ Deployer is a hybrid deployment engine that completely bypasses standard browser upload limits.

Instead of uploading files individually, you compress your mobile workspace into a single workspace.zip file. You upload that binary through a secure web interface, which triggers a GitHub Action to automatically unpack, verify, and commit the structural changes directly to your repository in the background.

No custom backends. No databases. No hosting fees. Just the GitHub REST API and GitHub Actions.

🏗️ How the Architecture Works

I wanted this tool to be fully serverless and highly secure. Here is the pipeline:

  1. The Interface (100% Client-Side): The frontend is a static web app hosted on GitHub Pages. It uses a sleek glassmorphism UI optimized for touch screens.
  2. Authentication: It asks for your GitHub Personal Access Token (PAT). This is stored strictly in your browser's localStorage. The app makes API calls directly to api.github.com—meaning your credentials never touch a third-party server.
  3. The Payload: When you drop your workspace.zip into the UI, it encodes the binary to Base64 and executes a PUT request to your target repository.
  4. The Engine: Inside your target repository, a lightweight GitHub Actions workflow (deployer-pipeline.yml) listens for changes to that specific zip file. When it detects the payload, the runner wakes up, unzips the payload, overwrites the old files, purges the archive, and commits the changes cleanly.

🚀 Try it Yourself

You don't need to install anything to use it. I've hosted the interface centrally so anyone can use it as a free SaaS tool.

Step 1: Prep your Repo
Drop this official GitHub Actions workflow file into the .github/workflows/ folder of the repository you want to sync to.

Step 2: Deploy
Head over to the DemonZ Deployer Web App.
Enter your repo name, paste your PAT, and upload your zip. Watch the terminal UI stream your deployment in real-time.

🤝 Let's Collaborate

I built this under DemonZ Development to solve a massive pain point for developers building on Android and constrained devices.

Check out the full source code and documentation here:
🔗 DemonZ Deployer GitHub Repository

If you find this architecture useful, I'd love to hear your feedback, see your pull requests, or just get a ⭐ on the repo! Let me know what you think in the comments below.

Top comments (0)