Capsules - Bytesized Hosting Wiki
"A new platform, Aethernal, is in Beta now. It’s made for people who want more freedom to choose, whether that be software or hardware resources. It also includes a new open-source app management system called Aethernal Agent."
Please see Introducing Aethernal Capsules to read the rest of the product announcement and additional information.
Aethernal Agent is open-source, you can find the code on GItlab.
We are constantly improving both the website and the Aethernal Agent. For updates on both see this dedicated changelog page.
This is systemctl wrapper designed to make it easier to manage your services, including checking their status and restarting them.
aa-cli help services will output:
Commands: aa-cli services help [COMMAND] # Describe subcommands or one specific subcommand aa-cli services list # Lists all available user services and their status. aa-cli services restart APP # restart the supplied application via systemd aa-cli services start APP # start the supplied application via systemd aa-cli services start-all # Start all systemd managed applications aa-cli services status APP # get the status of the supplied application via systemd aa-cli services stop APP # stop the supplied application via systemd
Because Capsules come in all shapes and sizes it's almost impossible to give a cut and dry optimised-ready client. This is why all clients use default settings. These settings are not optimised. You will have to go in and tinker with it yourself to get the best settings for your Capsule. If this is not something you want to do please consider getting our pre-optimised Appbox.
To optimise Deluge start by downloading and installing the LTConfig plugin. This will allow you to make changes to libtorrent to optimise the performance for your Deluge. It's our recommendation to start with the "High Performance Seed" preset and tweak from that if needed. Do know that if you have a Capsule on the low-end of the spec (1 core) it might cause your Capsule to run out of memory and start killing processes.
To optimise rTorrent take a look at this elaborate tweaking page.
If you get an error installing Docker images then please use
sudo docker login and login with your Docker hub account. This increases the rate limits to 200 per six hours. This only works starting aethernal-agent 0.3.7 so make sure you are on this version.
Cause appears to be the Process ID being left behind after app shutdown. Add the below line to the Service section of your ~/.config/systemd/user/medusa.service file to fix:
Reload the updated file by executing the following command:
systemctl --user daemon-reload
The updated ~/.config/systemd/user/medusa.service should look as below:
[Unit] Description=Medusa Daemon After=network.target [Service] Type=forking ExecStart=/usr/bin/python3 %h/apps/medusa/start.py -q --daemon --nolaunch --pidfile %h/.config/medusa/.medusa.pid --datadir=%h/.config/medusa TimeoutStopSec=25 KillMode=process Restart=on-failure PIDFile=%h/.config/medusa/.medusa.pid [Install] WantedBy=default.target
If still not working, try running manually as user with:
systemctl --user start medusa
You can only change resources once per day.
Allows you to add and change the port forwarding rules. If you have ever setup forwarding rules on your home NAT internet router, this is similar in concept. For example the default port for the SSH service is port 22 which the installed server within the capsule is configured to listen on. The Host Port will be a high port number that is external reachable which you would configure your SSH client to connect to, which would automatically forward on to port 22.
If you find that the server doesn't come back online after performing a
sudo /sbin/shutdown -r now refresh the dashboard and try a Start Capsule or Restart Capsule form the main Capsule actions menu on the top right.
Tautulli 2.6.3 is the last version to support Python 2. Python 3 will be required to continue receiving updates.
- Make sure Tautulli is shutdown from the dashboard or via the command
aa-cli service stop tautulli.service
- Edit ~/.config/systemd/user/tautulli.service
- Add the path to the python3 interpreter to the start of the ExecStart=
The updated line should look something like:
ExecStart=/usr/bin/python3 %h/apps/tautulli/Tautulli.py --config=%h/.config/tautulli/config.ini --datadir=%h/.config/tautulli
- Reload the updated unit file by executing the command
systemctl --user daemon-reload
- Start Tautulli from the dashboard or via
aa-cli service start tautulli.service
More to follow
- Familiar with Linux command line strongly recommended....
- Scope of support similar to VPS...
- Key differences to AppBoxes and other Bytesized products...
- Plex expectations
- Tips & Tricks...
- Aethernal Agent Dummies Guide
- The importance of (total or free?) Disk capacity impacts the overall performance. -- Clarification will hopefully help avoid complaints, when all it takes is a minor tweak. =)
|Last Author||Contributors||Versions||Last update|
|faz||24||Sat, 03 Jul 2021 00:13:23 +0200|