How We Built & Deployed MediQuick: Zero-Token Git Deployments on OrbixPanel

Connecting your self-hosted infrastructure to GitHub, GitLab, or Bitbucket shouldn't involve manually copying SSH keys, generating personal access tokens, or pasting repository URLs back and forth.

When building MediQuick—a fast medical information lookup engine that aggregates and formats clinical data from openFDA, DailyMed, and RxNorm—we wanted a deployment workflow that felt as frictionless as modern PaaS tools, but ran entirely on our own self-hosted servers.

In this post, we'll look at how OrbixPanel’s 1-Click OAuth Git Integration works under the hood and how we deployed MediQuick without pasting a single token or URL.

---

🏥 What is MediQuick?

MediQuick is a web application designed to query medical and pharmaceutical data across official public APIs:

• openFDA: Real-time drug safety, adverse event reports, and recall data.
• DailyMed: Official FDA package insert labels and clinical medication guides.
• RxNorm: Normalized names for clinical drugs and link identifiers.

When deploying a multi-API health tech application, you need quick iteration: push code to GitHub $\rightarrow$ automatically build, deploy, and assign Let's Encrypt SSL.

---

🔒 The Challenge: Private Token Sprawl

Normally, setting up self-hosted Git deployments forces you to choose between two annoying options:

1. Pasting Raw Git URLs & Access Tokens: Exposing personal tokens in text boxes across various tools.
2. Setting up Webhooks & SSH Keys manually per repository: Time-consuming setup for every new app you build.

---

⚡ The Solution: One-Time OAuth Registration

OrbixPanel solves this by using 1-Time OAuth Provider Integration.

How it works:

1. 5-Minute One-Time Setup: You register an OAuth App inside your GitHub, GitLab, or Bitbucket account (setting your server's callback URL).
2. Encrypted Credentials: Your OAuth Client ID and Secret stay encrypted locally on your OrbixPanel server.
3. 1-Click Deployment: Once connected, your panel automatically populates all your private and public repositories in a single list.

Zero manual token management, zero public URL pasting. Just click "Deploy" next to your branch.

---

🚀 Step-by-Step: Deploying MediQuick via OAuth

1. Register the OAuth Provider (Once per Server)

In your GitHub developer settings, create a new OAuth Application:

• Application Name: OrbixPanel
• Homepage URL: https://<your-server-domain>
• Authorization Callback URL: https://<your-panel>/api/git/callback/github

Paste the generated Client ID and Client Secret into OrbixPanel $\rightarrow$ Git Integrations.

2. Select Repository & Deploy

Once authorized, OrbixPanel fetches your repository list securely.
Find orbixpanel/mediquick, pick the branch (main), and hit Deploy.

OrbixPanel handles the rest automatically:

• Clones the repository securely over OAuth.
• Detects app environment & builds dependencies.
• Provisions Let's Encrypt SSL certificates.
• Serves https://mediquick.orbixpanel.com behind a reverse proxy with zero downtime.

---

🛡️ Security & Privacy First

Because OrbixPanel is self-hosted:

• Your OAuth tokens and access keys never hit 3rd-party servers or external clouds.
• OAuth tokens are stored with AES encryption locally on your own server hardware.
• You maintain total ownership over your deployment pipelines and API keys.

---

💬 Try It Out

Whether you are building healthcare apps like MediQuick, internal SaaS tools, or microservices, deployment should take seconds, not hours.

Check out live MediQuick at mediquick.orbixpanel.com, and test out 1-Click Git Deployments on your own VPS with OrbixPanel (Community Edition is FREE forever).

👉 Get Started: orbixpanel.com