search

lancachenet / monolithic

A monolithic lancache service capable of caching all CDNs in a single instance
https://hub.docker.com/r/lancachenet/monolithic
Other
725 stars 73 forks source link

Add the ability to select stored Steam games #179

Open kol19pl opened 10 months ago

kol19pl commented 10 months ago

config file or docker var

unspec commented 9 months ago

Select them in what way? What do you want to do with selected games?

If you are wanting to make sure a specific game is on your cache then we would suggest something like:

https://github.com/tpill90/steam-lancache-prefill

To pre-cache specific games

stale[bot] commented 6 months ago

This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

IsaacGao commented 2 months ago

Select them in what way? What do you want to do with selected games?

If you are wanting to make sure a specific game is on your cache then we would suggest something like:

https://github.com/tpill90/steam-lancache-prefill

To pre-cache specific games

Greetings. Allow me to clarify your scenario:

  1. Within AWS, I've established a caching server utilizing ECS, configured through LanCache.
  2. By means of the cloud provider's DNS resolver, I've directed Lancache towards this caching service.
  3. The intention is for this cache to expedite downloads solely for a designated game, such as Dota2; other games, upon being forwarded, would bypass my caching server to avoid incurring costly public internet traffic.

I inquire if there exists a method to accommodate this specific arrangement. Many thanks.

unspec commented 2 months ago

If i understand correctly, you would like lancache to download a specific game from your AWS environment if it gets requested, but download all other games direct from the appropriate game provider/somewhere else if they are requested?

I'm afraid thats not something that lancache supports. lancache works on files/chunks/slices that are requested by the client - it doesn't understand (or care) what game those files/chunks/slices are a part of. Its the client's (e.g steam) responsibility to know what files it needs for each game etc. So there is no way to trigger different behaviour based on the game being requested.

We also do not have a way to specify specific upstream targets for files (i.e no way to tell lancache where to find your AWS caching server) - lancache simply uses the original target/source the client tried to access.

IsaacGao commented 2 months ago

If i understand correctly, you would like lancache to download a specific game from your AWS environment if it gets requested, but download all other games direct from the appropriate game provider/somewhere else if they are requested?

I'm afraid thats not something that lancache supports. lancache works on files/chunks/slices that are requested by the client - it doesn't understand (or care) what game those files/chunks/slices are a part of. Its the client's (e.g steam) responsibility to know what files it needs for each game etc. So there is no way to trigger different behaviour based on the game being requested.

We also do not have a way to specify specific upstream targets for files (i.e no way to tell lancache where to find your AWS caching server) - lancache simply uses the original target/source the client tried to access.

Thank you for your response, your comprehension is accurate.

I grasp your point now, and upon reflection, I indeed confirm that games are downloaded in segments. It is unnecessary for Lancache to decipher the individual clients' download logic.

Gratitude for your patient elucidation once more.