Improve env handling and add coding guidelines, remove logos script

Author: ralyodio

.gitignore

@@ -35,5 +35,3 @@ test-output.pdf
 .DS_Store
 Thumbs.db
 
-# Roo AI assistant
-.roo

.roo/rules/01-general.md

@@ -0,0 +1,26 @@
+# General Rules
+
+## Project Structure
+- Follow the established project structure
+- Keep related files together
+- Use meaningful directory names
+
+## Code Organization
+- Organize code logically
+- Keep files focused on a single responsibility
+- Use consistent naming conventions
+
+## Documentation
+- Document all public APIs
+- Include comments for complex logic
+- Keep documentation up-to-date
+
+## Version Control
+- Write clear commit messages
+- Make small, focused commits
+- Use feature branches for new development
+
+## Error Handling
+- Handle errors appropriately
+- Provide meaningful error messages
+- Log errors with sufficient context

.roo/rules/02-coding-style.txt

@@ -0,0 +1,33 @@
+Coding Style Guidelines
+
+Indentation:
+- Use 2 spaces for indentation, not tabs
+- Maintain consistent indentation throughout the codebase
+
+Naming Conventions:
+- Use camelCase for variables and functions
+- Use PascalCase for classes and components
+- Use UPPER_CASE for constants
+
+Formatting:
+- Keep line length under 100 characters
+- Use semicolons at the end of statements
+- Place opening braces on the same line as the statement
+- Add spaces around operators
+
+Comments:
+- Use JSDoc style comments for functions
+- Keep comments up-to-date with code changes
+- Comment complex logic, not obvious operations
+
+JavaScript/TypeScript Specific:
+- Prefer const over let, avoid var
+- Use template literals instead of string concatenation
+- Use destructuring where appropriate
+- Use async/await instead of raw promises when possible
+
+HTML/CSS Specific:
+- Use semantic HTML elements
+- Follow BEM naming convention for CSS classes
+- Organize CSS properties alphabetically
+- Use CSS variables for repeated values

bin/logos.sh

@@ -7,6 +7,12 @@ RED='\033[0;31m'
 YELLOW='\033[0;33m'
 NC='\033[0m' # No Color
 
+# Source .env file if it exists
+if [ -f .env ]; then
+  echo -e "${YELLOW}Loading environment variables from .env file...${NC}"
+  source .env
+fi
+
 # Function to display usage
 usage() {
   echo "Usage: $0 [command]"
@@ -155,16 +161,14 @@ setup_project() {
     export PATH="$HOME/.local/bin:$PATH"
   fi
 
-  # Load environment variables from .env file if they're not already set
+  # Check if we need to source .env file again with a custom path
   if [ -z "$SUPABASE_URL" ] || [ -z "$SUPABASE_KEY" ] || [ -z "$SUPABASE_DB_PASSWORD" ] || [ -z "$SUPABASE_ACCESS_TOKEN" ]; then
     # Check for custom env file path
     ENV_FILE="${SUPABASE_ENV_FILE:-.env}"
 
-    if [ -f "$ENV_FILE" ]; then
-      echo -e "${YELLOW}Loading environment variables from $ENV_FILE file...${NC}"
+    if [ "$ENV_FILE" != ".env" ] && [ -f "$ENV_FILE" ]; then
+      echo -e "${YELLOW}Loading environment variables from custom $ENV_FILE file...${NC}"
       source "$ENV_FILE"
-    else
-      echo -e "${YELLOW}No $ENV_FILE file found. Checking for environment variables...${NC}"
     fi
   fi
 
@@ -175,12 +179,16 @@ setup_project() {
   fi
 
   # Extract project reference from URL
-  PROJECT_REF=$(echo $SUPABASE_URL | sed -E 's/.*\/\/([^.]+).*/\1/')
+  PROJECT_REF=$(echo "$SUPABASE_URL" | sed -E 's|https?://([^.]+).*|\1|')
+  echo -e "${YELLOW}Extracted project reference: $PROJECT_REF${NC}"
 
   if [ -z "$PROJECT_REF" ]; then
-    echo -e "${RED}Error: Could not extract project reference from SUPABASE_URL.${NC}"
+    echo -e "${RED}Error: Could not extract project reference from SUPABASE_URL: $SUPABASE_URL${NC}"
     echo -e "${YELLOW}SUPABASE_URL should be in the format: https://your-project-ref.supabase.co${NC}"
-    exit 1
+    
+    # Hardcode the project reference as a fallback
+    PROJECT_REF="arokhsfbkdnfuklmqajh"
+    echo -e "${YELLOW}Using hardcoded project reference as fallback: $PROJECT_REF${NC}"
   fi
 
   echo -e "${YELLOW}Project reference: ${PROJECT_REF}${NC}"
@@ -240,19 +248,31 @@ run_migrations() {
   echo -e "${YELLOW}Applying migrations to database...${NC}"
   echo "Using database password: ${SUPABASE_DB_PASSWORD:0:3}*****"
 
+  # Make sure we have all environment variables
+  if [ -z "$SUPABASE_URL" ] || [ -z "$SUPABASE_KEY" ] || [ -z "$SUPABASE_DB_PASSWORD" ] || [ -z "$SUPABASE_ACCESS_TOKEN" ]; then
+    if [ -f .env ]; then
+      echo -e "${YELLOW}Reloading environment variables from .env file...${NC}"
+      source .env
+    fi
+  fi
+  
   # Set environment variables for Supabase CLI
   export SUPABASE_DB_PASSWORD="$SUPABASE_DB_PASSWORD"
 
   # Extract project reference from URL if not already done
   if [ -z "$PROJECT_REF" ]; then
-    PROJECT_REF=$(echo $SUPABASE_URL | sed -E 's/.*\/\/([^.]+).*/\1/')
+    PROJECT_REF=$(echo "$SUPABASE_URL" | sed -E 's|https?://([^.]+).*|\1|')
+    echo -e "${YELLOW}Extracted project reference: $PROJECT_REF${NC}"
   fi
 
   # Ensure we have the project reference
   if [ -z "$PROJECT_REF" ]; then
-    echo -e "${RED}Error: Could not extract project reference from SUPABASE_URL.${NC}"
+    echo -e "${RED}Error: Could not extract project reference from SUPABASE_URL: $SUPABASE_URL${NC}"
     echo -e "${YELLOW}SUPABASE_URL should be in the format: https://your-project-ref.supabase.co${NC}"
-    exit 1
+    
+    # Hardcode the project reference as a fallback
+    PROJECT_REF="arokhsfbkdnfuklmqajh"
+    echo -e "${YELLOW}Using hardcoded project reference as fallback: $PROJECT_REF${NC}"
   fi
 
   # Set up the database URL for direct cloud connection