You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -37,14 +37,6 @@ Let's jump right in! Here's how to get started with our documentation.
37
37
---
38
38
39
39
This project is part of our comprehensive ["SweetOps"](https://cpco.io/sweetops) approach towards DevOps.
40
-
[<imgalign="right"title="Share via Email"src="https://docs.cloudposse.com/images/ionicons/ios-email-outline-2.0.1-16x16-999999.svg"/>][share_email]
41
-
[<imgalign="right"title="Share on Google+"src="https://docs.cloudposse.com/images/ionicons/social-googleplus-outline-2.0.1-16x16-999999.svg" />][share_googleplus]
42
-
[<imgalign="right"title="Share on Facebook"src="https://docs.cloudposse.com/images/ionicons/social-facebook-outline-2.0.1-16x16-999999.svg" />][share_facebook]
43
-
[<imgalign="right"title="Share on Reddit"src="https://docs.cloudposse.com/images/ionicons/social-reddit-outline-2.0.1-16x16-999999.svg" />][share_reddit]
44
-
[<imgalign="right"title="Share on LinkedIn"src="https://docs.cloudposse.com/images/ionicons/social-linkedin-outline-2.0.1-16x16-999999.svg" />][share_linkedin]
45
-
[<imgalign="right"title="Share on Twitter"src="https://docs.cloudposse.com/images/ionicons/social-twitter-outline-2.0.1-16x16-999999.svg" />][share_twitter]
46
-
47
-
48
40
49
41
50
42
@@ -64,8 +56,6 @@ It's 100% Open Source and licensed under the [Creative Commons Attribution-NonCo
64
56
65
57
66
58
67
-
68
-
69
59
## Usage
70
60
71
61
@@ -93,36 +83,66 @@ Available targets:
93
83
help Help screen
94
84
help/all Display help for all targets
95
85
help/short This help short screen
86
+
deps Install node modules
87
+
deps-production Install production only node modules
88
+
build Generate all static content (outputs to build/) using docker environment
89
+
start Start web server locally
90
+
real-clean Clean all dependencies and generated html files
91
+
all Run `clean`, `deps` and `build steps
96
92
97
93
```
98
94
<!-- markdownlint-restore -->
99
95
100
96
97
+
## Related Projects
101
98
102
-
## Share the Love
99
+
Check out these related projects.
103
100
104
-
Like this project? Please give it a ★ on [our GitHub](https://github.com/cloudposse/docs)! (it helps us **a lot**)
101
+
-[Geodesic](https://github.com/cloudposse/geodesic) - Geodesic is the fastest way to get up and running with a rock solid, production grade cloud platform
105
102
106
-
Are you using this project or any of our other projects? Consider [leaving a testimonial][testimonial]. =)
103
+
## ✨ Contributing
107
104
105
+
This project is under active development, and we encourage contributions from our community.
Please use the [issue tracker](https://github.com/cloudposse/docs/issues) to report any bugs or file feature requests.
113
115
114
-
-[Geodesic](https://github.com/cloudposse/geodesic) - Geodesic is the fastest way to get up and running with a rock solid, production grade cloud platform
116
+
### 💻 Developing
115
117
116
-
## Help
118
+
If you are interested in being a contributor and want to get involved in developing this project or [help out](https://cpco.io/help-out) with our other projects, we would love to hear from you! Shoot us an [email][email].
117
119
118
-
**Got a question?**We got answers.
120
+
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
119
121
120
-
File a GitHub [issue](https://github.com/cloudposse/docs/issues), send us an [email][email] or join our [Slack Community][slack].
122
+
1.**Fork** the repo on GitHub
123
+
2.**Clone** the project to your own machine
124
+
3.**Commit** changes to your own branch
125
+
4.**Push** your work back up to your fork
126
+
5. Submit a **Pull Request** so that we can review your changes
**NOTE:** Be sure to merge the latest changes from "upstream" before making a pull request!
129
+
130
+
### 🌎 Slack Community
131
+
132
+
Join our [Open Source Community][slack] on Slack. It's **FREE** for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally *sweet* infrastructure.
133
+
134
+
### 📰 Newsletter
135
+
136
+
Sign up for [our newsletter][newsletter] that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
We are a [**DevOps Accelerator**][commercial_support]. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.
128
148
@@ -143,52 +163,7 @@ We deliver 10x the value for a fraction of the cost of a full-time engineer. Our
143
163
-**Code Reviews.** You'll receive constructive feedback on Pull Requests.
144
164
-**Bug Fixes.** We'll rapidly work with you to fix any bugs in our projects.
145
165
146
-
## Slack Community
147
-
148
-
Join our [Open Source Community][slack] on Slack. It's **FREE** for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally *sweet* infrastructure.
149
-
150
-
## Discourse Forums
151
-
152
-
Participate in our [Discourse Forums][discourse]. Here you'll find answers to commonly asked questions. Most questions will be related to the enormous number of projects we support on our GitHub. Come here to collaborate on answers, find solutions, and get ideas about the products and services we value. It only takes a minute to get started! Just sign in with SSO using your GitHub account.
153
-
154
-
## Newsletter
155
-
156
-
Sign up for [our newsletter][newsletter] that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
157
-
158
-
## Office Hours
159
-
160
-
[Join us every Wednesday via Zoom][office_hours] for our weekly "Lunch & Learn" sessions. It's **FREE** for everyone!
Please use the [issue tracker](https://github.com/cloudposse/docs/issues) to report any bugs or file feature requests.
169
-
170
-
### Developing
171
-
172
-
If you are interested in being a contributor and want to get involved in developing this project or [help out](https://cpco.io/help-out) with our other projects, we would love to hear from you! Shoot us an [email][email].
173
-
174
-
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
175
-
176
-
1.**Fork** the repo on GitHub
177
-
2.**Clone** the project to your own machine
178
-
3.**Commit** changes to your own branch
179
-
4.**Push** your work back up to your fork
180
-
5. Submit a **Pull Request** so that we can review your changes
181
-
182
-
**NOTE:** Be sure to merge the latest changes from "upstream" before making a pull request!
@@ -209,45 +184,11 @@ Distribution of substantively modified versions of this document is prohibited w
209
184
210
185
Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder.
211
186
212
-
213
-
214
-
215
-
216
-
217
-
218
-
219
187
## Trademarks
220
188
221
189
All other trademarks referenced herein are the property of their respective owners.
222
-
223
-
## About
224
-
225
-
This project is maintained and funded by [Cloud Posse, LLC][website]. Like it? Please let us know by [leaving a testimonial][testimonial]!
226
-
227
-
[![Cloud Posse][logo]][website]
228
-
229
-
We're a [DevOps Professional Services][hire] company based in Los Angeles, CA. We ❤️ [Open Source Software][we_love_open_source].
230
-
231
-
We offer [paid support][commercial_support] on all of our projects.
232
-
233
-
Check out [our other projects][github], [follow us on twitter][twitter], [apply for a job][jobs], or [hire us][hire] to help with your cloud strategy and implementation.
All of our Terraform modules have automated tests. We have two sets of checks:
8
+
All of our Terraform modules have automated tests. We have two sets of checks:
9
9
10
-
- The first set of checks is executed through the feature-branch workflow, which can be found [here](https://github.com/cloudposse/github-actions-workflows-terraform-module/blob/main/.github/workflows/feature-branch.yml)
10
+
- The first set of checks is executed through the feature-branch workflow, which can be found [here](https://github.com/cloudposse/github-actions-workflows-terraform-module/blob/main/.github/workflows/feature-branch.yml)
11
11
This workflow generates some documentation and performs basic sanity checks, including linting and formatting. These checks are lightweight and can be executed without requiring any special permissions. Consequently, they *are automatically run* on every commit.
12
12
Before committing and pushing your changes, you can and should run this set of checks locally by executing the following command on your host
13
13
```
@@ -58,9 +58,8 @@ To initialize one of our modules with chatops, run the following commands:
58
58
1.`git clone` the terraform module repository
59
59
1.`cd $repo` to enter the repository directory
60
60
1.`make init` to initialize the build-harness
61
-
1.`make github/init` to write all the scaffolding
62
61
1.`git add *` to add the changes
63
-
1. Add the build badge to the `README.yaml` under the `badges` section.
62
+
1. Add the build badge to the `README.yaml` under the `badges` section.
64
63
1.`make readme` to rebuild the `README.md` (remember, never edit the `README.md` manually since it's generated from the `README.yaml`)
65
-
1. Open up a Pull Request with the changes. Here is a [good example](https://github.com/cloudposse/terraform-github-repository-webhooks/pull/17).
64
+
1. Open up a Pull Request with the changes. Here is a [good example](https://github.com/cloudposse/atmos/pull/555).
66
65
1. Request a Code Review in the [`#pr-reviews`](https://slack.cloudposse.com) Slack channel (and *big* thanks for your contribution!)
`atmos` is both a command-line tool and Golang module for provisioning, managing and orchestrating workflows across various toolchains including `terraform` and `helmfile`.
11
11
12
-
The `atmos` tool is part of the SweetOps toolchain and was built to make DevOps and Cloud automation easier across multiple tools. It has direct support for automating Terraform, Helmfile. By utilizing [Stacks](/reference-architecture/fundamentals/tools/stacks), `atmos` enable you to effortlessly manage your Terraform and Helmfile [Components](/components) from your local machine, in your CI/CD pipelines, or using [spacelift](/components/library/aws/spacelift/).
12
+
The `atmos` tool is part of the SweetOps toolchain and was built to make DevOps and Cloud automation easier across multiple tools. It has direct support for automating Terraform, Helmfile. By utilizing [Stacks](/fundamentals/stacks), `atmos` enable you to effortlessly manage your Terraform and Helmfile [Components](/components) from your local machine, in your CI/CD pipelines, or using [spacelift](/components/library/aws/spacelift/).
13
13
14
14
## Problem
15
15
A modern infrastructure depends on lots of various tools like terraform, packer, helmfile, helm, kubectl, docker, etc. All these tools have varying degrees of configuration support, but most are not optimized for defining DRY configurations across dozens or hundreds of environments. Moreover, the configuration format is very different between the tools, but usually, boils down to some kind of key-value configuration in either JSON or YAML. This lack of configuration consistency poses a problem when we want to make it easy to declaratively define the settings that end-users should care about.
@@ -313,7 +313,7 @@ For example, to run the `deploy-all` workflow from the [workflows](https://githu
313
313
## Recommended Filesystem Layout
314
314
315
315
:::info
316
-
For an example of what this looks like within [Geodesic](/reference-architecture/fundamentals/tools/geodesic) see the section on “Filesystem Layout”
316
+
For an example of what this looks like within [Geodesic](/fundamentals/geodesic) see the section on “Filesystem Layout”
317
317
318
318
:::
319
319
@@ -356,7 +356,7 @@ infrastructure/
356
356
357
357
Atmos supports a CLI configuration to define configure the behavior working with stacks and components.
358
358
359
-
In [Geodesic](/reference-architecture/fundamentals/tools/geodesic) we typically put this in `/usr/local/etc/atmos/atmos.yaml` (e.g. in `rootfs/...` in the `infrastructure` repository). Note this file uses the stack config format for consistency, but we do not consider it a stack configuration.
359
+
In [Geodesic](/fundamentals/geodesic) we typically put this in `/usr/local/etc/atmos/atmos.yaml` (e.g. in `rootfs/...` in the `infrastructure` repository). Note this file uses the stack config format for consistency, but we do not consider it a stack configuration.
360
360
361
361
The CLI config is loaded from the following locations (from lowest to highest priority):
0 commit comments