this post was submitted on 25 Oct 2025
27 points (93.5% liked)

Selfhosted

53057 readers
719 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hi, I teach a CS course, and I was wondering if there is a practical way in which to setup a server that would accept student's tar files, run some tests, and show them the results.

I could go "full unix mode" and roll up some accounts let them ssh into a server, scp their their files.... but I was wondering if there is a prepacked solution for this that is nicer to the eye. And I thought maybe you know some.

you are viewing a single comment's thread
view the rest of the comments
[–] lucullus@discuss.tchncs.de 1 points 1 week ago (1 children)

Security noob here. Would it be sufficient (in addition to only local authorized access) to directly put the file in an unprivileged container, watching its log output? And of course limiting resource use and execution time of the container (don't know if common container tools like docker or podman have a way to limit resources out of the box)

So lets say a simple interface for the file upload behind an authentication service, based on lets say python cgi, ramping up an unprivileged nonroot docker container, killing the container after a fixed time (a few seconds).