Created automated script to convert markdown issue documentation into GitHub Issues with proper labels and formatting. ## What's Added ### Script: scripts/import-github-issues.js - Parses docs/issues/*.md files - Creates GitHub Issues via Octokit API - Adds proper labels (P0/P1/P2, bug, feature, etc.) - Rate-limited to respect GitHub API limits - Comprehensive error handling ### Documentation: scripts/README.md - Complete setup instructions - Troubleshooting guide - Customization options - Advanced usage examples ### Dependencies - Added @octokit/rest for GitHub API access ## How to Use 1. Get GitHub Personal Access Token: - Visit https://github.com/settings/tokens - Create token with 'repo' scope 2. Set token: ```bash export GITHUB_TOKEN=your_token_here ``` 3. Run script: ```bash node scripts/import-github-issues.js ``` ## What Gets Created The script will create 25 GitHub Issues: - 5 P0 (critical) issues - 5 P1 (medium priority) issues - 15 P2 (nice-to-have) issues Each with: - Proper title with priority prefix - Full markdown body - Appropriate labels - File references intact ## Labels Created - P0 (red) - Critical priority - P1 (orange) - Medium priority - P2 (yellow) - Low priority - bug, feature, enhancement, tech-debt, security See scripts/README.md for full documentation. |
||
|---|---|---|
| .builder/rules | ||
| .github/workflows | ||
| aethex-forge | ||
| api | ||
| attached_assets | ||
| build | ||
| client | ||
| docs | ||
| docs-migration | ||
| electron | ||
| public | ||
| scripts | ||
| server | ||
| services | ||
| shared | ||
| supabase/migrations | ||
| tests | ||
| .builderrules | ||
| .dockerignore | ||
| .env.discord.example | ||
| .env.example | ||
| .env.foundation-oauth.example | ||
| .gitignore | ||
| .htaccess | ||
| .npmrc | ||
| .prettierrc | ||
| .replit | ||
| .vercelignore | ||
| AGENTS.md | ||
| build-api.js | ||
| build-for-hostinger.sh | ||
| components.json | ||
| copy-api.js | ||
| DISCORD_SETUP.md | ||
| Dockerfile | ||
| electron-builder.yml | ||
| hostinger-deploy.md | ||
| index.html | ||
| LICENSE | ||
| netlify.toml | ||
| OAUTH_SETUP.md | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.js | ||
| railway.json | ||
| README.md | ||
| replit.md | ||
| supabase-migration.sql | ||
| SUPABASE_SETUP.md | ||
| tailwind.config.ts | ||
| tsconfig.json | ||
| vercel.json | ||
| vite.config.server.ts | ||
| vite.config.ts | ||
| vite.desktop.config.ts | ||
AeThex Forge - Local Development Setup
Quick Start Guide
This guide will help you set up and run the AeThex platform locally on your machine.
Prerequisites
-
Node.js (v18 or higher)
- Download from: https://nodejs.org/
- This will also install npm (Node Package Manager)
-
Git (optional, if you want to clone updates)
- Download from: https://git-scm.com/
Installation Steps
1. Install Node.js
- Visit https://nodejs.org/ and download the LTS version
- Run the installer and follow the setup wizard
- Restart your terminal/PowerShell after installation
2. Verify Installation
Open PowerShell or Command Prompt and run:
node --version
npm --version
You should see version numbers (e.g., v20.x.x and 10.x.x)
3. Install Project Dependencies
Navigate to the project folder and install dependencies:
cd C:\Users\PCOEM\Downloads\aethex-forge\aethex-forge
npm install
This may take a few minutes as it downloads all required packages.
4. Set Up Environment Variables
Create a .env file in the root directory (aethex-forge folder) with the following variables:
Minimum Required (to run the app):
# Supabase Configuration (Required)
VITE_SUPABASE_URL=your_supabase_url_here
VITE_SUPABASE_ANON_KEY=your_supabase_anon_key_here
SUPABASE_SERVICE_ROLE=your_service_role_key_here
SUPABASE_URL=your_supabase_url_here
# API Base URL
VITE_API_BASE=http://localhost:5000
Optional (for full functionality):
# Discord Integration
DISCORD_CLIENT_ID=your_discord_client_id
DISCORD_CLIENT_SECRET=your_discord_client_secret
DISCORD_BOT_TOKEN=your_discord_bot_token
DISCORD_PUBLIC_KEY=your_discord_public_key
DISCORD_REDIRECT_URI=http://localhost:5000/api/discord/oauth/callback
# Foundation OAuth
VITE_FOUNDATION_URL=https://aethex.foundation
FOUNDATION_OAUTH_CLIENT_ID=your_foundation_client_id
FOUNDATION_OAUTH_CLIENT_SECRET=your_foundation_client_secret
# Email Service (SMTP)
SMTP_HOST=your_smtp_host
SMTP_PORT=587
SMTP_USER=your_smtp_user
SMTP_PASSWORD=your_smtp_password
# Other Services
VITE_GHOST_API_URL=your_ghost_api_url
GHOST_ADMIN_API_KEY=your_ghost_admin_key
Note: You can start with just the Supabase variables to get the app running. Other features will work once you add their respective credentials.
5. Run the Development Server
npm run dev
The application will start on http://localhost:5000
Open your browser and navigate to that URL to view the application.
Available Commands
npm run dev- Start development server (port 5000)npm run build- Build for productionnpm start- Start production servernpm run typecheck- Check TypeScript typesnpm test- Run tests
Project Structure
aethex-forge/
├── client/ # React frontend (pages, components)
├── server/ # Express backend API
├── api/ # API route handlers
├── shared/ # Shared types between client/server
├── discord-bot/ # Discord bot integration
└── supabase/ # Database migrations
Getting Supabase Credentials
If you don't have Supabase credentials yet:
- Go to https://supabase.com/
- Create a free account
- Create a new project
- Go to Project Settings → API
- Copy:
- Project URL →
VITE_SUPABASE_URLandSUPABASE_URL anonpublickey →VITE_SUPABASE_ANON_KEYservice_rolesecretkey →SUPABASE_SERVICE_ROLE
- Project URL →
Troubleshooting
Port Already in Use
If port 5000 is already in use, you can change it in vite.config.ts:
server: {
port: 5001, // Change to any available port
}
Module Not Found Errors
Try deleting node_modules and package-lock.json, then run npm install again:
Remove-Item -Recurse -Force node_modules
Remove-Item package-lock.json
npm install
Environment Variables Not Loading
- Make sure
.envfile is in the rootaethex-forgedirectory - Restart the dev server after adding new environment variables
- Variables starting with
VITE_are exposed to the client
Need Help?
- Check the
docs/folder for detailed documentation - Review
AGENTS.mdfor architecture details - See
replit.mdfor deployment information