I guess I don’t understand. You followed the docker installation directions correctly and it didn’t work or you modified the directions in a way that you prefer and it didn’t work?
Admin: lemux
Issues and Updates: !server_news
Find me:
mastodon: @minnix@upallnight.minnix.dev
matrix: @minnix:minnix.dev
peertube: @minnix@nightshift.minnix.dev
funkwhale: @minnix@allnightlong.minnix.dev
writefreely: @minnix@tech.minnix.dev
I guess I don’t understand. You followed the docker installation directions correctly and it didn’t work or you modified the directions in a way that you prefer and it didn’t work?
I have it installed for a few years now. I started with the AIO but moved to the separate container install after AIO was deprecated. I imagine the install process is too complex for portainer. https://docs.funkwhale.audio/stable/administrator/installation/docker.html
I did steps 1-4 and skipped the rest because I already have a proxy server running. Don’t remember anything related to snapd though. Mine is running in a Debian 11 VM on proxmox instead of an LXC, but the process should be the same. Also they have a matrix channel for help https://matrix.to/#/#funkwhale-support:matrix.org
From what I remember it was relatively painless to install, but upgrading can be a chore, especially this last upgrade. My main interest in FW was the federation aspect as far as finding new music. If you don’t care about federation, maybe a simpler option would work better for you.
At the very least you need to install a webserver and you need a proxy of some kind. If you truly want old school you can just create html pages hosted from the root of your webserver (although there are now easier modern ways to do this, you might learn more the classic way rather than using a CMS).
You will want a reverse proxy to lie between your webserver and the internet that handles SSL. Let’s Encrypt is a good option to generate a cert so that you only expose port 443 on your router to the internet and your webserver. You’ll have to open port 80 to generate the cert but can close it again once generated. Then you will have https.
That’s the basics. The how-to’s are easy to find online.
I’m not sure how soon you need this, but if you can wait sipeed has a $20 kvm with ATX control that should be out soon https://lunar.computer/news/sipeed-announces-new-20-risc-v-kvm-device/
There’s an interesting book I read recently related to this called The Anxious Generation: how the Great Rewiring of Childhood is Causing an Epidemic of Mental Illness. I’d recommend it.
As a counterpoint, EFF put out this article today: The Surgeon General’s Fear-Mongering, Unconstitutional Effort to Label Social Media
I am using Kinoite for quite a while now and not once did layering break anything.
That’s great for you. Not everyone may use their distro in the same way as you.
https://discussion.fedoraproject.org/t/is-silverblue-rpm-ostree-intended-to-be-used-with-layered-packages/26162/2 https://discussion.fedoraproject.org/t/fedora-silverblue-36-will-not-succesfully-deploy-after-layering-packages/77502/3 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/991 https://github.com/coreos/rpm-ostree/issues/4280
Not to mention the whole Firefox debacle of including an outdated borked version based with the system install instead of just moving to Flatpak install of most recent stable release. There’s a very valid reason why package layering is discouraged by atomic maintainers and why toolbox is there by default as part of OS. And don’t even get me started on DKMS and driver installation.
So, the points in favor of Kinoite is sticking closer to upstream, however it seems like I would need to layer quite a few packages. My understanding is that this is discouraged in an rpm-ostree setup, particularly due to update time and possible mismatches with RPMFusion
It’s not only discouraged but often times it’s system breaking. I used Kinoite for a year before I just became too frustrated and gave up. The first thing I learned though was to stay away from package layering because it tended to break things more often than not. Basically if you can’t find or build a flatpak and you don’t want to use toolbox all the time, just stick with workstation. Immutable is great when deploying to multiple servers or locked-down corporate workstations, but it makes no sense for your personal setup especially if you’re already familiar with Linux.
Not every room or space will be hosted by someone self-hosting their server. I find it kind of appalling that this would be the solution. It’s certainly not what I’ve heard from people working on projects around moderation.
This is somewhat the goal, but without the hyperbole. Homeservers will be hosted by individuals or orgs, but will contain many rooms and spaces each. In 2020 there were over 20,000 homeservers. That number has without a doubt grown exponentially. The concept is the same with Mastodon. If you are worried about moderation on the matrix.org homeserver there are many lists of public homeservers across the web. Many people research homeservers to see if they are a good fit for them just as they do Mastodon instances.
This blog post gives a good idea of where matrix is heading. Notice their mission of decentralization.
Since agglomeration around a single instance is against the goals of Matrix and its Foundation, users need to have a way out and incentives to move.
We are committed both to making Matrix more accessible, and to doing the work to decenter the Matrix.org homeserver.
Matrix.org is meant to be an entry point, not a stopping point. As to your concern regarding built-in tools, matrix is just a spec, an open source federated communication protocol based on HTTP. The community builds tools. Matrix is not discord. In fact it is in opposition to the discord philosophy of centralization, data mining, advertising, and AI training.
It sounds like you are more concerned with the matrix.org homeserver than matrix itself. Matrix.org homeserver will eventually go away for personal use, this is the plan for the future. Matrix has always kept this homeserver open as proof of concept, but has not planned to keep it open forever as the goal is the widespread adoption of the protocol and for people and orgs to host their own servers and build tools using matrix.
The bullet points you listed are all currently able to be realized on any self-hosted homeserver.
I’m curious as to how you would improve the mod tools Lionir. I have found mod/admin tools and especially Mjolnir to be quite good.
Just keep in mind that even with a jetson board you’ll need one of the higher memory configurations to have a non-frustrating stable diffusion experience. 32-64GB like the Orin and those aren’t cheap. The nanos just don’t cut it without severe optimizations and very long generate times.
Elaborate on why samba is bad when it comes to security? Like list a bunch of links like this or write a paragraph summarizing them like a chatbot?
NFS does symlinks but they have to be configured correctly.
Samba may have not given you issues in the past, but it also doesn’t give you any security.
Also never use samba. At the very least use NFS.
It seems to be quite a lot for the server it’s hosted on though (which is not the snappiest).
I’m working on it
It’s extremely light to run, and very easy to install and upgrade. I ran one for just myself without open registrations. The only con is that the community (self-hostable) version doesn’t allow js due to “safety reasons” so in order to have something like comments for your blog you have to either perform several janky CSS hacks or adjust the source code yourself. The only reason I chose wf was because of federation, but I eventually switched to standard WordPress with the federation plugin and now have comments and whatever else I want.
I see your point but you can call out China’s Uyghur genocide while still being against forced labor in other parts of the world.
I started using Frigate and thought about going the Coral route but realized you didn’t need them if you have a relatively recent Intel CPU (6th gen or newer) as OpenVino with the iGPU is pretty much on par https://github.com/blakeblackshear/frigate/discussions/5742 .
A lot of the newer SBCs are being shipped with integrated NPUs/TPUs now as well. I would get a Coral if I were to use an older SBC or RPi or older PC as a camera server for object detection. Currently I have an ESP32-CAM watching a bird feeder but that feed goes to a modern server for bird species recognition but I could see a Coral as an option.
I like Librum for reading, as far as finding https://lemmy.ml/c/piracy may know
Consequences will never be the same