diff --git a/Projects/kompose/docs/content/docs/guide/database.md b/Projects/kompose/docs/content/docs/guide/database.md
index 7f94dde9..ea67da16 100644
--- a/Projects/kompose/docs/content/docs/guide/database.md
+++ b/Projects/kompose/docs/content/docs/guide/database.md
@@ -11,19 +11,19 @@ description: Export, import, and manage PostgreSQL databases
- **Cleanup utilities**: Keep only the latest dumps, remove old backups
- **Hook integration**: Custom pre/post operations for each database action
-### πͺ Extensibility
+### 
Extensibility
- **Custom hooks**: Define `pre_db_export`, `post_db_export`, `pre_db_import`, `post_db_import`
- **Stack-specific logic**: Each stack can have unique operational requirements
- **Environment access**: Hooks inherit all environment variables
- **Dry-run aware**: Test hook execution without side effects
-### π Network Management
+### 
Network Management
- **Unified network**: All stacks communicate on a single Docker network
- **CLI overrides**: Change network on-the-fly without editing configs
- **Traefik integration**: Seamless reverse proxy setup with proper network awareness
- **Multi-network support**: Special stacks can have additional internal networks
-### π§ Environment Control
+### 
Environment Control
- **Global overrides**: Set environment variables via CLI flags
- **Layered configs**: Root `.env` + stack `.env` + CLI overrides
- **Precedence rules**: CLI > Stack > Root configuration hierarchy
diff --git a/Projects/kompose/docs/content/docs/guide/hooks.md b/Projects/kompose/docs/content/docs/guide/hooks.md
index 31199dd1..758b98a9 100644
--- a/Projects/kompose/docs/content/docs/guide/hooks.md
+++ b/Projects/kompose/docs/content/docs/guide/hooks.md
@@ -77,14 +77,14 @@ The `sexy` stack uses hooks for Directus schema management:
### Hook Best Practices
-β
**DO:**
+
**DO:**
- Return 0 for success, 1 for failure
- Use indented output: `echo " Message"`
- Make non-critical operations return 0
- Check container status before `docker exec`
- Test in dry-run mode first
-β **DON'T:**
+
**DON'T:**
- Assume containers are running
- Use blocking operations without timeouts
- Forget error handling
diff --git a/Projects/kompose/docs/content/docs/guide/quick-start.md b/Projects/kompose/docs/content/docs/guide/quick-start.md
index 35a84e7f..308d77c4 100644
--- a/Projects/kompose/docs/content/docs/guide/quick-start.md
+++ b/Projects/kompose/docs/content/docs/guide/quick-start.md
@@ -25,5 +25,5 @@ chmod +x kompose.sh
# Export all databases
./kompose.sh "*" db:export
-# That's it! π
+# That's it! 
```
diff --git a/Projects/kompose/docs/content/docs/guide/troubleshooting.md b/Projects/kompose/docs/content/docs/guide/troubleshooting.md
index ebf191b4..949ce42a 100644
--- a/Projects/kompose/docs/content/docs/guide/troubleshooting.md
+++ b/Projects/kompose/docs/content/docs/guide/troubleshooting.md
@@ -7,7 +7,7 @@ description: Common issues and solutions
### Common Issues
-#### π« 404 Error from Traefik
+#### 404 Error from Traefik
**Problem:** Websites return 404 even though containers are running
@@ -33,7 +33,7 @@ http://your-server:8080
docker inspect blog_app | grep traefik
```
-#### πΎ Database Import Fails
+#### 
Database Import Fails
**Problem:** `db:import` command fails
@@ -55,7 +55,7 @@ ls -lh news/*.sql
./kompose.sh news db:import 2>&1 | tee import.log
```
-#### π Container Won't Connect to Network
+#### 
Container Won't Connect to Network
**Problem:** Container fails to join kompose network
@@ -70,7 +70,7 @@ docker network create kompose
./kompose.sh "*" up -d
```
-#### πͺ Hooks Not Executing
+#### Hooks Not Executing
**Problem:** Custom hooks aren't running
diff --git a/Projects/kompose/docs/content/docs/index.md b/Projects/kompose/docs/content/docs/index.md
index 7076a49f..c10ba8a1 100644
--- a/Projects/kompose/docs/content/docs/index.md
+++ b/Projects/kompose/docs/content/docs/index.md
@@ -11,40 +11,40 @@ description: Learn about Kompose, your Docker Compose Symphony Conductor for man
### Why Kompose?
-π― **One Command to Rule Them All** - Manage dozens of stacks with a single command
-π **Database Wizardry** - Export, import, and clean up PostgreSQL databases like a boss
-πͺ **Hook System** - Extend functionality with custom pre/post operation hooks
-π **Network Maestro** - Smart network management with CLI overrides
-π **Environment Juggler** - Override any environment variable on the fly
-π¨ **Beautiful Output** - Color-coded logs and status indicators
-π§ͺ **Dry-Run Mode** - Test changes before applying them
+
**One Command to Rule Them All** - Manage dozens of stacks with a single command
+
**Database Wizardry** - Export, import, and clean up PostgreSQL databases like a boss
+
**Hook System** - Extend functionality with custom pre/post operation hooks
+ **Network Maestro** - Smart network management with CLI overrides
+
**Environment Juggler** - Override any environment variable on the fly
+
**Beautiful Output** - Color-coded logs and status indicators
+
**Dry-Run Mode** - Test changes before applying them
-### πΌ Stack Management
+### 
Stack Management
- **Pattern-based selection**: Target stacks with globs, comma-separated lists, or wildcards
- **Bulk operations**: Execute commands across multiple stacks simultaneously
- **Status monitoring**: Visual feedback with color-coded success/failure indicators
- **Smart filtering**: Include/exclude stacks with flexible pattern matching
-### πΎ Database Operations
+### Database Operations
- **Automated backups**: Export PostgreSQL databases with timestamped dumps
- **Smart imports**: Auto-detect latest dumps or specify exact files
- **Drop & recreate**: Safe database import with connection termination
- **Cleanup utilities**: Keep only the latest dumps, remove old backups
- **Hook integration**: Custom pre/post operations for each database action
-### πͺ Extensibility
+### Extensibility
- **Custom hooks**: Define `pre_db_export`, `post_db_export`, `pre_db_import`, `post_db_import`
- **Stack-specific logic**: Each stack can have unique operational requirements
- **Environment access**: Hooks inherit all environment variables
- **Dry-run aware**: Test hook execution without side effects
-### π Network Management
+### Network Management
- **Unified network**: All stacks communicate on a single Docker network
- **CLI overrides**: Change network on-the-fly without editing configs
- **Traefik integration**: Seamless reverse proxy setup with proper network awareness
- **Multi-network support**: Special stacks can have additional internal networks
-### π§ Environment Control
+### Environment Control
- **Global overrides**: Set environment variables via CLI flags
- **Layered configs**: Root `.env` + stack `.env` + CLI overrides
- **Precedence rules**: CLI > Stack > Root configuration hierarchy
diff --git a/Projects/kompose/docs/content/docs/reference/cli.md b/Projects/kompose/docs/content/docs/reference/cli.md
index 6447e5dc..234865aa 100644
--- a/Projects/kompose/docs/content/docs/reference/cli.md
+++ b/Projects/kompose/docs/content/docs/reference/cli.md
@@ -116,7 +116,7 @@ Import PostgreSQL database from SQL dump file.
./kompose.sh db:import path/to/dump.sql
```
-**β οΈ WARNING:** Drops and recreates the database!
+**
WARNING:** Drops and recreates the database!
### db:cleanup
diff --git a/Projects/kompose/docs/content/docs/reference/environment.md b/Projects/kompose/docs/content/docs/reference/environment.md
index b0f14faa..ca026719 100644
--- a/Projects/kompose/docs/content/docs/reference/environment.md
+++ b/Projects/kompose/docs/content/docs/reference/environment.md
@@ -107,17 +107,17 @@ DB_HOST=news-postgres # Overrides root
### Security
-- β
Use strong, random passwords
-- β
Never commit `.env` files to version control
-- β
Use `.env.example` as template
-- β
Rotate secrets regularly
+- Use strong, random passwords
+- Never commit `.env` files to version control
+- Use `.env.example` as template
+- Rotate secrets regularly
### Organization
-- β
Document custom variables
-- β
Group related variables
-- β
Use consistent naming
-- β
Keep defaults in root `.env`
+- Document custom variables
+- Group related variables
+- Use consistent naming
+- Keep defaults in root `.env`
## Generating Secrets
diff --git a/Projects/kompose/docs/content/docs/stacks/auth.md b/Projects/kompose/docs/content/docs/stacks/auth.md
index 3c3681ae..49a1ecd8 100644
--- a/Projects/kompose/docs/content/docs/stacks/auth.md
+++ b/Projects/kompose/docs/content/docs/stacks/auth.md
@@ -3,7 +3,7 @@ title: Auth Stack - The Bouncer at Your Digital Club
description: "You shall not pass... without proper credentials!"
---
-# π Auth Stack - The Bouncer at Your Digital Club
+# Auth Stack - The Bouncer at Your Digital Club
> *"You shall not pass... without proper credentials!"* - Keycloak, probably
@@ -13,18 +13,18 @@ This stack is your authentication and identity management powerhouse. Think of i
## The Star of the Show
-### π Keycloak
+### 
Keycloak
**Container**: `auth_keycloak`
**Image**: `quay.io/keycloak/keycloak:latest`
**Home**: https://auth.pivoine.art
Keycloak is like having a Swiss Army knife for authentication. It handles:
-- π€ **Single Sign-On (SSO)**: Log in once, access everything. Magic!
-- π« **Identity Brokering**: Connect with Google, GitHub, and other OAuth providers
-- π₯ **User Management**: Keep track of who's who in your digital zoo
-- π **OAuth 2.0 & OpenID Connect**: Industry-standard security protocols (the fancy stuff)
-- π‘οΈ **Authorization Services**: Fine-grained control over who can do what
+- 
**Single Sign-On (SSO)**: Log in once, access everything. Magic!
+- 
**Identity Brokering**: Connect with Google, GitHub, and other OAuth providers
+- 
**User Management**: Keep track of who's who in your digital zoo
+- 
**OAuth 2.0 & OpenID Connect**: Industry-standard security protocols (the fancy stuff)
+- 
**Authorization Services**: Fine-grained control over who can do what
## Configuration Breakdown
@@ -53,11 +53,11 @@ Running in `edge` mode because we're living on the edge (behind Traefik)! This t
| Variable | What It Does | Cool Factor |
|----------|-------------|-------------|
-| `KC_DB` | Database type (postgres) | π Elephants never forget |
-| `KC_DB_URL` | JDBC connection string | π The digital umbilical cord |
-| `KC_HOSTNAME` | Public-facing URL | π Your internet identity |
-| `KC_PROXY` | Proxy mode setting | π Trust the middleman |
-| `KC_FEATURES` | Enabled features (docker) | π³ Whale hello there! |
+| `KC_DB` | Database type (postgres) | 
Elephants never forget |
+| `KC_DB_URL` | JDBC connection string | The digital umbilical cord |
+| `KC_HOSTNAME` | Public-facing URL | Your internet identity |
+| `KC_PROXY` | Proxy mode setting | Trust the middleman |
+| `KC_FEATURES` | Enabled features (docker) | 
Whale hello there! |
## Ports & Networking
@@ -119,13 +119,13 @@ A: Clear your browser cache, Keycloak loves to cache things
**Q: Database connection issues?**
A: Ensure the `data` stack is running and healthy
-## Security Notes π
+## Security Notes
-- π¨ **Change the default admin password** (seriously, do it now)
-- π Database credentials are shared via root `.env`
-- π Always access via HTTPS in production
-- π Enable audit logging for compliance
-- π― Use realms to separate different applications/teams
+- 
**Change the default admin password** (seriously, do it now)
+- Database credentials are shared via root `.env`
+- Always access via HTTPS in production
+- 
Enable audit logging for compliance
+- Use realms to separate different applications/teams
## Fun Facts
@@ -142,4 +142,4 @@ A: Ensure the `data` stack is running and healthy
---
-*Remember: With great authentication power comes great responsibility. Don't be the person who uses "admin/admin" in production.* π¦ΈββοΈ
+*Remember: With great authentication power comes great responsibility. Don't be the person who uses "admin/admin" in production.* 