[cabrasky]

Descripción\nAgrega archivo .env.example con documentación de todas las variables de entorno necesarias.

Cambios

• Crea table2taste/.env.example con variables para DB, backend Spring y entorno

Variables documentadas

• POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB
• DB_URL, JWT_SECRET, JWT_EXPIRATION_MS
• TABLE_PASSWORD, DEFAULT_LANGUAGE, FILE_PATH
• SPRING_PROFILES_ACTIVE

Closes #3

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
14784426	Triggered	Generic High Entropy Secret	5318b80	.env.example	View secret
34427002	Triggered	Generic Password	5318b80	.env.example	View secret
14784427	Triggered	Generic Password	5318b80	.env.example	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[Copilot]

Pull request overview

This PR introduces a repository-level .env.example intended to document environment variables for local/deployed runs, and updates docker-compose.yml to use healthchecks and depends_on health conditions to improve startup ordering.

Changes:

• Added .env.example documenting DB and Spring-related environment variables.
• Updated docker-compose.yml to gate frontend/backend startup on dependent services being healthy.
• Added healthchecks for backend, frontend, and db services.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
docker-compose.yml	Adds healthchecks and switches depends_on to service_healthy conditions for improved orchestration.
.env.example	Adds an example env file documenting required environment variables (but currently includes real-looking secrets).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.