Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Of course it would be self hosting. If the website isn’t hosted on fastly, and is hosted by an individual, that would be the definition of self hosting. You’re also assuming that Fastly is caching responses, do you know that for certain?
Literally all you’ve done so far is resolve the host name to a DNS record. You think you’ve done something, but you haven’t.
lol what the fuck is your problem? How about you do something and explain to me how you self host a CDN hosted by fastly?????
When did I resolve the Hostname to a DNS record? Are you fucking stupid you obviously don't know what you are talking about. I resolved it's domain to an IPv4 address which points entirely to a fastly server. It's not a resource that get's delivered by CDN, it's the whole fucking website they are serving, which is a service they sell and that's not self hosting.
God damn why am I even spending my time arguing with someone that didn't understand the basics yet. If you think a domain is a hostname and an IPv4 address is a DNS record, just back off and return to the books. You probably feel so cool and think you have done something, which you did, you ridiculed yourself.
You clearly don’t understand a single thing about how the internet works and are very confused. Let me help you out.
You don’t? The website is what would be self hosted. Not Fastly.
Right there. You resolved the host record, probably an A record or ANAME for the website (dev.to) into an IPv4 address, using DNS.
Here’s what you’re critically misunderstanding about this. Just because you resolve the record for a website and the IP that’s returned belongs to fastly does not mean fastly is hosting the content. You literally haven’t done anything to prove that the website isn’t self-hosted on a computer in some guys garage. You’re making assumptions based on ignorance and using those assumptions to gatekeep self hosting because you don’t even know what you don’t know. It’s very possible that site isn’t self hosted, but so far you haven’t actually found any proof of that like you think you have.
A domain can have several host records of different types including one at the root of the domain. What you’re resolving isn’t “a domain” it’s a single record for that domain, and its associated IP address is contained in the DNS record. If you’d like to familiarize yourself with this system, try this: https://www.dummies.com/book/technology/information-technology/networking/general-networking/dns-for-dummies-292922/
It’s clear that you’re a hobbyist with very little understanding of how the internet and self hosting works on a fundamental level and that’s ok. But I recommend instead of wasting your energy being confidently wrong very publicly for the purpose of gatekeeping, you use that energy to learn how these things actually work instead.