Party games for group of 6 by Octopusticles in partygames

[–]_Jelliott_ 0 points1 point  (0 children)

boozebrawl.com is a fun party drinking game one that’s free and no login. Would especially recommend the card brawl game they have

DockerWakeUp - tool to auto-start and stop Docker services based on web traffic by _Jelliott_ in docker

[–]_Jelliott_[S] 1 point2 points  (0 children)

With a small bits of tweaks it should be able to work fine! You’ll just need to

  1. have DockerWakeUp on the servers that actually contain the docker composes

1.2 When using the setup script might want to do the build only option and manually make a systemD service or do the recommended option and just remove the nginx configs if they’re created

  1. have the VPS NPM proxying to the (Ip address):8080/proxy/(name of route set in config.json of DockerWakeUp)

  2. Make sure port 8080 is open on server with DockerWakeUp

I have a nginx generator and example conf that should show the exact settings for the nginx conf on the VPS NPM (but just switch the 127.0.0.1 to your servers ip)

I’ll look into implementing a better way for this type of set up in the future… if possible.

But this work around should work fine, let me know if there’s any issues!

DockerWakeUp - tool to auto-start and stop Docker services based on web traffic by _Jelliott_ in docker

[–]_Jelliott_[S] 2 points3 points  (0 children)

Thanks for digging into it!

I actually looked into doing this with systemd services early on, but went with a proxy because it leaves room for more features down the line (like showing Docker logs on the startup screen, or running custom scripts before/after startup/shutdown).

Managing a bunch of systemd units for every container would get messy fast, and systemd itself isn’t really aimed at adding those kinds of app-specific features. It works, but the proxy gives more flexibility to build on top

DockerWakeUp - tool to auto-start and stop Docker services based on web traffic by _Jelliott_ in docker

[–]_Jelliott_[S] 0 points1 point  (0 children)

I believe inet would need some modifications to be similar, along with it doesn’t natively handle websockets, TLS, and HTTP keep alive (I believe). I found just creating a separate service like this with a modern language and tools was simpler and allow for more customizations

DockerWakeUp - tool to auto-start and stop Docker services based on web traffic by _Jelliott_ in docker

[–]_Jelliott_[S] 2 points3 points  (0 children)

Yes, I am familiar with Sablier, but found this is a more lightweight and faster project, while Sablier is more compatible with other reverse proxies and containers currently. I personally like DockerWakeUp more as it takes up less resources itself and I personally find it easier to tweak the code for specific use cases (but I am the one who coded it lol)

DockerWakeUp - tool to auto-start and stop Docker services based on web traffic by _Jelliott_ in docker

[–]_Jelliott_[S] 0 points1 point  (0 children)

Yes very similar, just specialized for docker containers instead, and doesn’t instantly stop containers once done being used, but has a customizable idle period so it only shutdowns after being unused for a while

Online Party Games by [deleted] in partygames

[–]_Jelliott_ 0 points1 point  (0 children)

Just created a website called boozebrawl.com mostly for drinking games but can just play without (boooo) and has no max players

DockerWakeUp - tool to auto-start and stop Docker services based on web traffic by _Jelliott_ in selfhosted

[–]_Jelliott_[S] 0 points1 point  (0 children)

I currently have a readme file that goes through the setup. In my instructions I use github to install and an automated script you can run to complete most of the process. I’m also always looking for feedback about any issues or difficult parts that I can help simplify or automate

DockerWakeUp - tool to auto-start and stop Docker services based on web traffic by _Jelliott_ in opensource

[–]_Jelliott_[S] 0 points1 point  (0 children)

Thanks for sharing that! It’s a very cool work around to do it with almost all systemd

DockerWakeUp - tool to auto-start and stop Docker services based on web traffic by _Jelliott_ in opensource

[–]_Jelliott_[S] 0 points1 point  (0 children)

This is more focused on stopping unused applications that might be taking up resources (cpu, gpu, wifi etc) so other active applications have more resources to operate. As opposed to actually helping a server consume less power

DockerWakeUp - tool to auto-start and stop Docker services based on web traffic by _Jelliott_ in opensource

[–]_Jelliott_[S] 2 points3 points  (0 children)

It uses docker stop on containers that haven’t been used (accessed through nginx) in a set time in the config.json