Improve documentation by adding mkdocs material, as well as guide on how to setup one specific notification mechanism (#21)

Author: hsoerensen

.github/workflows/publish_mkdocs.yml

@@ -0,0 +1,28 @@
+name: Publish mkdocs to gh-pages
+on:
+  push:
+    branches:
+      - main
+permissions:
+  contents: write
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Configure Git Credentials
+        run: |
+          git config user.name github-actions[bot]
+          git config user.email 41898282+github-actions[bot]@users.noreply.github.com
+      - uses: actions/setup-python@v5
+        with:
+          python-version: 3.x
+      - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV
+      - uses: actions/cache@v4
+        with:
+          key: mkdocs-material-${{ env.cache_id }}
+          path: .cache
+          restore-keys: |
+            mkdocs-material-
+      - run: pip install mkdocs-material
+      - run: mkdocs gh-deploy --force

.gitignore

@@ -1,3 +1,4 @@
-./.idea/**/*
+/.idea
+/site
 
 /docker/notification.yml

.markdownlint.json

@@ -1,5 +1,8 @@
 {
   "MD013": {
-    "line_length": 120
+    "line_length": 256
+  },
+  "MD033": {
+    "allowed_elements": ["img"]
   }
 }

README.md

@@ -1,52 +1,34 @@
-# Voi Swarm Participation Node Setup
+# Voi Swarm
 
-## Prerequisites
+## About
 
-- `curl`
-- `apt-get`
+This repository contains the installation script and configuration files for setting up a Voi participation node on a
+Linux system. 
 
-If any package is not available on your system, or if you do not have permission to use said package, follow operating
-system guidance on installation and setup.
+Success criteria for the installation script are:
 
-## Supported Operating Systems and Compute Platforms
+    Focus on providing a good user experience.
+    Provide a simple and easy way to onboard new participants.
+    Offer easy ways for users to operate and maintain their nodes.
 
-### Operating Systems
+To achieve the above the package is an opinionated way to join the network, and may thus not be suitable for 
+all use cases.
 
-- Debian
-- Ubuntu
+## Documentation
 
-### Compute Platforms
+Documentation can be found on [https://voinetwork.github.io/voi-swarm/](https://voinetwork.github.io/voi-swarm/)
 
-- arm64
-- amd64 (x86_64)
+## Contributing
 
-## New to Voi
+Contributions are welcome! Please join the [Voi Network Discord server](https://discord.com/invite/vnFbrJrHeW) to discuss
+with other community members and contributors. You can also open an issue or a pull request on GitHub.
 
-To set up a new Voi node, run the following command:
+## License
 
-```bash
-/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/VoiNetwork/voi-swarm/main/install.sh)"
-```
-
-## Using an Existing Account/Address with Mnemonic
+AGPL-3.0. See [LICENSE](LICENSE) for more information.
 
-If you have an existing account/address with a mnemonic that you want to use, set the VOINETWORK_IMPORT_ACCOUNT
-environment variable to 1 and run the installation script:
-
-```bash
-export VOINETWORK_IMPORT_ACCOUNT=1
-/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/VoiNetwork/voi-swarm/main/install.sh)"
-```
 
-## Installing Without Wallet Setup
 
-If you want to install without including wallet setup, set the VOINETWORK_SKIP_WALLET_SETUP environment variable to 1
-and run the installation script:
-
-```bash
-export VOINETWORK_SKIP_WALLET_SETUP=1
-/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/VoiNetwork/voi-swarm/main/install.sh)"
-```
 
 ## Updating Your Participation Key
 
@@ -59,199 +41,4 @@ expire, rerun the installation script to generate a new key.
 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/VoiNetwork/voi-swarm/main/install.sh)"
 ```
 
-## Setting up Participation Key Expiry Notifications (Recommended)
-
-Each online account has a participation key that needs to be valid for the account to participate in the Voi network.
-A participation key is valid for a certain number of rounds, which is approximately 14 days. When the participation key
-expires the node runner will no longer be able to propose or vote on blocks. To avoid this situation you need to renew
-the participation key before expiration.
-
-To receive a notification when the participation key is about to expire, you can do the following:
-
-### Copy the Example File
-
-Start by copying the example notification.yml file to the voi/docker directory:
-
-`cp ~/voi/docker/notification.yml.example ~/voi/docker/notification.yml`
-
-### Update the notification.yml File
-
-Update the notification.yml file with your preferred notification mechanism by updating the NOTIFICATION_URLS
-environment variable. The notification mechanism can be a webhook, email, push, or any other notification mechanism that
-is available via [Apprise notifications](https://github.com/caronc/apprise?tab=readme-ov-file#supported-notifications)
-
-If you want to use multiple mechanisms, separate them with a comma. For example, to use both Discord and Pushbullet for
-notification, you would set the `NOTIFICATION_URLS` value in the `notification.yml` file  to:
-
-```yaml
-NOTIFICATION_URLS="discord://<webhook_id>/<webhook_token>,pushbullet://<access_token>"
-```
-
-### Updating Notification Schedule
-
-To modify the notification schedule, adjust the `- swarm.cronjob.schedule=0 16 * * *` label in the copied example file.
-This is by default set to run daily at 4 PM UTC. Adjust this to your preferred time, accounting for your
-timezone's UTC offset. Use a resource like [dateful.com](https://dateful.com/time-zone-converter) for timezone conversion.
-
-The format of the schedule is following the standard [cronjob format](https://en.wikipedia.org/wiki/Cron#Overview).
-
-### Applying Notification Configuration to the Stack
-
-To apply your notification configuration to the stack, rerun the installation script:
-
-```bash
-/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/VoiNetwork/voi-swarm/main/install.sh)"
-```
-
-### Testing Your Notification Configuration
-
-To test your notification configuration, you can manually trigger the notification service by running the following command:
-
-```bash
-~/voi/bin/notification-test
-```
-
-## Setting a Custom Telemetry Name
-
-To set a custom telemetry name, set the VOINETWORK_TELEMETRY_NAME environment variable to your desired name:
-
-```bash
-export VOINETWORK_TELEMETRY_NAME="my_custom_telemetry_name"
-/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/VoiNetwork/voi-swarm/main/install.sh)"
-```
-
-Custom telemetry name can be combined with other environment variables.
-
-## Uninstalling
-
-To uninstall, execute the following commands:
-
-- Leave the Swarm with `docker swarm leave --force`
-- Remove the `voi` directory with `rm -rf /voi/`
-- Remove the `data` directory with `sudo rm -rf /var/lib/voi`
-
-## Useful Scripts
-
-This section provides a collection of useful scripts for managing your Voi participation node. These scripts are
-designed to be executed within a running Docker container. They closely follow the commands outlined in the
-[D13 guide](https://d13.co/posts/set-up-voi-participation-node/) for setting up a Voi participation node under Ubuntu 22.04.
-
-### Creating a Node Wallet
-
-Create a new wallet with the following command:
-
-```bash
-~/voi/bin/create-wallet <wallet_name>
-```
-
-### Creating an Account
-
-Create a new account with the following command:
-
-```bash
-~/voi/bin/create-account
-```
-
-### Retrieving Account Mnemonic
-
-Retrieve the mnemonic of an existing account with the following command:
-
-```bash
-~/voi/bin/get-account-mnemonic <account_address>
-```
-
-### Importing an Account
-
-Import an existing account with the following command:
-
-```bash
-~/voi/bin/import-account
-```
-
-### Generating Participation Key
-
-Generate a participation key for an existing account with the following command:
-
-```bash
-~/voi/bin/generate-participation-key <account_address>
-```
-
-### Checking Participation Status
-
-Check the participation status of an existing account with the following command:
-
-```bash
-~/voi/bin/get-participation-status <account_address>
-```
-
-### Going Online
-
-Bring an existing account online with the following command:
-
-```bash
-~/voi/bin/go-online <account_address>
-```
-
-### Going Offline
-
-Take an existing account offline with the following command:
-
-```bash
-~/voi/bin/go-offline <account_address>
-```
-
-### Executing Goal Commands
-
-Execute goal commands with the following command:
-
-```bash
-~/voi/bin/goal <goal_command>
-```
-
-### Opening a Bash Shell in the AVM Container
-
-Open a bash shell in the AVM container with the following command:
-
-```bash
-~/voi/bin/start-shell
-```
-
-### Getting Basic Node Health
-
-To retrieve basic health information about your node, execute the following command:
-
-```bash
-~/voi/bin/get-node-status
-```
-
-The `get-node-status` command performs checks using:
-
-- `goal node status` to connect to the running daemon and retrieve basic node information
-- `/health`: This API endpoint checks the reported health of the node. [REST API /health documentation](https://developer.algorand.org/docs/rest-apis/algod/#get-health).
-- `/ready`: This API endpoint checks the reported readiness of the node and if fully caught up. [REST API /ready documentation](https://developer.algorand.org/docs/rest-apis/algod/#get-ready).
-
-### Testing Notifications
-
-To test notifications execute the following command:
-
-```bash
-~/voi/bin/notification-test
-```
-
-## Debugging
-
-### Startup state for services in stack
-
-`docker stack ps --no-trunc voinetwork`
-
-### Replication state for services in stack
-
-`docker service ls`
-
-### Pull log files
-
-`docker service logs voinetwork_algod`
-
-### Inspect service
 
-`docker inspect voinetwork_algod`