Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

NodeBB

  1. Home
  2. Selfhosted
  3. GitHub - SinTan1729/chhoto-url: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust.

GitHub - SinTan1729/chhoto-url: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust.

Scheduled Pinned Locked Moved Selfhosted
selfhosted
7 Posts 2 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • sintan1729@programming.devS This user is from outside of this forum
    sintan1729@programming.devS This user is from outside of this forum
    [email protected]
    wrote on last edited by
    #1

    A simple selfhosted URL shortener with no unnecessary features. Simplicity and speed are the main foci of this project. The docker image is ~6 MB (compressed), and it uses <5 MB of RAM under regular use.

    glizzyguzzler@lemmy.blahaj.zoneG 1 Reply Last reply
    0
    • sintan1729@programming.devS [email protected]

      A simple selfhosted URL shortener with no unnecessary features. Simplicity and speed are the main foci of this project. The docker image is ~6 MB (compressed), and it uses <5 MB of RAM under regular use.

      glizzyguzzler@lemmy.blahaj.zoneG This user is from outside of this forum
      glizzyguzzler@lemmy.blahaj.zoneG This user is from outside of this forum
      [email protected]
      wrote on last edited by
      #2

      Looks awesome and very efficient, does it also run with read_only: true (with a db volume provided, of course!)? Many containers just need a /tmp, but not always

      sintan1729@programming.devS 1 Reply Last reply
      0
      • glizzyguzzler@lemmy.blahaj.zoneG [email protected]

        Looks awesome and very efficient, does it also run with read_only: true (with a db volume provided, of course!)? Many containers just need a /tmp, but not always

        sintan1729@programming.devS This user is from outside of this forum
        sintan1729@programming.devS This user is from outside of this forum
        [email protected]
        wrote on last edited by
        #3

        Thanks. I had never tested this before. Seems like it throws errors. Of course, adding and deleting links don't work. But that's to be expected. But also link resolution fails since it cannot update the hit count properly. If this is a legitimate use case for you, I might work on making it work.

        glizzyguzzler@lemmy.blahaj.zoneG 1 Reply Last reply
        0
        • sintan1729@programming.devS [email protected]

          Thanks. I had never tested this before. Seems like it throws errors. Of course, adding and deleting links don't work. But that's to be expected. But also link resolution fails since it cannot update the hit count properly. If this is a legitimate use case for you, I might work on making it work.

          glizzyguzzler@lemmy.blahaj.zoneG This user is from outside of this forum
          glizzyguzzler@lemmy.blahaj.zoneG This user is from outside of this forum
          [email protected]
          wrote on last edited by
          #4

          I try to slap anything I’d face the Internet with with the read_only to further restrict exploit possibilities, would be abs great if you could make it work! I just follow all reqs on the security cheat sheet, with read_only being one of them: https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html

          With how simple it is I guessed that running as a userand restricting cap_drop: all wouldn’t be a problem.

          For read_only many containers just need tmpfs: /tmp in addition to the volume for the db. I think many containers just try to contain temporary file writing to one directory to make applying read_only easier.

          So again, I’d abs use it with read_only when you get the time to tune it!!

          sintan1729@programming.devS 1 Reply Last reply
          0
          • glizzyguzzler@lemmy.blahaj.zoneG [email protected]

            I try to slap anything I’d face the Internet with with the read_only to further restrict exploit possibilities, would be abs great if you could make it work! I just follow all reqs on the security cheat sheet, with read_only being one of them: https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html

            With how simple it is I guessed that running as a userand restricting cap_drop: all wouldn’t be a problem.

            For read_only many containers just need tmpfs: /tmp in addition to the volume for the db. I think many containers just try to contain temporary file writing to one directory to make applying read_only easier.

            So again, I’d abs use it with read_only when you get the time to tune it!!

            sintan1729@programming.devS This user is from outside of this forum
            sintan1729@programming.devS This user is from outside of this forum
            [email protected]
            wrote on last edited by
            #5

            Upon further testing, this does actually work. You may set both read_only: true, and cap_drop: all and it will work as long as you have a named volume. I had it mount a database file from the host system for my test config, which is why I was getting the errors. I don't know how to make that work though i.e. when the db is bind mounted from the host system. Setting the mount :rw doesn't seem to fix it.

            glizzyguzzler@lemmy.blahaj.zoneG 1 Reply Last reply
            0
            • sintan1729@programming.devS [email protected]

              Upon further testing, this does actually work. You may set both read_only: true, and cap_drop: all and it will work as long as you have a named volume. I had it mount a database file from the host system for my test config, which is why I was getting the errors. I don't know how to make that work though i.e. when the db is bind mounted from the host system. Setting the mount :rw doesn't seem to fix it.

              glizzyguzzler@lemmy.blahaj.zoneG This user is from outside of this forum
              glizzyguzzler@lemmy.blahaj.zoneG This user is from outside of this forum
              [email protected]
              wrote on last edited by
              #6

              Odd, I’ll try to deploy this when I can and see!

              I’ve never had a problem with a volume being on the host system, except with user permissions messed up. But if you haven’t given it a user parameter it’s running as root and shouldn’t have a problem. So I’ll see sometime and get back to you!

              sintan1729@programming.devS 1 Reply Last reply
              0
              • glizzyguzzler@lemmy.blahaj.zoneG [email protected]

                Odd, I’ll try to deploy this when I can and see!

                I’ve never had a problem with a volume being on the host system, except with user permissions messed up. But if you haven’t given it a user parameter it’s running as root and shouldn’t have a problem. So I’ll see sometime and get back to you!

                sintan1729@programming.devS This user is from outside of this forum
                sintan1729@programming.devS This user is from outside of this forum
                [email protected]
                wrote last edited by
                #7

                It was just a matter of setting the correct user. In most cases, user: 1000:1000 should fix it.

                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Login or register to search.
                Powered by NodeBB Contributors
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • World
                • Users
                • Groups