Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/FranksGP/Gestor_de_tareas/llms.txt

Use this file to discover all available pages before exploring further.

Gestor de Tareas is intentionally minimal in its configuration surface. There are no config files, no environment variables, and no command-line flags. The only setting the application exposes is the name (and optionally the path) of the JSON file used to store tasks. Everything else — menu text, field names, indentation — is hard-coded in index.py and can be changed by editing the source directly.

​
TASKS_FILE constant

The storage filename is defined as a module-level constant on line 4 of index.py: 
TASKS_FILE = "Tareas.json"
Every function that reads from or writes to disk — cargarTask(), guardarTask(), and by extension agregarTask(), listarTask(), tareaCompletada(), and delete_task() — references this constant rather than a hard-coded string. Changing the value of TASKS_FILE once at the top of the file is therefore sufficient to redirect all storage to a different filename.

​
Changing the storage filename

Open index.py in any text editor and replace the value on line 4: 
TASKS_FILE = "Tareas.json"
TASKS_FILE = "mis_tareas.json"
After saving index.py, the application will read from and write to mis_tareas.json instead. Any tasks stored in the old Tareas.json will not be visible until you either rename the file to match the new constant or revert the change.

​
Custom file path

Because TASKS_FILE is a relative path, its effective location depends on the directory from which you launch the script — not the directory where index.py lives. This is standard Python behaviour: relative paths are resolved against the process’s current working directory. For example: 
# Stores Tareas.json in /home/user/documents/
cd /home/user/documents
python /home/user/projects/gestor/index.py

# Stores Tareas.json in /home/user/projects/gestor/
cd /home/user/projects/gestor
python index.py
If you want the file to always land in a fixed location regardless of where you run the script, you can change TASKS_FILE to an absolute path: 
TASKS_FILE = "Tareas.json"
TASKS_FILE = "/home/user/projects/gestor/Tareas.json"
This makes the storage location explicit and predictable no matter which directory is active when you run the script.
Gestor de Tareas does not read from .env files, system environment variables, or any external configuration file. All configuration is done by editing index.py directly. This keeps the project dependency-free and easy to understand, but it does mean that configuration changes require a source-code edit rather than a runtime flag.
To keep your task history tidy, consider creating a dedicated directory for the project and always launching the script from there. For example, mkdir ~/tareas && cd ~/tareas before running python index.py ensures that Tareas.json is always created in one predictable place, making it straightforward to back up or version-control your task data.

Build docs developers (and LLMs) love

Get started for freeTalk to us