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
This is a default-backend server powered by Nginx. It's purpuse is to serve as a default backend for an ALB default target group with the [`terraform-aws-alb`](https://github.com/cloudposse/terraform-aws-alb) module , much the way a [`nginx-default-backend`](https://github.com/cloudposse/charts/blob/master/incubator/nginx-default-backend/) is used with ingress controllers for kubernetes.
6
9
7
10
The default backend is an HTTP service that handles all URL paths and hosts that the ALB does not understand (i.e., all the requests that are not mapped with an Ingress).
8
11
9
-
Basically, a default backend reponds to two URLs:
12
+
Basically, a default backend responds to two URLs:
10
13
11
14
-`/healthz` that returns 200
12
15
-`/` that returns 404
13
16
14
-
## Demo
15
17
16
-

18
+
---
19
+
20
+
This project is part of our comprehensive ["SweetOps"](https://docs.cloudposse.com) approach towards DevOps.
21
+
22
+
23
+
It's 100% Open Source and licensed under the [APACHE2](LICENSE).
24
+
25
+
26
+
27
+
28
+
## Screenshots
29
+
30
+
31
+

32
+
*Example of the default 404 status page returned by backend*
33
+
17
34
18
35
## Usage
19
36
20
37
```
21
38
docker run -p 1234:80 clouposse/default-backend:latest
22
39
```
23
40
41
+
42
+
43
+
44
+
45
+
46
+
47
+
48
+
## Related Projects
49
+
50
+
Check out these related projects.
51
+
52
+
-[terraform-aws-alb](https://github.com/cloudposse/terraform-aws-alb) - Terraform module to provision a standard ALB for HTTP/HTTP traffic
53
+
-[terraform-aws-alb-ingress](https://github.com/cloudposse/terraform-aws-alb-ingress) - Terraform module to provision an HTTP style ingress rule based on hostname and path for an ALB using target groups
54
+
-[terraform-aws-ecs-web-app](https://github.com/cloudposse/terraform-aws-ecs-web-app) - Terraform module that implements a web app on ECS and supporting AWS resources.
55
+
56
+
57
+
24
58
## Help
25
59
26
60
**Got a question?**
27
61
28
-
File a GitHub [issue](https://github.com/cloudposse/default-backend/issues), send us an [email](mailto:hello@cloudposse.com) or reach out to us on [Slack](https://slack.cloudposse.com).
62
+
File a GitHub [issue](https://github.com/cloudposse/default-backend/issues), send us an [email][email] or join our [Slack Community][slack].
63
+
64
+
## Commerical Support
65
+
66
+
Work directly with our team of DevOps experts via email, slack, and video conferencing.
67
+
68
+
We provide *commercial support* for all of our [Open Source][github] projects. As a *Dedicated Support* customer, you have access to our team of subject matter experts at a fraction of the cost of a fulltime engineer.
-**Questions.** We'll use a Shared Slack channel between your team and ours.
73
+
-**Troubleshooting.** We'll help you triage why things aren't working.
74
+
-**Code Reviews.** We'll review your Pull Requests and provide constructive feedback.
75
+
-**Bug Fixes.** We'll rapidly work to fix any bugs in our projects.
76
+
-**Build New Terraform Modules.** We'll develop original modules to provision infrastructure.
77
+
-**Cloud Architecture.** We'll assist with your cloud strategy and design.
78
+
-**Implementation.** We'll provide hands on support to implement our reference architectures.
79
+
80
+
81
+
## Community Forum
82
+
83
+
Get access to our [Open Source Community Forum][slack] on Slack. It's **FREE** to join 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 *sweet* infrastructure.
29
84
30
85
## Contributing
31
86
@@ -35,22 +90,28 @@ Please use the [issue tracker](https://github.com/cloudposse/default-backend/iss
35
90
36
91
### Developing
37
92
38
-
If you are interested in being a contributor and want to get involved in developing this project, we would love to hear from you! Shoot us an [email](mailto:hello@cloudposse.com).
93
+
If you are interested in being a contributor and want to get involved in developing this project or [help out](https://github.com/orgs/cloudposse/projects/3) with our other projects, we would love to hear from you! Shoot us an [email](mailto:hello@cloudposse.com).
39
94
40
95
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
41
96
42
97
1.**Fork** the repo on GitHub
43
98
2.**Clone** the project to your own machine
44
99
3.**Commit** changes to your own branch
45
100
4.**Push** your work back up to your fork
46
-
5. Submit a **Pull request** so that we can review your changes
101
+
5. Submit a **Pull Request** so that we can review your changes
102
+
103
+
**NOTE:** Be sure to merge the latest changes from "upstream" before making a pull request!
104
+
105
+
106
+
## Copyright
47
107
48
-
**NOTE:** Be sure to merge the latest from "upstream" before making a pull request!
This is a default-backend server powered by Nginx. It's purpuse is to serve as a default backend for an ALB default target group with the [`terraform-aws-alb`](https://github.com/cloudposse/terraform-aws-alb) module , much the way a [`nginx-default-backend`](https://github.com/cloudposse/charts/blob/master/incubator/nginx-default-backend/) is used with ingress controllers for kubernetes.
45
+
46
+
The default backend is an HTTP service that handles all URL paths and hosts that the ALB does not understand (i.e., all the requests that are not mapped with an Ingress).
47
+
48
+
Basically, a default backend responds to two URLs:
49
+
50
+
- `/healthz` that returns 200
51
+
- `/` that returns 404
52
+
53
+
screenshots:
54
+
- name: "Demo"
55
+
description: "Example of the default 404 status page returned by backend"
56
+
url: "docs/demo.png"
57
+
58
+
# How to use this project
59
+
usage: |-
60
+
```
61
+
docker run -p 1234:80 clouposse/default-backend:latest
0 commit comments