mwt
commented
2 years ago Hi, it looks like the package repository has not been updated for two months.
Yes. Packages are currently uploaded to PackageCloud manually. So nothing is broken.
As an update, in the last two months, I have built out the mirroring infrastructure for mirror.mwt.me considerably. There are now three origin servers (US East, US West, and Europe) with a tiered CDN that pulls from the closest origin. There is also a failover server that is used if the node near you goes down.
I mirror all of the files from PackageCloud each day to /ghd/ which is the second link in the readme.
I also have been using an alternative at /github-desktop/ which updates each day using the latest release from GitHub. This is automated, works well, and does not depend on PackageCloud.
@shiftkey so, if you stopped paying for PackageCloud today, you'd still have a working deb/rpm repo at /github-desktop/ which I could propose instructions for in the readme. I want to clarify that you could stop using PackageCloud at any time without major consequences or effort on your part.
My goal in making this mirror was to fix the bandwidth issue and I'd like to help fix this $160 issue as well. Maintaining this shouldn't cost you money. Let me know if you think this is good or if you think there's something missing. You can also do this and try out Cloudforge at the same time.
shiftkey
If you're using a Debian or RPM-based distro I've started evaluating PackageCloud as a way of distributing updates. The trial lasts for 2 weeks.
The details are up at https://packagecloud.io/shiftkey/desktop including setup instructions, and the current release is listed there. I'm aiming to get automated releases in place for the 2.5 release of GitHub Desktop that's coming up, but no promises (and I can manually upload anyway if I don't get time).
This is not a free service (starts at $75 a month) but if you get value out of it and would love to sponsor to assist with the expenses please get in touch (either here or via email).