-
Notifications
You must be signed in to change notification settings - Fork 0
/
modules.yml
35 lines (32 loc) · 1.61 KB
/
modules.yml
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
# Namespaces are groupings of modules, meant to group them by use case or by
# modules that are known to work well together. That doesn't necessarily mean
# you can't mix and match, it's just meant to be descriptive.
namespaces:
# The name of the module. When the user pulls the module, it will look like
# <namespace>/<module>
- name: examples
description: |
Example modules that are meant to demonstrate various concepts and should
not be used in a real deployment.
modules:
# This is an example of a module made for an image build. All Cloudless
# modules have a blueprint, but this one also includes an image build
# configuration to build and save an image based on that blueprint.
- name: "base-image"
url: "https://github.com/getcloudless/example-base-image"
image_build_configuration: "image_build_configuration.yml"
description: "Example of how to build a base image with Cloudless."
# These are examples of modules made for service deployment. All Cloudless
# modules have a blueprint, but this one also inclues a service test
# configuration to deploy a temporary test service and verify it works.
- name: "apache"
url: "https://github.com/getcloudless/example-apache"
service_test_configuration: "service_test_configuration.yml"
description: |
Example of how to deploy a simple Apache server with Cloudless.
- name: "haproxy"
url: "https://github.com/getcloudless/example-haproxy"
service_test_configuration: "service_test_configuration.yml"
description: |
Example of how to deploy a service requiring template variables (Haproxy)
with Cloudless.