openresty / openresty/openresty.org

Rsync endpoint for http://openresty.org/package/

Open
#217 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
1.3k
Forks
293
Avg merge
2d 20h
Merged PRs (30d)
2

Description

@zenithalhourlyrate, as the maintainer of TUNA mirrors, reported a syncing issue in #200. Although this issue has been resolved, it would still be very helpful to provide an rsync endpoint for open-source mirror sites, as it could help:

  • Reduce redundant requests and file transmission through network, and saves disk space of downstream, as many files (directories) are actually symlinks.
  • Keep the integrity of synced packages better. I'm not sure whether openresty packages are behind CDN, but as far as I know the file listing by CDN may not be updated and thus HTTP-based syncing programs (lftp, etc.) cannot get a full list of packages and metadata files and bring users trouble.

I'm also the maintainer of one of the downstream mirrors of openresty (also we're users of openresty actually!). After a discussion with @zenithalhourlyrate, we think that I should open up a new issue to follow up the progress, as the original issue #200 is closed now.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the repository's site and the prior discussion in issue #200 to understand how the package endpoint is currently served. Determine the appropriate way to provide an rsync endpoint for downstream mirrors; done means mirror maintainers can sync the OpenResty package tree reliably with reduced redundant transfers.

Written by the indexing model from the issue text.

Assessment

Domain
infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.