I want to host my website in my raspberry pi, I’ve read that I would need a web server software for this. Which one do you recommend? It won’t be a complex website.

  • d_k_bo@feddit.deEnglish
    27·
    1 年前

    Caddy! It has HTTPS built in and provides simple but powerful configuration with sane defaults.

    Example Caddyfile for a static file server:

    example.com {
	root * /var/www
	file_server
}

    I used nginx in the past, but didn’t like it’s verbose config files.

    • psykon@kbin.social
      9·
      1 年前

      +1 for Caddy. It’s my default webserver and reverse proxy. Built-in Https and the fact that I can get it up, running and configured in a matter of minutes are the main reasons.

  • Shimitar@feddit.itEnglish
    181·
    1 年前

    Nginx! Simplex essential and easy.

    Unless you need to rely a lot on CGIs then apache maybe is better.

  • 2tapry@lemmy.nzEnglish
    8·
    1 年前

    nginx

    Not sure why others are suggesting a Raspberry Pi and nginx would cause problems? I run three public facing websites on a single Raspberry Pi 4 with 2GB RAM. Has been working flawlessly for 2 years. Typical uptime is measured in multiple months.

    Running Wordpress, fail2ban and certbot. Booting and running of a USB drive - have considered SSD but no need as I cache to RAM for performance.

  • vegetaaaaaaa@lemmy.worldEnglish
    91·
    1 年前

    Apache, the OG HTTP server. Fast, well documented, battle-tested, FOSS and community-led (unlike nginx which is corporate-led). People will tell you that nginx is “faster” but never point to actual benchmarks. Both are ok.

    • slip@818.galleryEnglish
      2·
      1 年前

      Yeah apache is awesome. Lots of settings if u want, and every question I’ve ever asked and probably am yet to ask has already been answered on stack with multiple duplicates aha

      • vegetaaaaaaa@lemmy.worldEnglish
        1·
        1 年前

        Check out mod_md - this module allows getting certificates from Let’s Encrypt (or any other ACME cert provider) automatically. Just set this anywhere in your config, reload apache and you’re set. No more fiddling around with certbot.

        MDCertificateAgreement accepted
MDContactEmail me@example.org
MDomain my.example.org

        Also other comments make it look like only nginx supports FastCGI (e.g. php-fpm), apache has supported talking to FastCGI since 2005:

          <FilesMatch \.php$>
    SetHandler "proxy:unix:/run/php/php8.2-fpm.sock|fcgi://localhost"
  </FilesMatch>
        • slip@818.galleryEnglish
          1·
          1 年前

          Yeah I use php-fpm, I didn’t know much about it the first time I installed it, I just needed it for HTTP 2.

          For ssl I just install certbot and let it autorun LetsEncrypt, I haven’t had any issues with any of my ssl certs, it’s pretty nice.

          The age old LAMP stack is pretty solid, except for me it’s LAPP cuz I don’t wanna use mysql.

    • rambos@lemmy.world
      32·
      1 年前

      There is a NPM (nginx proxy manager) with rly nice GUI that you can run in docker container

  • hitagi@ani.socialEnglish
    5·
    1 年前

    Caddy was my first and it’s very easy to use. I use nginx nowadays because I heard it scales better. It’s harder to use but manageable enough.

    Depending on the type of website you’re hosting, you can probably just use Cloudflare pages or Netlify instead of hosting it at home with a Pi.

  • SniffBark@lemmy.worldEnglish
    4·
    1 年前

    I have recently started using Caddy and I love it! FOSS, automatic HTTPS, super easy to setup and works well as a reverse proxy. As your website will not be complex, the Caddyfile would be just a few lines.

  • Matt The Horwood@lemmy.horwood.cloudEnglish
    3·
    1 年前

    I only use nginx now, the out of box footprint is tiny.

    add this deb https://packages.sury.org/nginx/ bookworm main to your /etc/apt/sources.list to install the latest stable

  • Qazwsxedcrfv000@lemmy.unknownsys.comEnglish
    3·
    1 年前

    Is your site static or dynamic? If your site is made of good old HTML and CSS or your site is a SPA, any web server will serve it well.

    I prefer Nginx as it is performant and versatile enough for most use cases.

      • Qazwsxedcrfv000@lemmy.unknownsys.comEnglish
        11·
        1 年前

        If your dynamic pages leverage PHP, Nginx can be configured to support that via FastCGI. If your site has its own server runtime (e.g. a site written with NodeJS or Go), Nginx reverse proxy is literally its strength. So yeah give Nginx a try. I bet you won’t regret it.