this post was submitted on 27 Dec 2023
63 points (97.0% liked)

Selfhosted

39964 readers
211 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 1 year ago
MODERATORS
 

I have an old laptop lying around and I have been meaning to self host some stuff on it but never got around to it.

My biggest limitation is that I only have WIFI and I do not control the network. It's basically your default residential WIFI network.

The only thing I actually need is self-hosted cloud. What can I utilize this laptop for?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 10 months ago (2 children)

I starter my home server with a laptop. I did nextcloud, paperless, jellyfin + *arr services, photoprism, and a few others.

Not having control over your network is the biggest hurdle because you kind of need a fixed IP to access it.

However, there are some services to broadcast your hostname to the local network (e.g. so you can log in with serveruser@myserver over SSH).

You may be able to use that to access your containers from the network, but just keep in mind that other users on the local network can also access your server.

[–] [email protected] 1 points 10 months ago

Fixed IP doesn't matter today with virtual/mesh network approaches like Wireguard/Tailscale.

They open an outbound connection, so the router treats it like any other connection. Once the tunnel is established, inbound comms can take place.

Using Tailscale's Subnet Router enables access to local devices that can't run a TS client, while the ~~Serve and~~ Funnel options enable external access from devices that don't have the TS client installed. Edit: Serve is for sharing to TS clients that aren't part of your TS network.

It's really interesting to see these solutions today, when Hamachi was doing it 20 years ago. Glad to see it's caught on, and being developed/extended.

[–] [email protected] 1 points 10 months ago

Local only does not provide much value over what I have, unfortunately. I would probably just use KDEconnect for that.