Here ForAwhile / nanogram · GitLab
gitlab.com
GitLab.com

Documentation for nanogram available here for awhile

Edit: Dont be a ungrateful Be nice pls. I put a lot of time, effort, and my own money into making this. I’m choosing to freely share it :)

Yes I get help from LLM’s. Review the code if you think it’s unsafe, or just move on and don’t use it. Happy to answer any technical questions.

Edit 2: Expanded source code for termux version here.

Edit 3: Expanded source for pi version here

    • CameronDev@programming.devEnglish
      7·
      1 day ago

      Sorry, but a photo of a directory structure is not a source tree.

      Your git repo consists of 4 files, a readme, a licence, and two packed shell scripts.

      If you have an actual published source repo, link people to it.

      • hereforawhile@lemmy.mlOPEnglish
        15·
        1 day ago

        So just a expanded file structure directory is what you want? The script executable expands to each individual piece once run.

        What do you mean a actual published source repo? I do not understand how its not that. Everything is packaged into one script.

        • CameronDev@programming.devEnglish
          6·
          1 day ago

          Yes. Separate out each part out. You are currently publishing the equivalent of of a compiled binary. Split it up, and use a script to “compile” it back into the mega shell script.

          It means that changes to each file can tracked (and audited) individually, you can conditionally compile bits in or out, and most usefully, you can write tests for the individual components.

            • SteveTech@aussie.zoneEnglish
              1·
              22 hours ago

              You can still have that script, but put it on the releases page. Git works best with actual source code and it doesn’t belong there. You should also add an extra script that generates one of those ‘compiled’ scripts to the git repo, so that people can do it themselves.