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
Just wondering, as this is the second post I see you do like this, why not use git and a forge (codeberg, gitlab, github), to publish these projects, with proper file separation, a nice README with descriptions and instructions and a proper OSS license?
I thought about it but it's not worth tieing accounts together to me and I don't wanna make throwaway accounts just to share.
To small of scale I'm just messing around is the short answer.
Usage is commented at the start of the script. Just save it, chmod, run it and it spins it self right up.
What are the downsides of sharing code with no license?
The TL, DR version of sharing with No License, is that technically speaking you are not explicitly permitting others to use your code in any way, just allowing them to look, a license is a formal way to give permissions to others to copy, modify, or use your code.
You don't need an extra file for the license, you can embed it on a section at the top of your file, as you did with the description, just add a
# License
section at the very top, if you want the most permissive one you can just use MIT, just need to replace the year of publication of the code, and you can use a pseudonym/username like 'hereforawhile@lemmy.ml' if you don't want to use something like email, username on another site or real name, that can be used to identify you, if that's a concernThankyou that's really helpful 👍
It didn't used to be this way. You used to apply for copyright like a patent. Rich people stole content from poor artists that didn't have the lawyers to file copyright. This broken system has been reformed. Nowadays, if you create something, you automatically own the copyright. You now have to "opt out" of copyright with an explicit license to "release" the rights. Much better system.
Yet enforcing your copyright is exclusive to the rich. I had to move off of GitHub because of Microsoft infringing my code licenses and selling them as "GitHub Copilot", and I have no way of fighting back/recover my losses.