I am currently using Hugo as a static site generator for my blog. It’s not bad but rather limited. Does anybody know about something that would be equally as lightweight but offer some more flexibility. I just don’t know what is out there so anything you guys could come up with would be appreciated.

    • Meow.tar.gz@lemmy.goblackcat.comOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      The only limiting factor is really that if I am, say, in a public place that bans SSH access or SFTP access. I am starting to see more of this as deep packet inspection becomes available to the masses now. I could be composing my blog post on my laptop but be unable to otherwise publish it if I am on such a network that combines deep packet inspection with locking down ports.

      • TechnologyClassroom@partizle.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        You could also have your back end pull from a git repo every minute. A cron job could check a GitLab repo for changes and update the site if any changes are found.

      • TechnologyClassroom@partizle.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        That is a networking issue which is not specific to Hugo. You need to solve this as most of the suggestions also involve SSH.

        One way is to use a VPN like openvpn or wireguard that can use a common port like 80 or 443.

        • Meow.tar.gz@lemmy.goblackcat.comOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          No, of course it is not specific to Hugo. Solid point on OpenVPN because I forgot it can use TCP. However, does OpenVPN’s negotiation look like a TLS handshake from a browser to a client? Again, deep packet inspection is my enemy here.

          • TechnologyClassroom@partizle.com
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            Deep packet inspection is unlikely the culprit in my experience. SSH and SFTP use port 22 by default which is probably blocked. I log in to my work VPN through common ports 80 and 443 on public WiFi.

            • Meow.tar.gz@lemmy.goblackcat.comOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Actually, you’re mistaken because I’ve set SSH and SFTP to use the port for IMAPS which is 993. I know that Dunkin Donuts, for example, offers guest WiFi. They have port 993 open because I can send and receive email from my phone. My email provider is Hostinger for reference. However, when I try to SSH into my server over the 993 port it fails when it should not. I have verified that 993 is not firewalled and that the SSH daemon is listening for connections on port 993. What else could it be other than a firewall analyzing the TCP handshake and seeing that it is not email, http, or https traffic? If I am wrong please educate me.