more styling

This commit is contained in:
Adam Wiggins
2011-06-03 01:26:30 -07:00
parent d8e91f9a56
commit 75eca714b2
5 changed files with 45 additions and 22 deletions
+5 -5
View File
@@ -3,10 +3,10 @@ Abtract
Modern software is almost always delivered as a service: called *web apps*, or *software-as-a-service*. The twelve-factor app is a methodology for building software-as-a-service apps that:
* Use declarative formats for setup automation, to minimize time and cost of a new developer joining the project;
* Have a clean contract with the underlying operating system, offering maximum portability between runtime environments;
* Are suitable for deployment on modern cloud platforms, obviating the need for servers and systems administration;
* Minimize divergence between development and production, enabling continuous deployment for maximum agility;
* And can scale up without significant changes to tooling, architecture, or development practices.
* Use **declarative** formats for setup **automation**, to minimize time and cost of a new developer joining the project;
* Have a **clean contract** with the underlying operating system, offering **maximum portability** between execution environments;
* Are suitable for **deployment** on modern **cloud platforms**, obviating the need for servers and systems administration;
* **Minimize divergence** between development and production, **enabling continuous** deployment for maximum agility;
* And can **scale up** without significant changes to tooling, architecture, or development practices.
The twelve-factor methodology can be applied to apps written in any programming language, and which use any combination of backing services (database, queue, memory cache, etc).
+11 -11
View File
@@ -1,35 +1,35 @@
The Twelve Factors
==================
## 0. Repo
## I. Repo
### One code repo, many deploys
## 1. Dependencies
## II. Dependencies
### Explicit dependency declaration and isolation
## 2. Config
## III. Config
### Store config in the environment
## 3. Backing Services
## IV. Backing Services
### Treat backing services as attached resources
## 4. Build, release, run
## V. Build, release, run
### Separate build and run stages
## 5. Processes
## VI. Processes
### Stateless, disposable processes handle application logic
## 6. Port binding
## VII. Port binding
### Services exported via port binding
## 7. Concurrency
## VIII. Concurrency
### Scale up via the process model
## 8. Dev/prod parity
## IX. Dev/prod parity
### Parity between development and production
## 9. Logs
## X. Logs
### Logs are event streams
## 10. Admin processes
## XI. Admin processes
### One-off admin/management tasks
+1 -1
View File
@@ -1,4 +1,4 @@
Who should read this document?
==============================
Any developer building applications run as a service.
Any developer building applications run as a service, and ops engineers who deploy or run such applications.
+27 -5
View File
@@ -2,6 +2,7 @@ body {
margin: 0;
padding: 0;
font-family: Georgia, sans-serif;
line-height: 1.5em;
}
h1, h2, h3 {
@@ -11,13 +12,14 @@ h1, h2, h3 {
header {
margin: 0;
padding: 24pt;
padding: 26pt;
border: 1px solid black;
color: #fff;
background: #000;
font-size: 200%;
font-size: 22pt;
text-align: center;
box-shadow: 0px 2px 6px #888;
box-shadow: 0px 2px 12px #888;
margin-bottom: 12pt;
}
section {
@@ -25,7 +27,8 @@ section {
padding-top: 16pt;
}
section h1 {
font-size: 150%;
font-size: 18pt;
border-bottom: 2px solid #aaa;
}
article {
@@ -34,9 +37,28 @@ article {
section#toc {
background: #ccc;
margin-top: 32pt;
margin-top: 24pt;
padding-top: 32pt;
padding-bottom: 32pt;
}
section#toc h1 {
font-size: 32pt;
border: 0;
margin-bottom: 24pt;
}
section#toc h2 {
margin-top: 12pt;
}
section#toc h3 {
font-weight: normal;
}
footer {
color: #444;
font-size: 12pt;
background: #000;
box-shadow: 0px -2px 12px #888;
height: 48pt;
padding-top: 64pt;
padding-left: 64pt;
}
+1
View File
@@ -23,4 +23,5 @@
</div>
<footer>
<div>Copyright &copy; <%= Time.now.year %> Adam Wiggins</div>
</footer>