-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathsdl.yml.tmpl
65 lines (60 loc) · 2.63 KB
/
sdl.yml.tmpl
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
# Welcome to the Akash Network! 🚀☁
# This file is called a Stack Definition Laguage (SDL)
# SDL is a human friendly data standard for declaring deployment attributes.
# The SDL file is a "form" to request resources from the Network.
# SDL is compatible with the YAML standard and similar to Docker Compose files.
---
# Indicates version of Akash configuration file. Currently only "2.0" is accepted.
version: "2.0"
# The top-level services entry contains a map of workloads to be ran on the Akash deployment. Each key is a service name; values are a map containing the following keys:
# https://docs.akash.network/intro-to-akash/stack-definition-language#services
services:
# The name of the service "web"
web:
# The docker container image with version. You must specify a version, the "latest" tag doesn't work.
image: ghcr.io/${OWNER}/${IMAGE}:${VERSION}
# You can map ports here https://docs.akash.network/intro-to-akash/stack-definition-language#services.expose
expose:
- port: 3000
as: 80
accept:
- ecosystem.akash.network
to:
- global: true
# The profiles section contains named compute and placement profiles to be used in the deployment.
# https://docs.akash.network/intro-to-akash/stack-definition-language#profiles
profiles:
# profiles.compute is map of named compute profiles. Each profile specifies compute resources to be leased for each service instance uses uses the profile.
# https://docs.akash.network/intro-to-akash/stack-definition-language#profiles.compute
compute:
# The name of the service
web:
resources:
cpu:
units: 0.5
memory:
size: 512Mi
storage:
size: 512Mi
# profiles.placement is map of named datacenter profiles. Each profile specifies required datacenter attributes and pricing configuration for each compute profile that will be used within the datacenter. It also specifies optional list of signatures of which tenants expects audit of datacenter attributes.
# https://docs.akash.network/intro-to-akash/stack-definition-language#profiles.placement
placement:
dcloud:
attributes:
host: akash
signedBy:
anyOf:
- "akash1365yvmc4s7awdyj3n2sav7xfx76adc6dnmlx63"
pricing:
# The name of the service
web:
denom: uakt
amount: 1000
# The deployment section defines how to deploy the services. It is a mapping of service name to deployment configuration.
# https://docs.akash.network/intro-to-akash/stack-definition-language#deployment
deployment:
# The name of the service
web:
dcloud:
profile: web
count: 1