Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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!
view the rest of the comments
Any links to the actual sources and not just random proton links?
Github comes up with a file-based build system for tup.
Same thought here, why uploading it to proton drive? github isnt evil that they trying to snatch that code or whatever. If you are so cautious then ramp up a gitea or gitlab self hosted instance up.
You are welcome to upload it to any git instance you want, I'm not interested in leading an open-source project like this
It is not about leading anything but about having the code in a repository so that it is easy to read/consult/audit/etc.
You can upload the code to any service (it doesn't have to be GitHub, it can be GitLab, sourcehut, etc...) and disable issues and comments.
You can upload the code to any service as well
You're right, OP. Just dumping it somewhere is acceptable. It doesn't make it very accessible for other people. But since you're not planning to maintain it or make it easy to use for other people... It's alright. Most important thing is to include a license file or it can't be used. But that's it.
Yes thanks, it has a UNLICENSE file included, for anyone interested you can read more at https://unlicense.org/
Well, whoever is developing it should publish the code somewhere...
I developed it and I'm sharing it through Proton Drive only
Then you don't welcome contributions. So this is dead in the water for me.
Anyone is welcome to contribute and upload their contributions on any platform they want
What's the license on it then? Can I just fork it?
https://unlicense.org/
Public domain
Yes you can fork
Those random proton drive links are the sources, and only the sources
If you want people to take you seriously about being open source, you need to have a git repo, like github, gitlab, etc. you can even self host one. Heck, you can even use a different (non git) DVCS, but not just a link to a cloud drive...
No I don't need to have a git repo, if someone can't take something that's not on a VCS serious it is there problem, not mine
I let the code speak for itself
Do you think no one took Linux serious because Linus uploaded it to a FTP? It is how a lot of code always have been released
yeah.... no. red flags galore. Why should anyone trust you if you don't trust version control.
Using Linus as an example is interesting... Who the fuck do you think created git?
If you don't want to use github, that's fine, you have sr.ht, and https://savannah.gnu.org/ as good (and libre free options)
Code smells and maturity are signals people use to determine if they want to use/fork/work on a project. Not having source control is a great way to give yourself a headache over time.
I never said anyone should trust anything, in fact I believe no one should trust me, that is why there are no binaries included, just raw sources to examine and compile yourself
I'm fully aware of that he also created git, over a decade after, and it has nothing to do with the trusting of Linux, in fact Linux huge size and interest was the reason he created git, it was well trusted long before git, so your point is garbage
Garbage in - Garbage Out
I look forward to the next version of your project called tup_new, tup_usethisone, tup_fixed_fixed_fixed
You obviously didn't even look at the links this time so you won't probably care for the next either
I did, i saw you had you unlicense in the root directory, that you had md files dotted around which tells me you ARE using a source control system internally, or at least with lots of domain experience of using one.
Oh jeez, md files are proof that I use source control internally?
No I don't, but you are free to believe that
I've got experience with them ofc, would that be a reason I must use one every time?
not proof, but a indicator...
Anyway, since your aware of the use of version control I find your anti-versioning stance perplexing, but regardless, you created a open source thing, making the world a better place, thank you for that.