Replace numbered list with h3

This commit is contained in:
VD15 2025-05-29 13:36:30 +01:00
parent 846130771e
commit de7670204a

View file

@ -59,7 +59,7 @@ The bot is meant to feel *light, fun, and competitive*. Mixing social, gacha and
## 🧪 Installation ## 🧪 Installation
1. Download and install dependencies ### Download and install dependencies
Clone the repo Clone the repo
@ -81,7 +81,7 @@ Install project dependencies via pip
python3 -m pip install -r requirements.txt python3 -m pip install -r requirements.txt
``` ```
2. Setup config file ### Setup config file
A sample config file is included with the project as a template: `example_config.ini` A sample config file is included with the project as a template: `example_config.ini`
@ -97,7 +97,7 @@ cp example_config.ini config_dev.ini
# Edit config_dev.ini # Edit config_dev.ini
``` ```
4. Setup database ### Setup database
To set up the database, run: To set up the database, run:
@ -105,7 +105,7 @@ To set up the database, run:
KEMOVERSE_ENV=dev python3 setup_db.py KEMOVERSE_ENV=dev python3 setup_db.py
``` ```
5. Run the bot ### Run the bot
```sh ```sh
KEMOVERSE_ENV=dev ./startup.sh KEMOVERSE_ENV=dev ./startup.sh
@ -113,14 +113,14 @@ KEMOVERSE_ENV=dev ./startup.sh
If all goes well, you should now be able to interact with the bot. If all goes well, you should now be able to interact with the bot.
6. Running in production ### Running in production
To run the the in a production environment, use `KEMOVERSE_ENV=prod`. You will To run the the in a production environment, use `KEMOVERSE_ENV=prod`. You will
also need to create a `config_prod.ini` file and run the database setup step also need to create a `config_prod.ini` file and run the database setup step
again if pointing prod to a different database. (you are pointing dev and prod again if pointing prod to a different database. (you are pointing dev and prod
to different databases, right? 🤨) to different databases, right? 🤨)
7. Updating ### Updating
To update the bot, first pull new changes from upstream: To update the bot, first pull new changes from upstream: