The Problem
Clients that need low‑latency OHLC charts from Coinbase must stitch together a websocket client, a streaming aggregation layer (e.g., Bytewax), and a visualization front‑end. Implementing that pipeline from scratch is time‑consuming and error‑prone.
What This Does
The repository does not contain the described data‑pipeline code. Its file set consists of a Jekyll‑based static site:
index.md, samplepage.md, README.md – Markdown content for a developer portfolio. layouts/default.html – HTML layout used by Jekyll. config.yml – Site configuration (title, theme, etc.). images/ – GIF and PNG assets referenced in the markdown. pdf/samplepresentation.pdf – A static presentation.
No Python modules, no Bytewax flow definitions, and no Streamlit or Bokeh scripts are present. Consequently, there is no entry point such as main.py or a Dockerfile that would build a runnable service.
How To Use It
Because the repository is a static site template, the only documented workflow is the Jekyll build process described in the README:
Clone the repo
git clone https://github.com/evanca/TradeDataCoinbase.git cd TradeDataCoinbase
Install Jekyll (requires Ruby)
gem install bundler jekyll bundle install
Build and serve locally
bundle exec jekyll serve
There is no code or configuration for:
Coinbase websocket authentication (no .env or COINBASEAPIKEY). Bytewax pipeline definition (no pipeline.py, no requirements.txt). Bokeh or Streamlit UI (no .py files, no streamlit run).
To realize the intended functionality, a developer would need to add the missing Python components and a suitable requirements.txt or pyproject.toml.
Real‑World Use
If the missing pipeline were added, a typical deployment might look like:
Start the websocket‑to‑Bytewax ingest service
python ingest.py &
Launch the Streamlit dashboard that reads the aggregated OHLC table streamlit run dashboard.py
At present the repository provides only a static showcase page; it cannot be integrated into a live trading analytics stack without substantial new code.
Code Health & Issues
Medium – Missing core implementation – No Python source files for trade ingestion, aggregation, or visualization; the repo’s content does not match its description. Medium – No tests – The repository contains no tests/ directory or CI configuration, so code correctness cannot be validated automatically. Low – No CI/CD – No .github/workflows or other pipeline files; builds rely on manual Jekyll execution. Low – Documentation mismatch – README advertises a “Developer Portfolio Landing Page Template” while the project title suggests a Coinbase data pipeline, creating confusion for stakeholders. Low – License present – A LICENSE file exists, satisfying basic open‑source compliance.
No obvious security secrets are committed, but the absence of environment‑variable handling for API keys would be a risk once the pipeline is added.
The Bottom Line
The repository is a static Jekyll portfolio site, not a functional Coinbase‑to‑OHLC pipeline. It can serve as a quick personal website, but it offers no usable code for real‑time trade data processing. Teams seeking a ready‑made streaming aggregation and visualization stack will need to build that layer from scratch or locate a more appropriate repository.