Skip to content

Pips801/lancache

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

16 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Game Download Cache Docker Container

Introduction

This docker container provides a caching proxy server for game download content. For any network with more than one PC gamer in connected this will drastically reduce internet bandwidth consumption.

The primary use case is gaming events, such as LAN parties, which need to be able to cope with hundreds or thousands of computers receiving an unannounced patch - without spending a fortune on internet connectivity. Other uses include smaller networks, such as Internet Cafes and home networks, where the new games are regularly installed on multiple computers; or multiple independent operating systems on the same computer.

This container is designed to support any game that uses HTTP and also supports HTTP range requests (used by Origin). This should make it suitable for:

  • Origin (EA Games)
  • Riot Games (League of Legends)
  • Battle.net (Hearthstone, Starcraft 2, Overwatch)
  • Frontier Launchpad (Elite Dangerous, Planet Coaster)
  • Uplay (Ubisoft)
  • Windows Updates

You can use this container for Steam, however steamcache container is a better option as it uses a different caching method that's better for Steam.

Usage

You will need to have a DNS server forwarding queries to the machine your docker container is running on. You can use the steamcache-dns docker image to do this or you can use a DNS service already on your network see the steamcache-dns github page for more information.

Run the origin container using the following to allow TCP port 80 (HTTP) through the host machine:

docker run --name lancache -p <ip>:80:80 pips/lancache:latest

Hey!: you will need to add a second IP to the interface you run the lancache on. More info here

Quick Explanation

For an game cache to function on your network you need two services.

The cache service transparently proxies your requests for content to the content procider, or serves the content to you if it already has it.

The special DNS service handles DNS queries normally (recursively), except when they're about the games you're interested in and in that case it responds that the depot cache service should be used.

Monitoring

Tail the access logs (default: /data/logs/access.log).

docker exec lancache tail -f /data/logs/access.log)

Running on Startup

Follow the instructions in the Docker documentation to run the container at startup. Documentation

Thanks

Based on original configs from ansible-lanparty. Modified from Steamcache Team.

About

Generic LAN Download Content Cache

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • Nginx 88.0%
  • Shell 12.0%