ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
The Iron Codex is a medieval history archive of 800 researched articles on the people, battles, kingdoms, dynasties and surviving arms of the Middle Ages.
EducationJavaScript · CSSGitHub @RPBMediaOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
A mobile-friendly React and Node.js history app focused on medieval Europe from 476 to 1453.
• Random history articles on the home page
• Chronological medieval events
• Medieval kingdoms, cities, and towns
• People profiles with biography sections
• Historical artifacts
• Responsive red, gold, black, and silver visual design
Open http://localhost:4000.
IronCodex supports email/password accounts, Google sign-in, signed HTTP-only session cookies, and a protected Favorites shell.
Copy .env.example to .env for local development:Read the full README ↗A mobile-friendly React and Node.js history app focused on medieval Europe from 476 to 1453.
npm run install:all
npm run build
npm start
Open http://localhost:4000.
IronCodex supports email/password accounts, Google sign-in, signed HTTP-only session cookies, and a protected Favorites shell.
Copy .env.example to .env for local development:
cp .env.example .env
Required for production and recommended locally:
AUTH_SESSION_SECRET="replace-with-a-long-random-secret"
AUTH_BASE_URL="https://your-domain.example"
Optional:
GOOGLE_CLIENT_ID="your-google-oauth-client-id"
GOOGLE_CLIENT_SECRET="your-google-oauth-client-secret"
CORS_ORIGIN="https://your-domain.example"
AUTH_USERS_FILE="/absolute/path/to/users.json"
For Google OAuth, create a Google OAuth web client and add this authorized redirect URI:
https://your-domain.example/api/auth/google/callback
For local development, use:
http://localhost:4000/api/auth/google/callback
The local user store defaults to server/data/users.json, which is ignored by Git.