Remove obsolete files and components from the Web-Original project

This commit deletes various files including configuration settings, controllers, models, views, and third-party libraries that are no longer in use. The removal of these files helps streamline the project and reduces clutter, ensuring a cleaner codebase for future development. Key files removed include appsettings, controllers, views related to home and events, and Bootstrap and jQuery libraries.

DEPLOYMENT.md

@@ -11,17 +11,18 @@ This approach allows you to edit credentials without rebuilding the container.
 **Steps:**
 
 1. **Generate Password Hashes** (on your development machine):
+
    ```bash
    # Run the app locally and navigate to:
    https://localhost:<port>/dev/hash-password?password=YourPassword
    ```
-
 2. **Create `auth-secrets.json`** on your Docker host:
+
    ```bash
    cp auth-secrets.example.json auth-secrets.json
    ```
-
 3. **Edit `auth-secrets.json`** and replace the placeholder hashes:
+
    ```json
    {
      "Authentication": {
@@ -36,19 +37,20 @@ This approach allows you to edit credentials without rebuilding the container.
      }
    }
    ```
-
 4. **Mount the file in Docker Compose**:
+
    ```yaml
    volumes:
      - ./auth-secrets.json:/app/secrets/auth-secrets.json:ro
    ```
-
 5. **Update credentials**: Simply edit `auth-secrets.json` on the host and restart the container:
+
    ```bash
    docker-compose restart webapp
    ```
 
 **Security Note**: Set proper file permissions on the host:
+
 ```bash
 chmod 600 auth-secrets.json
 ```
@@ -60,6 +62,7 @@ chmod 600 auth-secrets.json
 This approach is useful for container orchestration platforms (Kubernetes, Docker Swarm, etc.).
 
 **Docker Compose Example**:
+
 ```yaml
 environment:
   - TSA_Authentication__Users__0__Email=admin@example.com
@@ -73,6 +76,7 @@ environment:
 ```
 
 **Docker Run Example**:
+
 ```bash
 docker run -d \
   -p 8080:8080 \
@@ -85,6 +89,7 @@ docker run -d \
 ```
 
 **Kubernetes Secret Example**:
+
 ```yaml
 apiVersion: v1
 kind: Secret
@@ -138,11 +143,13 @@ docker-compose logs -f webapp
 ### Adding a New User
 
 **With Volume-Mounted File:**
+
 1. Edit `auth-secrets.json` on the host
 2. Add new user entry to the `Users` array
 3. Restart the container: `docker-compose restart webapp`
 
 **With Environment Variables:**
+
 1. Add new environment variables (increment the index number)
 2. Recreate the container: `docker-compose up -d`
 
@@ -162,24 +169,22 @@ docker-compose logs -f webapp
 ## Security Considerations
 
 1. **File Permissions**:
+
    ```bash
    chmod 600 auth-secrets.json
    chown root:root auth-secrets.json
    ```
-
 2. **Never Commit Secrets**: Add to `.gitignore`:
+
    ```
    auth-secrets.json
    docker-compose.yml
    ```
-
 3. **Use HTTPS in Production**: Configure SSL/TLS certificates
-
 4. **Backup Credentials**: Store encrypted backups of `auth-secrets.json`
-
 5. **Password Rotation**: Periodically regenerate password hashes
-
 6. **Monitor Access**: Review application logs for failed login attempts:
+
    ```bash
    docker-compose logs webapp | grep "Failed login"
    ```
@@ -191,6 +196,7 @@ docker-compose logs -f webapp
 ### Container Won't Start
 
 Check logs:
+
 ```bash
 docker-compose logs webapp
 ```
@@ -198,16 +204,17 @@ docker-compose logs webapp
 ### Can't Login
 
 1. Verify `auth-secrets.json` is properly mounted:
+
    ```bash
    docker exec tsa-app ls -la /app/secrets/
    ```
-
 2. Check if the file is being loaded:
+
    ```bash
    docker-compose logs webapp | grep "secrets"
    ```
-
 3. Verify JSON syntax:
+
    ```bash
    cat auth-secrets.json | jq .
    ```