HealthBite

A Django web app for meal and calorie tracking: sign up / sign in, a daily dashboard, log meals (preset foods or your own items with calories), browse history by date, progress charts, goals, and profile settings. Development uses SQLite.

Stack

• Python 3.10+ (recommended)
• Django 4.2 (see comment in DjangoProject1/settings.py)
• SQLite (db.sqlite3)

Features and routes

Path	Description
/	Home: today’s meal lines, calorie total, notes
/login/, /register/	Sign in and sign up
/add-meal/	Log a meal: pick a catalog food, or enter a custom name + calories per serving (optional unit); meal type and quantity apply to either
/historyrecord/	Meal history for a selected date
/progress/	~7-day calorie trend vs goal
/goals/	Goal-related summary
/my-info/	Profile, change password, delete account
/logout/	Sign out
/admin/	Django admin (superuser required)

Auth uses a session (user_id). Application users are AppUser records, separate from Django’s built-in User.

Local setup

1. Virtual environment (recommended)

cd HealthBite
python3 -m venv .venv
source .venv/bin/activate   # Windows: .venv\Scripts\activate

2. Install dependencies

There is no requirements.txt in the repo yet; install Django 4.2 to match settings:

pip install "Django>=4.2,<5"

3. Apply migrations

python3 manage.py migrate

This applies all app migrations (including FoodItem.created_by for custom foods).

4. Create an admin user (optional, for /admin/)

python3 manage.py createsuperuser

5. Run the dev server

python3 manage.py runserver

Open http://127.0.0.1:8000/ in your browser.

Add meal: catalog vs custom foods

• Catalog foods (FoodItem with created_by empty) are shared presets (e.g. seeded in migrations). Their names must be unique among catalog items.
• Custom foods are created from the add-meal form: you enter a name, calories per serving, and optionally a serving unit (defaults to serving). They are stored as FoodItem rows linked to your AppUser via created_by, then reused in your dropdown for later meals.
• If the custom name field is non-empty, that path is used and the catalog dropdown is ignored for that submit. If it is empty, choose an item from the dropdown when catalog items exist; if there are no catalog items yet, fill in the custom fields only.

Admin and data

• Admin URL: http://127.0.0.1:8000/admin/
• Under Core, you can inspect AppUser, UserProfile, MealLog, MealLogItem, FoodItem, etc.
• FoodItem in admin shows created_by: blank = catalog, set = user-defined. You can still add catalog rows in admin; users can add their own from /add-meal/ without admin.
• If there are no catalog foods yet, you can still log meals using only the custom-food fields, or add seed FoodItem rows in admin / migrations.

Project layout (short)

HealthBite/
├── manage.py
├── DjangoProject1/          # project settings, root URLconf
├── core/                    # main app: models, views, urls, admin, static
├── templates/core/          # HTML templates
└── db.sqlite3               # local SQLite (do not commit sensitive DBs to public repos)

Development notes

• DEBUG = True and the default SECRET_KEY are for local use only. Before production, follow the Django deployment checklist.
• Sign-up / sign-in is a demo-style flow: passwords are stored in a password_hash field as plain text for this course-style app, not production-grade hashing. Do not deploy as-is.

License

If the repository has no license file, confirm with the maintainers before redistributing or reusing the code.