auto db seed

Author: utkarshsingh77

.github/workflows/deploy.yml

@@ -34,3 +34,5 @@ jobs:
             cd /root/ourawork
             docker compose down
             docker compose up -d
+            # Run DB seed script
+            bash db/seed_database.sh

README.md

@@ -26,17 +26,20 @@ This web application facilitates connections between restaurants looking to prom
 ### Getting Started
 
 1. Clone the repository:
+
    ```
    git clone <repository-url>
    cd food-influencer-marketplace
    ```
 
 2. Start the Docker containers:
+
    ```
    docker-compose up -d
    ```
 
 3. Initialize the database:
+
    ```
    docker-compose exec db mysql -umktuser -pmkpass marketplace < schema.sql
    ```
@@ -88,11 +91,12 @@ This web application facilitates connections between restaurants looking to prom
 The application uses the following database tables:
 
 ### users
+
 - `id` - Primary key
 - `name` - User's full name
 - `email` - User's email (unique)
 - `password` - Hashed password
-- `role` - Either 'restaurant' or 'influencer'
+- `role` - Either 'restaurant', 'influencer', or 'admin'
 - `bio` - User's bio/description
 - `profile_image` - Path to profile photo
 - `social_links` - JSON containing social media links
@@ -101,6 +105,7 @@ The application uses the following database tables:
 - `created_at` - Account creation timestamp
 
 ### gigs
+
 - `id` - Primary key
 - `restaurant_id` - Foreign key to users table
 - `title` - Gig title
@@ -110,6 +115,7 @@ The application uses the following database tables:
 - `created_at` - Creation timestamp
 
 ### applications
+
 - `id` - Primary key
 - `gig_id` - Foreign key to gigs table
 - `influencer_id` - Foreign key to users table
@@ -118,6 +124,7 @@ The application uses the following database tables:
 - `applied_at` - Application timestamp
 
 ### instagram_tokens
+
 - `id` - Primary key
 - `user_id` - Foreign key to users table
 - `account_name` - Friendly name for the Instagram account
@@ -128,6 +135,7 @@ The application uses the following database tables:
 - `created_at` - Creation timestamp
 
 ### instagram_posts
+
 - `id` - Primary key
 - `influencer_id` - Foreign key to users table
 - `token_id` - Foreign key to instagram_tokens table
@@ -143,22 +151,26 @@ The application uses the following database tables:
 ## Key Features
 
 ### Authentication & Authorization
+
 - User registration and login
 - Role-based access control (restaurant vs. influencer)
 - Session management
 
 ### Profiles
+
 - Enhanced user profiles with role-specific fields
 - Profile image upload
 - Social media integration
 - Editable details
 
 ### For Restaurants
+
 - Post gigs with details
 - Review and respond to applications
 - Manage multiple gigs
 
 ### For Influencers
+
 - Browse available gigs
 - Apply to gigs with personalized messages
 - Track application status
@@ -184,19 +196,22 @@ The platform includes comprehensive Instagram integration for influencers, allow
 2. Create a new app with the Instagram Basic Display product
 
 3. Configure your app:
+
    - Add the Instagram Basic Display product
    - Configure Valid OAuth Redirect URIs with your domain + `/instagram_auth.php`
    - Add your domain to App Domains
    - Note your App ID and App Secret
 
 4. Update `html/includes/instagram_config.php`:
+
    ```php
    define('INSTAGRAM_APP_ID', 'your-app-id');
    define('INSTAGRAM_APP_SECRET', 'your-app-secret');
    define('INSTAGRAM_REDIRECT_URI', 'https://your-domain.com/instagram_auth.php');
    ```
 
 5. Configure the Instagram webhook (optional for real-time updates):
+
    - Set up a webhook in the Meta Developer Dashboard
    - Point it to: `https://your-domain.com/api/instagram_webhook.php`
    - Use the verify token defined in `html/instagram_webhook.php`: `food_influencer_webhook_token`
@@ -229,18 +244,19 @@ The latest update adds support for managing multiple Instagram accounts per user
 
 1. Create a new PHP file in the `html` directory
 2. Include the required files at the top:
+
    ```php
    <?php
    require_once 'includes/db_connect.php';
-   
+
    // Add page-specific logic here
-   
+
    // Include header (after potential redirects)
    require_once 'includes/header.php';
    ?>
-   
+
    <!-- HTML content here -->
-   
+
    <?php require_once 'includes/footer.php'; ?>
    ```
 
@@ -310,11 +326,11 @@ if (!empty($_FILES['file']['name'])) {
     $file_extension = pathinfo($_FILES["file"]["name"], PATHINFO_EXTENSION);
     $new_filename = "file_" . time() . "." . $file_extension;
     $target_file = $target_dir . $new_filename;
-    
+
     // Validate file
     $allowed_types = ['jpg', 'jpeg', 'png', 'pdf'];
     $max_size = 5 * 1024 * 1024; // 5MB
-    
+
     if ($_FILES["file"]["size"] > $max_size) {
         $error = "File is too large";
     } elseif (!in_array(strtolower($file_extension), $allowed_types)) {
@@ -341,13 +357,15 @@ if (!empty($_FILES['file']['name'])) {
 ### PHP Configuration
 
 Key PHP settings are in `html/php.ini`:
+
 - upload_max_filesize = 10M
 - post_max_size = 20M
 - memory_limit = 128M
 
 ### Nginx Configuration
 
 Key Nginx settings in `nginx.conf`:
+
 - client_max_body_size = 20M
 - Various MIME type settings
 
@@ -356,6 +374,7 @@ Key Nginx settings in `nginx.conf`:
 ### File Upload Issues
 
 If experiencing "413 Request Entity Too Large" errors:
+
 - Check if your file exceeds the 10MB limit
 - Verify Nginx configuration has proper client_max_body_size value
 - Ensure PHP settings for upload_max_filesize and post_max_size are correct
@@ -364,13 +383,16 @@ If experiencing "413 Request Entity Too Large" errors:
 ### Database Connection Issues
 
 If experiencing database connection problems:
+
 - Verify database credentials in db_connect.php
 - Check if the database container is running
 - Ensure the schema has been imported
+- **If you get an error about the 'role' column not accepting 'admin', see the Seeding section above for how to alter the table.**
 
 ### Instagram Integration Issues
 
 If experiencing Instagram connection problems:
+
 - **"Session Invalid" Error**: Clear cookies, try incognito mode, or reconnect the account
 - **"Invalid Redirect URI" Error**: Ensure your redirect URI in the code exactly matches what's in the Meta Developer Dashboard
 - **Database Column Errors**: The system will automatically update the database schema, but you can manually run the table creation from `instagram_config.php`
@@ -386,4 +408,37 @@ If experiencing Instagram connection problems:
 
 ## License
 
-[Your license information here] 
+[Your license information here]
+
+### Seeding the Database
+
+To seed the database with initial data (including the admin user), use the provided script:
+
+```sh
+bash db/seed_database.sh
+```
+
+This will:
+
+- Apply the schema
+- Seed users, gigs, and other data
+- Set up the admin user
+
+#### Admin Credentials (default after seeding):
+
+- **Email:** `[email protected]`
+- **Password:** `password123`
+
+#### If you see an error like:
+
+```
+ERROR 1265 (01000): Data truncated for column 'role' at row 1
+```
+
+This means the `role` column in your `users` table does not yet allow the value `'admin'`. To fix this, run:
+
+```sql
+ALTER TABLE users MODIFY role ENUM('restaurant', 'influencer', 'admin') NOT NULL;
+```
+
+Then re-run the seed script or the admin setup SQL.

db/schema.sql

@@ -3,7 +3,7 @@ CREATE TABLE IF NOT EXISTS users (
   name VARCHAR(100) NOT NULL,
   email VARCHAR(100) NOT NULL UNIQUE,
   password CHAR(60) NOT NULL,
-  role ENUM('restaurant','influencer') NOT NULL,
+  role ENUM('restaurant', 'influencer', 'admin') NOT NULL,
   bio TEXT,
   profile_image VARCHAR(255),
   social_links JSON,