# Technical documentation — indawo_online_docker

Evidence date: 2026-10-12.

Source: `git@bitbucket.org:overdrive/indawo_online_docker.git`, `master` at `56c9ae976882a0bcebbbbf58c3524dd26f08f6aa` (2025-06-25 18:22:04 +0000). `origin/HEAD` is `master`. No other branch and no tag.

The scan-host path `~/projects/sonar_scan/repos/indawo_online_docker` was not on the machine that wrote this document. The findings below are from a clone of that revision. `git ls-remote --heads --tags` returned only `refs/heads/master` at that hash.

## Repository identity

| Item | Value | Provenance |
|---|---|---|
| Remote | `git@bitbucket.org:overdrive/indawo_online_docker.git` | **Implemented** (`git remote -v`) |
| Default branch | `master` | **Implemented** (`origin/HEAD`) |
| Commits | 1 | **Implemented** |
| Last commit | `56c9ae9`, 2025-06-25 18:22:04 +0000, subject `Initial commit`, author Ettiene `ettiene@overdrive.co.za` | **Implemented** |

## Tree

```text
.gitignore
```

`git show --stat 56c9ae9` reports `.gitignore` as 50 insertions. The file is text.

No README, license, `bitbucket-pipelines.yml`, Dockerfile, Compose file, `appspec.yml`, Terraform, Serverless template, or dependency manifest (`package.json`, `*.csproj`, `*.sln`, `requirements.txt`, `pom.xml`, `composer.json`, `go.mod`) is in the tree.

## Languages and frameworks

No application language is present.

| File | Format | Role |
|---|---|---|
| `.gitignore` | Text | Git ignore patterns. Header calls them examples |

## Ignore file

`.gitignore` is the only committed file. It was added in `56c9ae9` and never edited. The header points at `https://www.atlassian.com/git/tutorials/saving-changes/gitignore` and says to customize the list. It was not customized.

It ignores, among other patterns: `node_modules/`, `dist/` (twice), `*.class`, `*.py[cod]`, `*.log`, `*.jar`, `target/`, `.idea/`, `TEST*.xml`, `.DS_Store`, `Thumbs.db`, `*.app`, `*.exe`, `*.war`, and several media extensions.

It does not ignore `.vs/`, `bin/`, `obj/`, `.sonarqube/`, `sonar-project.properties`, `*.bat`, `Dockerfile`, or `docker-compose.yml`.

**Inferred:** stock Bitbucket "Initial commit" ignore file, from the commit subject, the Atlassian link, and the example header. **Not evidence** that Node, Java, Python, Maven, or Docker was chosen for this repository.

## Runtime, data, and integration map

| Area | Finding |
|---|---|
| Application runtime | None |
| Framework | None |
| Docker or other container definition | None. The repository name includes `docker`. No image or Compose file is committed |
| Database | None |
| API | None |
| Authentication | None |
| Background worker, job, or queue | None |
| Object storage or cache | None |
| External integration | None |
| Infrastructure and deployment | None |
| Environment configuration | None. No `.env`, appsettings, or example config |
| Monitoring and logging | No application logger. `*.log` is an ignore pattern only |
| CI | No pipeline file |
| Tests | No test project and no test command |
| Security controls in application code | None to review. No secret, connection string, or token was found in `.gitignore` |

## Sonar files named outside git

On 2026-09-28 the onboarding issue recorded this top-level listing from the scan host:

```text
sonar-project.properties
sonarqube_scan.bat
```

Neither path is in `56c9ae9`. Contents: **Unknown / Requires Confirmation**.

A listing that skipped dotfiles would hide `.gitignore` and still would not invent Sonar files. The likely reading is that those two files were added on a working copy and never committed. That reading is **Inferred** and is not confirmed, because the scan-host directory could not be opened. The ignore file would not have blocked committing either name.

## Local development and testing

There is no documented setup, and there is nothing to run.

A clone of `master` yields `.gitignore` only.

No test command exists. No server port is configured. No image build command is configured.

## Security notes for this tree

No secret is stored in the committed file. No application attack surface is present: there is no listener and no container.

## Related Silicon Ark documents

`quantiviaLive` is a separate git remote with its own Silicon Ark set. This repository's commit and tree do not reference it.

That set records, inside `quantiviaLive`, a README titled "Indawo / Code Deploy with AWS and FTP Deploy", a local vhost `local.indawo`, CodeDeploy steps for an application named `CodedeployDev`, and a pipeline `git ftp init` to `public_html/indawo.overdriveqa.co.za`. The `quantiviaLive` project plan already says that README does not mention Quantivia and that no `appspec.yml` or Dockerfile was found there. Treating this empty remote as the Docker half of that deploy story would be a guess. Status: **Unknown / Requires Confirmation**.