Docker setup for development

[achasol-db]

Adding a docker setup to make development by new contributors easier.

[gitguardian]

⚠️ GitGuardian has uncovered 2 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
17730731	Triggered	Generic Password	8d9b95d	env.docker.example	View secret
-	-	Generic Password	8d9b95d	docker-compose.dev.yml	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.}

[MrBlack1995]

Hi @achasol-db — thanks for the Docker setup proposal! We appreciate the idea of lowering the onboarding barrier for new contributors.

After reviewing, we decided not to include the Docker setup in PR #51 (our feature/flow consolidation branch) since local dev is already a lightweight process:

Local (SQLite):

source venv/bin/activate
cd src/backend && ./run.sh        # backend
python3 src/build.py && cd src/frontend && npm start  # frontend

Databricks Apps deployment:

DATABRICKS_HOST="https://your-workspace.cloud.databricks.com" \
  DATABRICKS_TOKEN="dapi..." \
  python3 src/deploy.py \
    --app-name kasal-lakebase \
    --user-name your.email@databricks.com

That said, we've added you as a contributor on PR #51 because ideas and contributions are always welcome — even when they don't make it into the final cut.

Could you close this PR when you get a chance? Thanks for thinking about the developer experience!