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
OpenWRT support on GL.inet devices seems to be complex. The following is my understanding of the situation.
GL.inet have an OpenWRT fork on GitHub https://github.com/gl-inet/openwrt This is what is installed on GL.inet devices.
The OpenWRT developers in due course try to work out how to port mainline OpenWRT onto OpenWRT onto GL.inet devices.
Yes. My experience with the gl-inet device I have was that initially the fork was good enough and when the company didn't update it much anymore, it was very easy to reflash the device to a main-line OpenWRT version. It's now working great with the latest mainline version despite being quite old already.
This seems to have worked for the older devices, but I don't know about the newer devices, for example far as I can tell the "Flint" doesn't have mainline support despite being over a year old.