It expects that you have read the instructions carefully and claims no responsibility to any damage done, but you can report issues. This project's intended purpose is to have your system in a state with files preconfigured for a great user experience, For a unified distribution with the intent of fulfilling consumer/user usage without having technical experience or using terminals.
| Software | Purpose | Extra notes |
|---|---|---|
| Tailscale | Remote networking without port forwarding | Provides a seamless networking experience. You can MoSH, host servers and even access your home network with it. Essential for home-labbing, server hosting and remotely accessing an ARPAnet |
| PlayIt.gg | Port forward an IP publicly without fees | Allows for a public IP that can be accessed/used by anyone on the internet, whether it be game servers, SFTP, anything |
| Sunshine/Moonlight | Remote Desktop | High Performance remote GUI(desktop) access wiht minimal latency. You may use w/Tailscale to get an experience like Chrome Remote Desktop. |
The executable file's location is /opt/playit/playit
/etc/playit/playit.toml should not exist prior to execution of the command below, as it can cause issues. For setup run this:
/opt/playit/playit --secret_path /etc/playit/playit.toml start
Error? Delete /etc/playit/playit.toml and try setup again. A systemd service autostarts it at startup if the executable is found.
Host your own Minecraft Server on your PC.
Note: For a vanilla experience, Bedrock is heavily recommended You server folder's contents go in
/opt/mc-server/mc-server
And the main binary is to be called mc-server
Want mods only possible to use on Java? Use server software like FabricMC alongside mods like Lithium, GeyserMC and Floodgate to get started.
Prioritize Flatpaks over Native packages. Flatpaks are for user apps, mainly GUIs. It makes sense for things like libreoffice, Blanket or something like that. They just get installed, work fine, do not require a reboot. However, if you need system integration go with RPM-OSTree at your own risk, or try a Distrobox container. They allow for better system integration and performance, but you risk dependancy hell and more complex system updates. Keep it mainly for things the user doesn't see, like daemons. Are you a developer, just go ahead with a Distrobox container for your dev envioroment. There is no one stopping you from using proprietary software, you should compare the application in itself, not the development model. Same base/framework, yet no limit to visual theming/customization, one of the things I belive in. Make hundreds of rices, but maintain the same code base/framework.
| Name | Description | ID |
|---|---|---|
| BOINC | Help with contributing to science with idle power | boinc-client boinc-client-static boinc-manager |
| Docker | For containerization and BOINC | docker-cli |
| TLP | A daemon that makes system calls to actively save power, while keeping the same system performance | tlp tlp-rdw |
| Name | Description | ID |
|---|---|---|
| Tor | Access the unrestricted internet and get around censorship, and help others do the same | org.torproject.torbrowser-launcher io.frama.tractor.carburetor |
| Chrome Dev | A great browser for everyday usage and productivity | com.microsoft.EdgeDev |
| Vesktop | BetterDiscord-ish app | dev.vencord.Vesktop |
| Telegram | Yup, conduct your “activities” there |