Skip to content

Conversation

@tabathad
Copy link
Contributor

@tabathad tabathad commented Feb 6, 2026

Part of #1325, complements #1335.

Adds a deployment guide covering:

  • Prerequisites
  • Quick start walkthrough
  • Docker deployment
  • Git client configuration
  • Production considerations

Also adds the deployment page to the docs sidebar.

@netlify
Copy link

netlify bot commented Feb 6, 2026

Deploy Preview for endearing-brigadeiros-63f9d0 ready!

Name Link
🔨 Latest commit 24eb8e2
🔍 Latest deploy log https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/6985fe4216d8940008568282
😎 Deploy Preview https://deploy-preview-1385.git-proxy.preview.finos.org
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions bot added the documentation Improvements or additions to documentation label Feb 6, 2026
@codecov
Copy link

codecov bot commented Feb 6, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.35%. Comparing base (2150064) to head (24eb8e2).
⚠️ Report is 36 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1385      +/-   ##
==========================================
- Coverage   81.35%   81.35%   -0.01%     
==========================================
  Files          65       65              
  Lines        4639     4649      +10     
  Branches      792      792              
==========================================
+ Hits         3774     3782       +8     
- Misses        850      852       +2     
  Partials       15       15              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@tabathad tabathad force-pushed the docs/deployment-guide branch from 761c2e7 to dfac352 Compare February 6, 2026 12:40
@tabathad tabathad force-pushed the docs/deployment-guide branch from dfac352 to 24eb8e2 Compare February 6, 2026 14:44
Copy link
Contributor

@jescalada jescalada left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good so far! Just wondering if we could look into the config loading issue - although it might be because I tested on v1.19.2 rather than the latest rc...

As for the Docker part, I'll do some more setup testing later so we can refine this 👍🏼

- Sessions are in-memory only (lost on restart)

2. **MongoDB** — Recommended for production
- Requires MongoDB 7.0+
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe GitProxy is compatible with Mongo 6.0+, as shown in the latest CI build matrix.

Suggested change
- Requires MongoDB 7.0+
- Requires MongoDB 6.0+

### 3. Start GitProxy

```bash
git-proxy --config ./proxy.config.json
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oddly, this command doesn't seem to be correctly loading the config on my end. When calling git-proxy --validate, I see that the config file being loaded is ~/.nvm/versions/node/v22.13.1/lib/node_modules/@finos/git-proxy/proxy.config.json which is not the "current working directory" that's mentioned in the option description...

I wonder if this is exclusive to the GitProxy global install and if there's an easy way to fix it.

### 6. Approve the Push

1. Navigate to http://localhost:8080 in your browser
2. Log in with default credentials (**development only**):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might want to include a link to the auth documentation in the architecture guide: https://github.com/finos/git-proxy/blob/1e98d9dbef27f6e338cf18354b0bbbc418b8a070/docs/Architecture.md#Authentication

The proper link will be available after that PR is merged!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants