Strata.Analytics

Branching and Versioning

Epic / Feature branches

For epics / features that have multiple stories or are a big chunk of work, use feature release branches. There should be a feature release main branch and all PRs for that feature will use that as the base. When the entire feature is ready to be deployed, merge the feature release main back into main main.

For example, if the feature is for Content Migration, create the feature release main as feature/[team]/release/content-migration/main. For stories tied to that feature (for example, JAZZ-4231), branch off the feature release main and name it feature/[team]/release/content-migration/JAZZ-4231-content-migration-mapping.

Bugs / Small Changes

For bugs and small changes, use regular feature/[team]/JAZZ-1234-description and fix/[team]/JAZZ-1234-description branches that will be merged into main

Usage

AWS Profile

[profile sdt-analytics-service-role]
source_profile = 809820578507_SDT-Dev-Developers
role_arn = arn:aws:iam::809820578507:role/sdt-analytics-service-role
region=us-east-1

Build and Run

docker-compose up -d --build

https://localhost:8443/index (swagger api)
https://localhost:8443/hangfire (hangfire dashboard)
http://localhost:8081 (redis commander)

Extracting nuget package

docker create --name throwaway strataanalytics_analytics-api
docker cp throwaway:/pack .
docker rm throwaway

Cleanup

docker-compose down

2.7 KiB Raw Blame History