-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPFS mirror #1
Comments
This comment has been minimized.
This comment has been minimized.
Hey Ruben,
sorry for our late reply and thank you for your offer and idea.
Right now we think that we don't need that. We might consider using IPFS in
the future.
Greetings Lukas
|
@AlpixTM I understand, that you don't need it - but that was never in question. I would just like to offer it as an alternative to regular HTTPS/HTTP mirrors. I just need rsync access to one of your tier1 or main mirrors to make that happen. :) |
Hey Ruben, we only offer tier1 access to our official mirrors, but you can sync from an official mirror. E.g. you could sync from mirror.erickochen.nl::endeavouros Greetings Lukas |
reopen if you need, but looks solved to me ? |
Yeah, will set it up as soon as I find time :) |
I've added it to the cluster. It can be viewed in the Browser via http://endeavouros.pkg.pacman.store/ For pacman you just have to configure it to use the local ipfs node, which should look like this:
|
No, thanks for the information, I will remove it.
No, it's planned to remove the old ones soon |
Would that work for everybody like a normal http mirror, or is some config with pacman needed? |
@AlpixTM there's no special config needed for pacman. The decentralized nature of IPFS just means that there are some operations that have more latency. That's why I recommend having the mirror 3 times in the list, to have pacman retry it. While you can access the IPFS network via publicly available gateway you loose a lot of features doing this (and might run into some rate-limiting). It's recommended to install ipfs on each machine which should use the mirror or have one centralized ipfs instance in a local network since the packages will be cached and offered to other computers in the local network at LAN speed. Additionally, each node that downloaded a package via the mirror will hold it for a while in its cache (until the cache gets wiped the next time). So there are many sources available if a package is often installed - which should allow for organic growth instead of having a lot of servers sitting around. TL;DR the ipfs daemon will replace the lan sharing scripts/addons for pacman, while there's zero configuration necessary, even if you switch between different networks and allow for a more organic decentralized growth of the package exchange infrastructure. |
I've updated the install instructions to include Endeavouros https://github.com/RubenKelevra/pacman.store#use-the-pkg-cache-with-pacman |
@AlpixTM wrote
Hey Lukas, this mirror is gone:
Is there an alternative I can tap into? |
Hey, you can use rsync://mirror.jingk.ai/endeavouros/ Does that work for you? Greetings Lukas |
Hey @AlpixTM, thanks! I've updated my config, if it's not working I let you know :) |
Hey @AlpixTM, while this server works it's kind of slow. I feel like I might overload it when I leech from it all the time. Current download speed is just 16 Mbit/s. Is there any fast server available? :) |
Hey, you could also try rsync://mirror.moson.org/endeavouros/ |
@AlpixTM this one is fine, getting around 250 MByte/s :) Thanks again! |
Hey guys,
I'm running an ArchLinux packages IPFS-Cluster under the domain pacman.store, which allows everyone to join by running a small daemon next to the IPFS node. This is called collaborative cluster.
I was wondering if you're interested in having me fetch your packages as well and add them to the cluster. This would allow people to fetch your ISOs and packages via an IPFS node, which would then continue to seed the files - like bittorrent.
The text was updated successfully, but these errors were encountered: