EduPets is a standard FastAPI application, so getting it running locally requires nothing more than Python 3.10 or later, a virtual environment, and two dependencies. The steps below take you from a fresh clone to a working game in your browser in under five minutes.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Edupets-Studio/Edu-pets/llms.txt
Use this file to discover all available pages before exploring further.
Create a virtual environment
Create an isolated Python environment so the project’s dependencies don’t conflict with anything else on your machine.Then activate it:Your terminal prompt should now show
(.venv) to confirm the environment is active.Install dependencies
Install the project’s two runtime dependencies from This installs:
requirements.txt.fastapi[standard]==0.136.1— the web framework, bundled with Uvicorn and its standard extrasjinja2==3.1.6— the HTML templating engine used to render every page
Start the development server
Use the FastAPI will start the Uvicorn development server and begin watching for file changes. You should see output similar to:Any change you make to a Python file or template will automatically reload the server.
fastapi dev command to launch Uvicorn with hot reload enabled.Open the app in your browser
Navigate to http://127.0.0.1:8000 in any modern browser. You will be greeted by the EduPets landing screen with a Comenzar (Start) button that leads to the login page and from there into the game.
All game state — pet stats, player name, coins, and task history — is stored in your browser’s localStorage. There is no database, no backend session, and no environment variables required. You can start playing immediately after the server is running, and your progress persists across page refreshes automatically.
App bootstrap
The following excerpt frommain.py shows how the FastAPI application is initialised, how static files are mounted, and how the Jinja2 template engine is configured:
BASE_DIR is resolved at import time so the paths to the static/ and templates/ directories work correctly regardless of where the process is started from — which is important for Vercel’s serverless runtime.
