swizzin was designed to be an easy to use, modular seedbox solution.
We only support Debian and Ubuntu LTS (Long term support) systems. Explicitly, that means the following:
- Debian 9, 10 and 11
- Ubuntu 18.04 and 20.04
- A KVM VPS or bare metal server is recommended
- 2+ CPU cores KVM or Intel Atom c2750
- 4 GB of RAM
- A processor compliant with one of the following architectures is required:
amd64e.g. any modern computer/server
arm64e.g. Apple Silicon, Raspberry Pi 2 v1.2 or newer (ARMv8)
With the exception of the processor architecture, these are not hard and fast requirements -- you may find that you're able to get away with running on a weaker CPU or less RAM; however, best performance will be had if the applications you're using have ample resource overhead.
Make sure you have either
wget installed. Pick the command of your choice to get started:
bash <(curl -sL git.io/swizzin) && . ~/.bashrc
Please note that if you are running Ubuntu and choose to run the initial setup though
sudo you should include the
-H argument to ensure that your home directory is modified to /root when you sudo up. The installer will take care of this for you, and this should be the only time you need to specify
sudo -H before running a swizzin command.
sudo -H su -c 'bash <(wget -O- -q https://git.io/swizzin-setup)'
After running the above command, the script will check for updates and install some necessary prerequisites before continuing.
When finished, the installer will ask you a few questions:
- A username for the master user
- A password for the master user
- The packages you would like to install
In text fields, you only need to enter your text and hit
return to enter. To choose packages, from the list, you can navigate with the arrow keys. Press
space to select an entry. When you're satisfied with your selection, press
tab to move the selector to
Ok and then press enter. This will advance the screen.
When you have finished running through the prompts, installation will start. The time it takes will depend on the number of packages you have selected.
There's a whole bunch of options for the setup.sh to achieve custom/unattended setups, which you can read all about in this guide.
A few items to be aware of as known issues. Most of these have had attempts at working around them, but it's good to be aware of things to avoid:
- Installer appears frozen before any user input (usually on
apt update && apt upgradebefore running the installer.
- Capital letters in usernames: capital letters should never be used for usernames
- Usernames which may conflict with a group that already exists: for example, certain images like AWS may have an
admingroup out of the box. If you try to name your user
adminthe install will fail in this case.
If you're having troubles with any of the items in the documentation, please first consult the Troubleshooting guide. If that is not enough for you, join us in Discord and we will attempt to help you to our best ability.
If you have found a bug or are having an issue, please open an issue on GitHub.