-19
Here is a more polished release of nanogram. Fully compatible on raspberry pi now. (gitlab.com)
submitted 10 months ago* (last edited 10 months ago) by to c/selfhosted@lemmy.world
32 comments fedilink hide all child comments
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] 9 points 10 months ago (6 children)

I dont understand why people do this

Charitably: AI turbocharged dunning-kruger

Less charitable: Malware delivery.

There is no good reason why they couldn't have a normal source tree, that they pack into a single shell script in CI.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] [S] -4 points 10 months ago (5 children)

    Here is the source tree.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 10 points 10 months ago (4 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [+] [S] -9 points 10 months ago (3 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 11 points 10 months ago* (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 2 points 10 months ago (1 child)

    Ok I'll work on it and share when I am done

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 10 months 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.

  • permalink
  • fedilink
  • source
  • parent