Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Self-Host?

romanzipp.com

Post reply on HN
Print view View original

211–220 of 269 posts

Re: Why Self-Host?

#211

Post by moehm »

udev4096 wrote: post #176
maxheyer wrote: post #148

Earlier quoted context omitted.

Hi R_Spaghetti, Founder of enum here. That's a fair point, and a good catch. Honestly, using Google Workspace for our internal email was a pragmatic choice early on to let us focus on building our core product. It's a classic startup trade-off, and one we're scheduled to fix in the coming weeks. I want to be clear, though: our customer-facing platform and all its data are and always have been 100% sovereign. Our infr…

> Our infrastructure is totally independent of Big Tech That's wishful thinking. You cannot be truly independent from them, no one can. They control major BGP routes, major ASN, big fiber cables, etc. It's just impossible

'If you wish to make an apple pie from scratch, you must first invent the universe.'

- Carl Sagan

They aren't going to cut the fiber cables if your Google accounts gets locked.

Re: Why Self-Host?

#212

Post by rrix2 »

manmal wrote: post #205
tadfisher wrote: post #161

Earlier quoted context omitted.

Wordpress is just low-hanging fruit for attackers. Ideally the default behavior should be to expose /wp-admin on a completely separate network, behind a VPN, but no one does that, so you have to run fail2ban or similar to stop the flood of /wp-admin/admin.php requests in your logs, and deal with Wordpress CVEs and updates. More ideal: don't run Wordpress. A static site doesn't execute code on your server and can't be…

A static site does run on a web server.

a static site is served by a webserver, but the software to generate it runs elsewhere.

Re: Why Self-Host?

#213

Post by moehm »

manmal wrote: post #205
tadfisher wrote: post #161

Earlier quoted context omitted.

Wordpress is just low-hanging fruit for attackers. Ideally the default behavior should be to expose /wp-admin on a completely separate network, behind a VPN, but no one does that, so you have to run fail2ban or similar to stop the flood of /wp-admin/admin.php requests in your logs, and deal with Wordpress CVEs and updates. More ideal: don't run Wordpress. A static site doesn't execute code on your server and can't be…

A static site does run on a web server.

Yes, but the web server is just reading files from disk and not invoking an application server. So if you keep your web server up to date, you are at a much lesser risk than if you would also have to keep your application + programming environment secure.

Re: Why Self-Host?

#214

Post by avmich »

> Big Tech and governments (like with chat control in the EU) want to shine light in every part of your personal life.

What would be a way to shine light in every part of their private life?

Re: Why Self-Host?

#215

Post by hamdingers »

turtlebits wrote: post #158
hamdingers wrote: post #127

Earlier quoted context omitted.

What kind of backup solution are you expecting? Every selfhosted app runs in docker, where the backup solution is back up the folders you mounted and the docker-compose.yml. To restore, put the folders back and run docker compose up again. I don't need every app to implement its own thing, that would be a waste of developer time.

That doesn't work for databases unless you stop the container. You'll likely end up with a corrupt backup.

Then stop the container.

A self hosted app can have a few minutes of downtime at 3am while the backup script runs.

Re: Why Self-Host?

#216

Post by mamcx »

turtlebits wrote: post #158
hamdingers wrote: post #127

Earlier quoted context omitted.

What kind of backup solution are you expecting? Every selfhosted app runs in docker, where the backup solution is back up the folders you mounted and the docker-compose.yml. To restore, put the folders back and run docker compose up again. I don't need every app to implement its own thing, that would be a waste of developer time.

That doesn't work for databases unless you stop the container. You'll likely end up with a corrupt backup.

?

Any decent RDBMS can be backup live without issues. You only need to stop for restore (well without going with complex tricks)

Re: Why Self-Host?

#218

Post by radiator »

R_Spaghetti wrote: post #58

You write: I'm fortunate enough to work at a company (enum.co) where digital sovereignty is not just a phrase. info.addr.tools shows [1]: MX 1 smtp.google.com. TXT "mailcoach-verification=a873d3f3-0f4f-4a04-a085-d53f70708e84" TXT "v=spf1 include:_spf.google.com ~all" TXT "google-site-verification=TTrl7IWxuGQBEqbNAz17GKZzS-utrW7SCZbgdo5tkk0" This is not just a phrase, it is a DNS entry. Using the most evil in phrases…

> TXT "google-site-verification=TTrl7IWxuGQBEqbNAz17GKZzS-utrW7SCZbgdo5tkk0" just to clarify, this part is not evil, it is just a compromise one makes to prevent Gmail from classifying outgoing email as spam (I think).

Re: Why Self-Host?

#219

Post by throwawaylaptop »

I operate an entire saas with 34 paying smb companies, on namecheap shared hosting. PHP/jQuery. While namecheaps time to first bit is a little longer than some, my saas is still faster than 90% of CRMs I've ever used because that was my main goal when writing it.
Post reply on HN