How to prepare a self-hosted machine I gift to remote friends - Learning Together (discuss.james.network)
from kiol@lemmy.world to selfhosted@lemmy.world on 11 Feb 22:03
https://lemmy.world/post/25452338

Actively working on a guide, as a companion to my recent podcast episode on the same topic you can hear at podcast.james.network/…/byebye-raspberry-pi

#selfhosted

threaded - newest

hendrik@palaver.p3x.de on 11 Feb 22:24 next collapse

By the way, concerning the loose surge protector: Good thing you replaced that. If you see something like that, and it's mains voltage, always replace it ASAP. Not because it doesn't look nice or the RasPi gets unhooked... But because it's a proper fire hazard. A whole house can burn down if you have a loose mains connection and that somehow leads to electrical sparks.

kiol@lemmy.world on 11 Feb 22:26 collapse

Well said.

solrize@lemmy.ml on 11 Feb 23:20 next collapse

What does this question even mean (no I don’t want to listen to a podcast to find out)?

Sometimes I think people have been using the term “self-hosted” to mean what we used to call a home PC. I have always thought of a hosted computer (whether self-hosted or hosted by a company) as meaning a server which normally would live in a data center, and sometimes even means a rented box or VPS on which you self-host by installing and managing the software yourself (as opposed to using managed hosting or cloud services). Of course if you have good enough internet, you can self-host a server at home, but the considerations are otherwise about the same. I.e. it would usually not also be your workstation or gaming box.

So what is it that your friends are going to do with the machine? That would be pretty important in figuring out how to prepare it.

kiol@lemmy.world on 11 Feb 23:32 next collapse

The recipients are watching Jellyfin content on a smart tv and accessing whatever else pops up on a static page available at hostname.local

infeeeee@lemm.ee on 12 Feb 00:31 next collapse

Don’t use .local as an internal domain it can cause problems. Use .internal, it was recently reserved for this purpose

kiol@lemmy.world on 12 Feb 00:32 next collapse

Thanks!

someonesmall@lemmy.ml on 12 Feb 01:14 collapse

Until August 2024 only .arpa was reserved for residential network services. Glad to hear there is something new less akward!

solrize@lemmy.ml on 14 Feb 09:25 collapse

I see, you are trying to make a home theater PC (HTPC). That would be a clearer term to use.

kiol@lemmy.world on 14 Feb 16:50 collapse

It is running way more than that. Serving my media has been my starting application for explaining this process.

kiol@lemmy.world on 11 Feb 23:33 next collapse

err, I don’t actually know what you mean by question. Your response is to a how to guide. Anyways, cheers since you aren’t interested. No worries.

JustAnotherKay@lemmy.world on 14 Feb 13:22 collapse

You don’t even have to listen to a podcast to find out how misguided this comment is. Click the link, it’s all transcribed. It’s not a question, it’s a guide.

If you’re not interested in the content, scroll past instead of being rude to people.

solrize@lemmy.ml on 14 Feb 20:13 collapse

The link is to podcast.james.network. Why would I expect it to be something other than a podcast?

JustAnotherKay@lemmy.world on 14 Feb 23:29 collapse

The in-body link is to the podcast, but the post itself is a link to discuss.james.network which is a transcription of the guide

solrize@lemmy.ml on 15 Feb 03:46 collapse

You should explain that in the post body, not expect someone to click a link that says “podcast” in hope of getting a non-podcast.

JustAnotherKay@lemmy.world on 15 Feb 05:44 collapse

I dunno if you’re trolling me or if your UI just looks different but

<img alt="" src="https://lemmy.world/pictrs/image/f25bea8c-f454-40a9-8f08-75cbaf5d4b91.png">

Having the link at the top of the post like this, because it’s embedded into the actual post instead of the body like the second link, makes it pretty clear to me that that’s a discussion link and not a podcast link

solrize@lemmy.ml on 15 Feb 08:23 collapse

I see roughly the same thing:

<img alt="" src="https://lemmy.ml/pictrs/image/7a110e27-dd8b-4d3a-bec5-9bfd8e9ce1e7.jpeg">

Your post says there is a podcast at [url] and that you are working on a guide as a companion to it, but it doesn’t say anything about where the guide is or whether any of it is online yet at all. Ok, I see now that the link url is discuss.james.network which is a different domain than the podcast, but that is still not much help. If that’s where the guide is, you should say so. I’d expect to see a discussion forum on a domain like that, not a podcast transcript.

Really, though you should just include the guide in the post. Otherwise you’re just promoting your podcast and discussion site.

JustAnotherKay@lemmy.world on 15 Feb 10:39 collapse

Lemmy is a link aggregator, this guy posted a link to his website and a brief (albeit lacking, I will agree with you there) description of what the links were. I don’t see any issue promoting free content in the forms of links on a link aggregator.

I also think there’s sort of a social agreement that if you’re going to make a comment about a post that exists purely as a link to elsewhere, you should probably click the link so that you know what is being discussed instead of what we’re doing, discussing the link itself lol.

Xanza@lemm.ee on 11 Feb 23:46 next collapse

listen to my podcast, guys. /s

kiol@lemmy.world on 12 Feb 00:05 collapse

Absolutely, hate listening strongly encouraged.

hempster@lemm.ee on 13 Feb 14:30 collapse

I wouldn’t trust a computer donated by anyone let alone for self-hosting personal data on it. No thanks!

kiol@lemmy.world on 13 Feb 15:31 collapse

Haha, that is why it is with friends and family for people who want that. Definitely not for everyone. Cheers.