• 1 Post
  • 40 Comments
Joined 2 days ago
cake
Cake day: January 28th, 2025

help-circle

  • Its nice and pretty nerdy. As web based nmarkdown editor in pretty good and the extra features rocks.

    It has a few quirks I don’t like though, on the self-hosted side:

    • no multi-user support.
    • auth is quirky and required a ticket to make it work at all
    • must be deployed on subdomain, which make it impossible to host multiple instances for multiple users easily

    But from functionality point of view, I love it
















  • No, the router being the SPOF (single point of failure) is totally avoidable.

    At mny home (no SaaS services offered, but critical “enough” for my life services) i have two different ISPs on two different tecnologies: one is FTTC via copper cable (aka good old ADSL successor) plus a WFA 5G (much faster but with data cap). Those two are connected to one opnSense router (which, indeed, is a SPOF at this time). But you can remove also this SPOF by adding a second opnSense and tie the two in failover.

    So the setup would be:

    • FTTC -> ISP1 router -> LAN cable 1 to port 1 of opnSense n.1
    • FTTC -> ISP1 router -> LAN cable 2 to port 1 of opnSense n.2
    • FWA -> ISP2 router -> LAN cable 1 to port 2 of opnSense n.1
    • FWA -> ISP2 router -> LAN cable 2 to port 2 of opnSense n.2

    Then in both opnSense i would setup failover multi-WAN and bridge them together so that one diyng will trigger the second one.

    edit: fixed small errors