• 1 Post
  • 377 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle








  • They can still have support contracts and SLA etc from slack.
    It’s just that the servers slack runs on are on-prem and completely controlled by the business buying into the self hosted licence.
    The benefits should be tighter security (say, can only be accessed via VPN), and for many many MAU probably lower costs. Chances are, Disney already has datacenter ops and hardware contracts.

    And why choose slack? For quite a while, it was extremely common for developers (maybe even industry standard?). It had loads of features in the small market of internal chat programs. And it’s easy to build extensions and integrations for.

    I’m not saying that Disney is running on-prem slack, but I wouldn’t be surprised if they were


  • Transfering a domain from one registrar (IE reseller) to another can be a pain, but yes you can - it normally involves a fee and manual actions from the registrars.
    As long as the new registrar supports the TLD. A few Geo-TLDs can only be resold/managed by some registrars.

    The easiest thing to do is to point the domain at ClouDNS nameservers.
    Make sure you are happy with ClouDNS (I’ve never had issues with them) etc before committing




  • Nginx Proxy Manager is probably perfect for you.
    Pick a domain (like mylab.home or something), set up your home network to resolve that domains IP as your docker hosts IP.
    NPM will do self-signed certs. So, you will get a “warning, Https is insecure” kinda page when you visit it. You could import NPMs root cert into your OS/browser so it trusts it (or set up an “don’t warn for this domain” or something).

    If you don’t want per-client config to trust it, then you need to buy a domain, use a DNS that supports letsencrypt DNS-challenge, and grab certs that way (means you don’t need a publicly accessible well-known route exposed)