# Project plan — indawo_online_docker

Evidence date: 2026-10-12.

Source repository: `git@bitbucket.org:overdrive/indawo_online_docker.git`.

Inspected revision: `master` at `56c9ae9` (2025-06-25, Ettiene, "Initial commit"). That commit is `origin/HEAD`. The only remote branch is `master`. There are no tags.

The scan-host path named on the onboarding issue (`~/projects/sonar_scan/repos/indawo_online_docker`) was not on this machine. The tree below was read from a clone of the git revision above. That revision is the same commit the issue records (`56c9ae9`, 2025-06-25 18:22:04 +0000). `git ls-remote` shows one ref, `refs/heads/master`, at that hash.

This plan describes what the repository contains. It does not decide what the product should become.

There is no README, license, product brief, Dockerfile, or prior Silicon Ark set for `indawo_online_docker`.

## Product

**Unknown.** Nothing in the committed tree states a product purpose, a user, or a problem being solved.

The repository name is `indawo_online_docker`. **Inferred from the name only:** someone may have intended a Docker packaging of an online product named Indawo. No commit message, file, or comment says that. No `Dockerfile`, Compose file, or container config is committed.

Silicon Ark already documents a different repository, `quantiviaLive`, whose own project plan records Indawo strings inside that tree:

- A `README.md` titled "Indawo / Code Deploy with AWS and FTP Deploy", a local vhost `local.indawo`, and AWS CodeDeploy steps for an application named `CodedeployDev`. That Silicon Ark note says the README does not mention Quantivia.
- A `bitbucket-pipelines.yml` `development` step that runs `git ftp init` against `public_html/indawo.overdriveqa.co.za`.

`quantiviaLive`'s project plan already flags those strings as a discrepancy and asks whether they were copied into that repository by mistake. This repository does not mention Quantivia, those hostnames, CodeDeploy, or FTP. Whether `indawo_online_docker` was meant to hold that deploy story, a Docker image for it, or an unrelated empty name is **Unknown / Requires Confirmation**.

## What this repository is

A Bitbucket repository with one commit and no application source.

Committed path at `56c9ae9`:

| Path | What it is |
|---|---|
| `.gitignore` | Text ignore list, 50 lines. Its own header says the patterns are examples to customize, and it links to an Atlassian Git tutorial |

Provenance: **Implemented** (the file is in git). Calling it a stock Bitbucket creation template is **Inferred** from the header, the Atlassian URL, the commit subject "Initial commit", and the fact that it is the only file.

No source file, test, dependency manifest, pipeline, Docker file, solution, or infrastructure file is committed.

## History

| Commit | Date | Author | Subject |
|---|---|---|---|
| `56c9ae9` | 2025-06-25 18:22:04 +0000 | Ettiene (`ettiene@overdrive.co.za`) | Initial commit — adds `.gitignore` only |

Full hash: `56c9ae976882a0bcebbbbf58c3524dd26f08f6aa`.

Nothing in git is dated after 2025-06-25. The commit adds one file and deletes nothing.

## Scope in this repository

In scope, because it is committed:

- The default-style ignore list.

Out of scope, because it is not in this repository:

- Any Indawo application, website, API, or online service.
- Any Docker image, Compose stack, or container runtime config.
- Hosting, a database, credentials, and a deployment pipeline.

## Architecture

No application architecture is present.

There is no process to deploy, no interface to call, and no data store the application owns. The name includes "docker". The tree does not.

## Milestones and implementation plan

No milestone, roadmap, or implementation plan is in the repository.

The single commit records that the remote was created with a stock ignore file on 2025-06-25. That is history, not a plan.

## Dependencies

No dependency manifest is committed. The ignore list names directories and extensions used by Node, Java, Python, Maven, JetBrains, macOS, and Windows. Those names are in the template text. They are not evidence that this repository uses those stacks. See `technical-documentation.md`.

## Current status

Dormant. One branch (`master`), one commit, last change 2025-06-25, no application source.

Whether anyone still expects this repository to hold a Dockerised Indawo service is **Unknown / Requires Confirmation**.

## Discrepancy — scan-host file list

The onboarding issue (recorded 2026-09-28) lists this top-level structure from the scan host:

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

Neither file is in git at `56c9ae9`. `.gitignore` does not ignore either name (`*.bat` and `sonar-project.properties` are absent from the pattern list). The scan-host path was not available here, so their contents were not read.

**Unknown / Requires Confirmation:** those two files may be untracked files that exist only on the scan host. `.gitignore` is in git and was absent from that listing, which fits a listing that skipped dotfiles. That does not explain Sonar files being listed when git does not contain them.

## Human confirmation

1. Was `indawo_online_docker` meant to be a Docker packaging of an Indawo online product, and if so, which product?
2. Is this remote related to the Indawo README, vhost `local.indawo`, CodeDeploy application `CodedeployDev`, or FTP host `indawo.overdriveqa.co.za` documented inside `quantiviaLive`, or is the shared name a coincidence?
3. Do `sonar-project.properties` and `sonarqube_scan.bat` exist outside git, and what do they contain?
4. Should this repository stay, be archived, or be left as an empty remote?