Closed J-Hendy closed 2 years ago
It should be back up. I'm in the process of setting up something more stable. sourceforge has turned out to be really cantankerous.
All our support for this! Let us know here when you have a chance to complete it. Thank you so much.
I will let you know, I'm in the process of setting up the new mirror.
Hi, if you want to offload any bandwidth, I have some mirror infrastructure that you can use. Right now, I run apt-mirror
to clone your backblaze repo, but I could receive the files in any way that's convenient. For example, you could build the repo with GitHub actions, roll it into a tarball and put it in a consistent location, send it to an endpoint, etc.
I appreciate the offer -- another user has also offered hosting but we haven't worked out delivery yet. I was actually looking to make the jump today because I'm sick and tired of sourceforge (big mistake to ever involve them), I can't ask users to install a patched apt (required for GH hosted binaries), and Zotero just isn't moving taking over the hosting.
I have been working feverishly over the past few days to get the backblaze bucket up and running, and it should work now, but it's honestly not been a great experience dealing with their library, so I'm looking to be rid of that too.
Qua infrastructure, I was thinking of sticking whatever hosting is available behind the free cloudflare CDN; the builds already happen in github actions, so I could either just leave that in place (or to be precise, rebuild things so these are the primary location) and you could grab them from there, or I if I could push them to you in some kind of way that would be fantastic and I'd just make that primary. rsync over ssh would be most frugal, a tarball to an endpoint would be possible but I rebuild the repo at least once a day as new beta's drop, so that seems a bit wasteful. But whatever works for you.
rsync over ssh would be perfect. I guess I would make you a user account on my server and you add the rsync command to GitHub actions with your password stored as a secret?
Note: My mirror is accessible through two hostnames:
rsync over ssh would be perfect. I guess I would make you a user account on my server and you add the rsync command to GitHub actions with your password stored as a secret?
That's how I have it set up for sourceforge right now. I hope Ruben won't take affront, but I'm eager to get away from sourceforge and backblaze.
Note: My mirror is accessible through two hostnames:
and . The second uses free Cloudflare as you described.
I'd just point my existing cloudflare DNS at either of those.
That works for me. You can just send me your pubkey to add to authorized_hosts
. I'll make a retorquere user for you and you can rsync via retorquere@mirror-rs.mwt.me
You should probably point Cloudflare at mirror-rs.mwt.me. I'll add your hostname to nginx.
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQC/z3vcoTsQ1g9TAsDz7pBPLqJtJqcpfpCkk1XYAgEXR8Mkh3N9xbwIBLCDup9dOh40brBLPZgR8JsmuehOXHSx9XfuQlZKlK+Q6sOf9WEC6szrQTkI5puwSyjc/KCmbb/T8MaSUAmenS1ilTzphQvb0YqjyXakNVb4B2kv5iDiT9IzAiOwIAQZMKGoXtKKSqvRZPj6WsD4Cx47c4oQOFsiIStuSm0IGxxgvbaFqGf8hQAW4XYceskjs3Gpa2H7quYw4xUDsNQ3PUtw6Ab/FAcYQc/Im8pN77EIOROIKRYR59EYqVbgBJEHJP0tijbiZQTwF27wkfHx5R2GkHgNRk4zRhCt/eghDf7nLJg8fwn0bBBuX1orm+tUhGMYOu0rXcliXvmq5n7s6EaeShsQ+Z6pd0YbvfeQklLVmorQRQzr3a+Bbho9TEqQ8NlWgSqshSe8gxc47MGCnqLIvUnxjspvVuwxtq53K3aJXVQ+siXzFKFySjEvr04lbH9PEo3QU7TGCDolv6YZp1AncexKXgyQYYnQxmCM6lN40FQbI61K0FxV0Y3C3Dl2Y9PN4fgT5R1wM4cZJn5iUU8dfQjyYhnSWt8NBUwREDl51p7lakLs0oJzySLZG6fDPToBjfrk4rDXsRFRi9UBMcP3MWnyn40DW7RGfGMndaC4UUoMv/Dj3w== emiliano.heyns@iris-advies.com
Can you add these two hostnames?
I want to add rpm packages too at some point so I want to gradually migrate everything to the latter hostname.
I added the user. You should be able to push with something like
rsync -av --delete $SOURCE retorquere@mirror-rs.mwt.me:/
I setup nginx on those two hostnames to show the same site as mirror.mwt.me but without the redirect to my website. We can adjust this once there are some synced files to display.
I finished setting this up and threw all the current files in there. Your hosts aren't pointed there yet, but as a test, I added retorquere-test.mwt.me to the list of hostnames. You can see that:
https://retorquere-test.mwt.me/zotero-apt https://retorquere-test.mwt.me/apt-package-archive
both go to the right place and the root domain just redirects to this repo.
Do these map to the same actual location? In that case I'll just use the latter -- the final part (zotero-apt
/apt-package-archive
) is in the repo content... which I now realize is because the Zotero crew asked me to do this... which complicates everything. I may need to rethink this.
Yeah, removing the final part from the package contents makes total sense. I'm trying to get the rebuild with it stable tonight, then tomorrow without, and then we don't need to round-robin anything. Any mirror under any URL would work.
They both map to the same location using symlinks (which is /
in rsync). I'm not sure what you mean by the final part being in the content.
It might be smarter to work this out such that you rsync to /apt-package-archive
and then I serve the root using the webserver. Then, if you decide to sync rpm packages to /dnf-archive
or something, it'll work without having to change anything.
I mean that the Packages
files has apt-package-archive
in it for the one and zotero-apt
for the other, and that the repo won't work for the mismatch. It doesn't actually have to have this in the Packages
file, it didn't use to be there. I can revert that but need to get to a stable publish first.
Got it. That does sound like a pain. I just ripped these files with a simple:
wget -m https://apt.retorque.re/file/zotero-apt/index.html
So, only /zotero-apt
would be correct at the moment.
The repos have been updated. What paths should I rsync to?
Let's do retorquere@mirror-rs.mwt.me:/apt-package-archive
. That should be more flexible. That way you can sync to any retorquere@mirror-rs.mwt.me:/path
and serve it as https://zotero.retorque.re/path
.
(so, this will appear as https://zotero.retorque.re/apt-package-archive)
It tried to use password auth on the server for some reason. Perhaps the SF cert install step is only setting it to be used by that one host.
I'll troubleshoot by trying to rsync something simpler through gh actions.
Hi,
I'm a bit rusty with adding package repos but followed the installing Zotero steps and had the following 404 errors when downloading the package:
Regards.