Skip to content

FerhatTumer/stocks-analyze

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

BistAnalyzer — Setup Guide

Ön Koşullar

  • VS Code + GitHub Copilot extension (Chat + Agent Mode)
  • .NET 9 SDK
  • Docker + Docker Compose (PostgreSQL, Redis, Seq için)
  • Git

Repo Yapısı (başlangıç)

Bu dosyaları GitHub repo'na push'la. Copilot Agent bunları okuyarak projeyi oluşturacak.

BistAnalyzer/
├── .github/
│   └── copilot-instructions.md    ← Copilot HER mesajda otomatik okur
├── prompts/
│   ├── step-0-scaffold.md         ← Solution + projeler + paketler
│   ├── step-1-domain.md           ← Domain katmanı
│   ├── step-2-application.md      ← Contracts + Application katmanı
│   ├── step-3-infrastructure.md   ← Infrastructure katmanı
│   ├── step-4-api.md              ← API katmanı (Minimal API + SignalR)
│   ├── step-5-blazor.md           ← Blazor Server dashboard
│   ├── step-6-docker.md           ← Docker Compose + config
│   ├── step-7-tests.md            ← Unit testler
│   └── step-8-finalize.md         ← CI, migration, README, son doğrulama
└── README.md                      ← Bu dosya

Adım Adım Uygulama (VS Code Copilot Agent Mode)

Hazırlık

  1. VS Code'da projeyi aç
  2. Copilot Chat panelini aç (Ctrl+Shift+I veya sidebar'dan)
  3. Chat modunu "Agent" olarak seç (dropdown'dan)

ADIM 0: Solution Scaffold

Read prompts/step-0-scaffold.md and execute ALL phases in it sequentially.
Run every terminal command yourself. Create all files yourself.
At the end, run `dotnet build` and verify it succeeds.

Git commit: git add -A && git commit -m "chore: initial solution scaffold"


ADIM 1: Domain Layer

Read prompts/step-1-domain.md and generate ALL files listed in it.
Follow the folder structure exactly. Place files under src/Domain/.
Use the namespace prefix BistAnalyzer.Domain.
After creating all files, run `dotnet build` to verify.

Domain ve Contracts projelerinde 0 NuGet paketi olmalı. Git commit: git add -A && git commit -m "feat: domain layer - entities, value objects, enums, events"


ADIM 2: Application Layer + Contracts

Read prompts/step-2-application.md and generate ALL files listed in it.
This includes BOTH the Contracts project (src/Contracts/) and Application project (src/Application/).
Follow the folder structure exactly.
Use namespace prefixes BistAnalyzer.Contracts and BistAnalyzer.Application.
After creating all files, run `dotnet build` to verify.

Git commit: git add -A && git commit -m "feat: contracts + application layer - DTOs, interfaces, use cases, scoring service"


ADIM 3: Infrastructure Layer

Read prompts/step-3-infrastructure.md and generate ALL files listed in it.
Follow the folder structure exactly. Place files under src/Infrastructure/.
Use the namespace prefix BistAnalyzer.Infrastructure.
After creating all files, run `dotnet build` to verify.

Büyük katman. Context limitine takılırsa bölümlere ayır:

  • "Generate the Persistence folder files from step-3-infrastructure.md"
  • "Generate the DataProviders folder files from step-3-infrastructure.md"
  • "Generate the Cache and Jobs folder files from step-3-infrastructure.md"

Git commit: git add -A && git commit -m "feat: infrastructure - EF Core, providers, cache, jobs"


ADIM 4: API Layer

Read prompts/step-4-api.md and generate ALL files listed in it.
Follow the folder structure exactly. Place files under src/API/.
Use the namespace prefix BistAnalyzer.API.
After creating all files, run `dotnet build` to verify.

Git commit: git add -A && git commit -m "feat: api layer - minimal api endpoints, signalr hub mapping"


ADIM 5: Blazor Dashboard

Read prompts/step-5-blazor.md and generate ALL files listed in it.
Follow the folder structure exactly. Place files under src/Web/.
Use the namespace prefix BistAnalyzer.Web.
After creating all files, run `dotnet build` to verify.

Git commit: git add -A && git commit -m "feat: blazor dashboard - pages, components, signalr"


ADIM 6: Docker Compose

Read prompts/step-6-docker.md and create all Docker-related files.
Verify with `docker compose config` that the configuration is valid.

Git commit: git add -A && git commit -m "chore: docker compose configuration"


ADIM 7: Tests

Read prompts/step-7-tests.md and generate ALL test files.
Follow the folder structure exactly.
After creating all files, run `dotnet build` and `dotnet test` to verify.

Git commit: git add -A && git commit -m "test: domain and application unit tests"


ADIM 8: Finalize

Read prompts/step-8-finalize.md and execute ALL phases.
Run final `dotnet build && dotnet test` to verify everything works.

Git commit: git add -A && git commit -m "chore: CI pipeline, final verification"


Sorun Giderme

Copilot context limitine takılırsa

From prompts/step-3-infrastructure.md, generate ONLY the files under
Infrastructure/DataProviders/. Follow the same rules.

Build hataları

Fix all build errors. Run `dotnet build` and resolve each error.
Do NOT change the project references or add packages to Domain or Contracts.

Docker sorunları

docker compose up -d
docker compose logs api

Çalıştırma

# .env dosyası oluştur
echo "TCMB_EVDS_API_KEY=your_key_here" > .env

# Docker Compose ile başlat
docker compose up -d

# Erişim
# API:       http://localhost:5000
# Dashboard: http://localhost:5001
# Hangfire:  http://localhost:5000/hangfire
# Seq Logs:  http://localhost:5341
# PostgreSQL: localhost:5432 (bist/bist123)
# Redis:     localhost:6379

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors