Selfhosted

62088 readers

161 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

-18

Here is a more polished release of nanogram. Fully compatible on raspberry pi now. (gitlab.com)

submitted 8 months ago* (last edited 8 months ago) by hereforawhile@lemmy.ml 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

[–] CameronDev@programming.dev 10 points 8 months ago (1 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.

[+] hereforawhile@lemmy.ml -9 points 8 months ago (1 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.

[–] CameronDev@programming.dev 11 points 8 months ago* (last edited 8 months ago) (1 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.

[–] hereforawhile@lemmy.ml 2 points 8 months ago (1 children)

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

[–] SteveTech@aussie.zone 2 points 8 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.