• The author switched from using OpenLiteSpeed to Nginx for hosting a weather forecasting website.
  • The website experiences spikes in traffic during severe weather events, requiring additional preparation.
  • OpenLiteSpeed was initially chosen for its integrated caching and speed, but the complexity and GUI configuration were challenges.

Archive link: https://archive.ph/Uf6wF

  • TCB13@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    edit-2
    10 months ago

    they have config files, but they suggest using the gui for beginners. I don’t know. WTF!!

    They don’t because OLS is an entry level product, kind of a technology demo. Their real thing the the LiteSpeed Enterprise that has way more features and is tightly integrated with other solutions such as CloudLinux and WHM/cPanel.

    But there is a point when someone wants to split up different types of web applications, for instance some of them need node, the others need php or something entirely different that would conflict with the other two. This way configs can be changed during a deployment in production while others don’t need to be touched and unaffected services are not interrupted not even for a very short time.

    Yes there is, but not in this context. I specifically said time and time again that LS was good for shared environments / shared hosting NOT the “singular developer” use case you’re describing. The blogger also seems to miss this very important detail.

    But well you both may be missing that detail because you never had to deal with shared hosting so you don’t see how LS is really the only other solution whenever Apache isn’t enough.