this post was submitted on 27 Oct 2023
10 points (100.0% liked)

Self-hosting

2777 readers
2 users here now

Hosting your own services. Preferably at home and on low-power or shared hardware.

Also check out:

founded 2 years ago
MODERATORS
poVoq
sam_uk
10
Advice around setting up two laptops, one as server (self.selfhosting)
submitted 1 year ago* (last edited 1 year ago) by schmorpel to c/selfhosting
14 comments fedilink hide all child comments
 

So I have two laptops. Both run Linux Mint.

I need Laptop 1 to work with.

Laptop 2 is an unrepairable POS that starts having a little trouble with keyboard and hinges but works nicely otherwise and has a nice large 1TB disc and a GPU. I want to bury L2 in a shelf(*) and save videos and music on it to access from L1.

I would also like to play with Stable Diffusion on L2, accessing it from L1. Can I do that?

Edit: At some point I want to have my website served from L2 as well but I guess that can be a future project.

(*) Bonus points for ideas about how to have L2 do other useful things when I don't use it and install it as grow tent heating instead of just have it sit in a corner.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] admin@mastodon.futurelab.social 1 points 1 year ago (1 children)

@schmorpel It's about defense in depth. If you are running an application inside of a docker container, it's much more difficult for it to interact with or compromise other applications running in other containers or on the host system. So if I'm running a bookwyrm instance and a mastodon instance in separate containers, and there's a security flaw in bookwyrm that someone exploits, that doesn't mean they automatically get access to the mastodon stuff too.

[โ€“] admin@mastodon.futurelab.social 1 points 1 year ago

@schmorpel additionally, using containers allows for wrapping of dependencies. If I have one application that uses python 2.7 and another that uses python 3, installing both versions on the host system could cause conflicts. But containers have separated file systems, so they can each have their own dependencies without conflict. Mastodon runs a web service to serve http content, a database, various workers etc that can all run together on an separate network stack from other containers.