more automated upgrades

docs/maintenance/index.md

@@ -2,11 +2,11 @@
 
 In the maintenance chapter you find details about where important log files are found, how you can customize your AA installation and how to solve common issues.
 
-```{toctree}
+:::{toctree}
 :maxdepth: 1
 
 apps
 project
 troubleshooting
 tuning/index
-```
+:::

docs/maintenance/tuning/celery.md

@@ -1,14 +1,13 @@
 # Celery
 
-```{eval-rst}
-.. hint::
+:::{hint}
     Most tunings will require a change to your supervisor configuration in your `supervisor.conf` file. Note that you need to restart the supervisor daemon in order for any changes to take effect. And before restarting the daemon you may want to make sure your supervisors stop gracefully:(Ubuntu):
 
     ::
 
       supervisor stop myauth:
       systemctl supervisor restart
-```
+:::
 
 ## Task Logging
 
@@ -28,10 +27,9 @@ command=/home/allianceserver/venv/auth/bin/celery -A myauth worker -l info
 
 Celery workers often have memory leaks and will therefore grow in size over time. While the Alliance Auth team is working hard to ensure Auth is free of memory leaks some may still be cause by bugs in different versions of libraries or community apps. It is therefore good practice to enable features that protect against potential memory leaks.
 
-```{eval-rst}
-.. hint::
+:::{hint}
     The 256 MB limit is just an example and should be adjusted to your system configuration. We would suggest to not go below 128MB though, since new workers start with around 80 MB already. Also take into consideration that this value is per worker and that you may have more than one worker running in your system.
-```
+:::
 
 
 ### Supervisor
@@ -90,15 +88,14 @@ command=... -p worker_00=256MB -p worker_01=256MB -p worker_02=256MB
 ...
 ```
 
-```{eval-rst}
-.. hint::
+:::{hint}
     You will want to experiment with different settings to find the optimal. One way to generate task load and verify your configuration is to run a model update with the following command:
 
     ::
 
       celery -A myauth call allianceauth.eveonline.tasks.run_model_update
 
-```
+:::
 
 ### Concurrency
 
@@ -108,17 +105,15 @@ This can be achieved by the setting the concurrency parameter of the celery work
 --concurrency=10
 ```
 
-```{eval-rst}
-.. hint::
+:::{hint}
     The optimal number will hugely depend on your individual system configuration and you may want to experiment with different settings to find the optimal. One way to generate task load and verify your configuration is to run a model update with the following command:
 
     ::
 
       celery -A myauth call allianceauth.eveonline.tasks.run_model_update
 
-```
+:::
 
-```{eval-rst}
-.. hint::
+:::{hint}
     The optimal number of concurrent workers will be different for every system and we recommend experimenting with different figures to find the optimal for your system. Note, that the example of 10 threads is conservative and should work even with smaller systems.
-```
+:::

docs/maintenance/tuning/index.md

@@ -2,15 +2,14 @@
 
 The official installation guide will install a stable version of Alliance Auth that will work fine for most cases. However, there are a lot of levels that can be used to optimize a system. For example some installations may we short on RAM and want to reduce the total memory footprint, even though that may reduce system performance. Others are fine with further increasing the memory footprint to get better system performance.
 
-```{eval-rst}
-.. warning::
+:::{warning}
     Tuning usually has benefits and costs and should only be performed by experienced Linux administrators who understand the impact of tuning decisions on to their system.
-```
+:::
 
-```{toctree}
+:::{toctree}
 :maxdepth: 1
 
 gunicorn
 celery
 redis
-```
+:::