You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's now happening again. We're using gitpkg.vercel.app to package subdirectories of repos and now we can't install.
So, I'm asking again: How can one "deploy GitPkg with your own vercel account" to avoid this error in the future?
I've never used Vercel but was able to get Gitpkg running in a self-hosted manner on my own server using the Vercel CLI via vercel dev. There are probably easier ways to do this and deploy it directly in Vercel, so maybe someone else can comment on that.
Unfortunately I didn't keep great notes, but all I did was something like the below:
Create a free Vercel account
Check out the gitpkg code to a server
Run npm install to install dependencies
Install Typescript
Install the Vercel CLI
Run vercel dev to start the application.
My notes have the following steps which show some of the steps I did. Apologies that it's not more specific but I remember I had to muck around a bit to find the right sequencing.
mkdir gitpkg
cd gitpkg
wget https://github.com/EqualMa/gitpkg/archive/refs/heads/main.zip
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
// need to restart shell here I think to effect the setup of nvm into PATH
nvm install 22
npm install typescript --save-dev
npm i -g vercel
// I also installed earlyoom because I found that random bots would hit the endpoint and it would chew up memory and crash
apt install earlyoom
At some point in the above you need to link your deployment to your free Vercel account - I /think/ that happens when you first run vercel dev but there may be another step there that I've forgotten.
I put nginx in front of it as a reverse proxy and added a location rule so it would ONLY forward requests to the gitpkg backend that were relevant to our repository. I highly recommend doing this so nginx filters out all the random Internet background radiation and only valid requests are passed to your gitpkg endpoint. (Alternatively if you can deploy this off the public Internet that is safer; I started to deploy it on Tailscale but ran into some internal network config issues that made this painful).
I've had this running happily for several months now. We're planning on removing our dependency on this in our build process soon but that is dragging out so if time permits I'm going to look at stripping out the Vercel requirement as it doesn't seem to add any value for a self-deployment like this.
Activity
yosizesta commentedon Nov 23, 2025
same problem here
EqualMa commentedon Nov 23, 2025
Sorry for the inconvenience. My vercel free account is paused due to overusage. Please deploy GitPkg with your own vercel account.
deflexable commentedon Nov 29, 2025
@EqualMa is there a doc anywhere on how to easily deploy this?
DanielKuhn commentedon Feb 4, 2026
It's now happening again. We're using gitpkg.vercel.app to package subdirectories of repos and now we can't install.
So, I'm asking again: How can one "deploy GitPkg with your own vercel account" to avoid this error in the future?
trogau commentedon Feb 4, 2026
I've never used Vercel but was able to get Gitpkg running in a self-hosted manner on my own server using the Vercel CLI via
vercel dev. There are probably easier ways to do this and deploy it directly in Vercel, so maybe someone else can comment on that.Unfortunately I didn't keep great notes, but all I did was something like the below:
npm installto install dependenciesvercel devto start the application.My notes have the following steps which show some of the steps I did. Apologies that it's not more specific but I remember I had to muck around a bit to find the right sequencing.
At some point in the above you need to link your deployment to your free Vercel account - I /think/ that happens when you first run
vercel devbut there may be another step there that I've forgotten.I put nginx in front of it as a reverse proxy and added a location rule so it would ONLY forward requests to the gitpkg backend that were relevant to our repository. I highly recommend doing this so nginx filters out all the random Internet background radiation and only valid requests are passed to your gitpkg endpoint. (Alternatively if you can deploy this off the public Internet that is safer; I started to deploy it on Tailscale but ran into some internal network config issues that made this painful).
I've had this running happily for several months now. We're planning on removing our dependency on this in our build process soon but that is dragging out so if time permits I'm going to look at stripping out the Vercel requirement as it doesn't seem to add any value for a self-deployment like this.