Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
infra
infra
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 65
    • Issues 65
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Analytics
    • Analytics
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards
  • alpine
  • infra
  • infrainfra
  • Issues
  • #325

Closed
Open
Opened Mar 16, 2010 by Kogen Mantis@k0gen
  • Report abuse
  • New issue
Report abuse New issue

Use bittorrent protocol for alpine linux iso's and img's distribution

Here is how I see it:

  1. New Alpine Linux is compiled on build machine.
  2. New ISO image is prepared with md5 hash file
  3. New torrent is generated for above files. (configured for linuxtracker or local tracker)
  4. Build machine starts seeding torrent and send newly made .torrent to list of mirror servers.
  5. Mirror servers are configured to watch for a new .torrent files in designated alpine dist torrent folder.
  6. When new .torrent is detected mirror server immediately start download and when finished became seedbox for this files.

(from redmine: issue id 325, created on 2010-03-16, closed on 2011-06-12)

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
4
Labels
Download mirrors Feature Normal Rejected
Assign labels
  • View project labels
Reference: alpine/infra/infra#325