5 ms·

Thats the problem without self-hosting your essential stuff.

by gsich 8y ago

gtsteve 8y ago
I don't see it as too much of a problem so long as you're not one of those teams that orchestrates their deployments using a Slack bot. Just make sure you have an agreed backup mechanism, i.e. Google Hangouts, Zoom, etc.
borplk 8y ago
self-hosting doesn't imply automatic and better uptime than the hosted version. most people are much better off letting dedicated teams of tens of people take care of the hosted version for them.
strunz 8y ago
Funny, our self-hosted infrastructure goes down weekly.
- slenk 8y ago
  No offense, but you're probably doing it wrong
  - FooBarWidget 8y ago
    You just gave a good argument of why s/he should use Slack. Yeah s/he might be doing it wrong, but so what? One should focus on core business, not system administration.
    - Dirlewanger 8y ago
      Yup, every time one of the popular centralized XaaS platforms go down, there's always the snarky "Heh, well my stuff is self-hosted...", and they are always the types that have no idea how to value their time.
peeters 8y ago
Reasons my self-hosted servers have gone down in the past year: - Scheduled electrical maintenance that facilities manager failed to disclose (even though they knew about it for weeks). - Emergency power-down because two of the four air conditioners failed at the same time. - Someone accidentally powered off the VM. I'd much rather have an hour long outage here and there than incur the cost of defending against these circumstances (and still have it go down for some new unforeseen reason).
- gsich 8y ago
  >- Someone accidentally powered off the VM. how is that self-hosting when you don't control the hypervisor in this case? it usually implies that you at least have some sort of control. either having a real server somewhere (with ups and stuff) or at home, where you know when power is out. while what you are doing is technically self-hosting, I would have changed the VM provider after the first incident like you described.
rayvd 8y ago
Less blowback typically when you can blame a third party though.

Thats the problem without self-hosting your essential stuff.

by gsich 8y ago

Thats the problem without self-hosting your essential stuff.

I don't see it as too much of a problem so long as you're not one of those teams that orchestrates their deployments using a Slack bot. Just make sure you have an agreed backup mechanism, i.e. Google Hangouts, Zoom, etc.

borplk 8y ago

self-hosting doesn't imply automatic and better uptime than the hosted version. most people are much better off letting dedicated teams of tens of people take care of the hosted version for them.

strunz 8y ago

Funny, our self-hosted infrastructure goes down weekly.

slenk 8y ago
No offense, but you're probably doing it wrong
- FooBarWidget 8y ago
  You just gave a good argument of why s/he should use Slack. Yeah s/he might be doing it wrong, but so what? One should focus on core business, not system administration.
  - Dirlewanger 8y ago
    Yup, every time one of the popular centralized XaaS platforms go down, there's always the snarky "Heh, well my stuff is self-hosted...", and they are always the types that have no idea how to value their time.

peeters 8y ago

Reasons my self-hosted servers have gone down in the past year: - Scheduled electrical maintenance that facilities manager failed to disclose (even though they knew about it for weeks). - Emergency power-down because two of the four air conditioners failed at the same time. - Someone accidentally powered off the VM. I'd much rather have an hour long outage here and there than incur the cost of defending against these circumstances (and still have it go down for some new unforeseen reason).

gsich 8y ago
>- Someone accidentally powered off the VM. how is that self-hosting when you don't control the hypervisor in this case? it usually implies that you at least have some sort of control. either having a real server somewhere (with ups and stuff) or at home, where you know when power is out. while what you are doing is technically self-hosting, I would have changed the VM provider after the first incident like you described.

rayvd 8y ago

Less blowback typically when you can blame a third party though.