Skip to content
NaingzwehtutPublic

About

πŸ’Ό Full-stack job finder platform: browse, search and apply for jobs.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

Β 

History

4 Commits

Folders and files

NameName
Last commit message
Last commit date
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

JobFlow

A job search platform that aggregates listings from Remotive and RemoteOK into one normalized feed. Public browsing, search, and filters work without an account; registered users can save jobs and track application status from a dashboard.

jobflow/
β”œβ”€β”€ backend/   Flask API (job aggregation, auth, saved jobs) β€” deploy to Render
└── frontend/  React + Vite SPA β€” deploy to Vercel

How it works

  • The Flask backend is the only thing that talks to Remotive and RemoteOK. It fetches both APIs, normalizes them into one job schema (title, company, location, remote, tags, job_type, experience_level, apply_url, etc.), merges them, and caches the result in memory for JOB_CACHE_TTL seconds so the upstream APIs aren't hit on every request.
  • job_type: internship and experience_level: entry_level are inferred from keywords in the title/description (e.g. "intern", "junior", "entry level") since neither upstream API exposes these as clean fields.
  • The frontend never calls Remotive/RemoteOK directly β€” only the Flask API.
  • Auth is stateless JWT (Flask-JWT-Extended), not Supabase Auth. Supabase here is just a hosted Postgres database; the connection string is all that's used.
  • When a user saves a job, the backend stores a snapshot of that job's normalized data alongside the save record, so the dashboard renders saved jobs without needing to re-query the external APIs (which don't support lookup-by-id).

Local development

Backend

cd backend
python3 -m venv venv && source venv/bin/activate
pip install -r requirements.txt
cp .env.example .env   # then edit DATABASE_URL / JWT_SECRET_KEY as needed
python run.py           # runs on http://localhost:5000

For local development you can leave DATABASE_URL unset β€” it falls back to a local SQLite file, which is fine for trying things out before you have Supabase set up. Tables are created automatically on startup (db.create_all()), so no migration step is needed for a first run.

Frontend

cd frontend
npm install
cp .env.example .env   # VITE_API_URL=http://localhost:5000
npm run dev             # runs on http://localhost:5173

Setting up Supabase (production database)

  1. Create a project at supabase.com.
  2. In Project Settings β†’ Database, copy the Connection pooling URI (port 6543) β€” this is built for serverless/short-lived connections like Render's.
  3. Set that as DATABASE_URL in the backend's environment. The app will create the users and saved_jobs tables on first boot. backend/db/schema.sql is provided as a reference/fallback if you'd rather run the SQL yourself.
  4. Nothing else is required β€” no Supabase Auth setup, no RLS policies β€” since the Flask backend handles auth and every query is scoped to the authenticated user at the application layer.

Deployment

Backend β†’ Render

  1. Push this repo to GitHub and create a new Web Service on Render pointed at backend/ (or use the included render.yaml as a Blueprint).
  2. Build command: pip install -r requirements.txt. Start command: gunicorn wsgi:app.
  3. Set environment variables: DATABASE_URL (Supabase pooling URI), JWT_SECRET_KEY (long random string), FRONTEND_ORIGINS (your Vercel URL, comma-separated if more than one), and optionally JOB_CACHE_TTL.

Frontend β†’ Vercel

  1. Import the repo into Vercel, set the project root to frontend/.
  2. Framework preset: Vite. Build command npm run build, output directory dist.
  3. Set VITE_API_URL to your Render backend URL (no trailing slash).
  4. vercel.json is included so client-side routes (e.g. /jobs/:id) resolve correctly on refresh/direct link.

After both are deployed, update the backend's FRONTEND_ORIGINS to include the real Vercel URL (CORS is locked down to that list).

API reference (backend)

Method Path Auth Description
GET /api/jobs none List jobs. Query params: q, remote, internship, entry_level, tech (comma-separated), location, page, per_page
GET /api/jobs/meta none Distinct tags/locations currently available, for filter UIs
GET /api/jobs/<job_id> none Single normalized job
POST /api/auth/register none { email, password, name? } β†’ { token, user }
POST /api/auth/login none { email, password } β†’ { token, user }
GET /api/auth/me JWT Current user
GET /api/dashboard/saved-jobs JWT List saved jobs (optional ?status= filter)
POST /api/dashboard/saved-jobs JWT { job_id } β†’ saves a job (snapshots current data)
PATCH /api/dashboard/saved-jobs/<id> JWT { status } β†’ one of saved, applied, interview, rejected
DELETE /api/dashboard/saved-jobs/<id> JWT Remove a saved job
GET /api/dashboard/analytics JWT { total_saved, by_status }

Notes & known limitations

  • The external job APIs are not paginated server-side in a way that supports deep lookups by id, so the backend fetches the full list per provider and filters/ paginates in memory. This is fine at Remotive/RemoteOK's current listing volumes but wouldn't scale to much larger sources without moving to a periodic sync job that writes into Postgres.
  • job_type and experience_level are keyword-inferred, not provided upstream, so they won't be perfectly accurate for every listing.
  • db.create_all() is used instead of a migration framework for simplicity. For schema changes after launch, consider adding Flask-Migrate (Alembic).

About

πŸ’Ό Full-stack job finder platform: browse, search and apply for jobs.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages