Deeproxio Asset Management API

• Build Status (develop branch)
  • 
• Deeproxio.Asset.API.Client NuGet (Azure Artifacts Public):
  • 

Deeproxio.Asset.API is gRPC service for Deeproxio platform which used for file and file metadata management.

Asset API is backed by Minio AWS S3-like cloud native file object storage and MongoDB database as a persistence storage.

Technologies:

• ASP.NET Core 3+
• gRPC
• Protobuf
• FluentValidation
• AutoMapper
• MongoDB.Driver
• Minio
• Polly
• Serilog
• MSTest Framework

Service requires access to Minio and MongoDB instances in standalone version, but Helm chart k8s deployment contains Minio and MongoDB dependencies.

Docker

• docker image preparation

  # cd in root git repository
  docker build -t dpio-asset-api:latest -f ./Deeproxio.Asset.API/Dockerfile .

• docker image standalone usage

  # run command after image build
  docker run -d --name dpio-asset-api --restart always -p 4300:80 --link local-mongo --link local-minio -e AssetsDatabaseSettings__ConnectionString=mongodb://local-mongo:27017 -e StorageSettings__EndpointUrl=local-minio:9000 -e StorageSettings__AccessKey=<your_minio_accesskey> -e StorageSettings__SecretKey=<your_minio_accesskey> -e ENVIRONMENT=Production dpio-asset-api:latest

  P.S. local-minio and local-mongo are Minio and MongoDB containers deployed in the same docker environment. Replace to any correct name if it's need. Also replace ConnectionString, AccessKey, SecretKey and EndpointUrl values to correct settings.

Helm

1. Run docker image preparation step and create image in local cache.

2. (Optional) Push image to any accesible by your k8s cluster container registry.

3. Create helm package and install release with specification of any required setting from values.yaml.

   # cd in chart\dpio-asset-api directory
   helm package .
   helm install test-asset . --set {option_name}=[override_value] --wait

4. Use kubectl proxy or kubectl port-forward to access service instance.

Development

1. Use BloomRPC for debugging gRPC services.