Deployment/2017: Difference between revisions
From charlesreid1
No edit summary |
m (Admin moved page Deployment to Deployment/2017) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Deployment is about getting the infrastructure you need, and getting it all ready/set/go for launching and running lots of services. | Deployment is about getting the infrastructure you need, and getting it all ready/set/go for launching and running lots of services. | ||
Most important deployment page is here: [[Deployment/New Node Checklist]] | |||
==2018== | |||
Droplet deployment guide: [[Deployment/Wisko]] | |||
==Deployment Guides== | |||
This is a guide to small scale (handful of nodes) deployment, bare metal to Docker: [[Deployment/New Node Checklist]] | |||
This is a coverage of boats (groups of Docker containers that ship together) and where you can go once you've gotten Docker running: [[Docker/Boats]] | |||
==More About Deploying== | |||
===Small scale=== | |||
You can do this on a small scale, as I've documented in a couple of places: | You can do this on a small scale, as I've documented in a couple of places: | ||
| Line 5: | Line 21: | ||
* [[Droplet]] (old but still useful procedure) | * [[Droplet]] (old but still useful procedure) | ||
* [[Geodroplet]] (old but still useful procedure) | * [[Geodroplet]] (old but still useful procedure) | ||
===Big scale=== | |||
if you deploy on a big scale, you can't rely on things like hard-coded IP addresses, so you use a load balancer that takes care of things on the backend. Then you just point all requests for your app or your service to the (backend) domain that handles the requests without busting a sweat. | |||
===Deployment tooling=== | |||
Tooling: | Tooling: | ||
| Line 14: | Line 36: | ||
* [[Docker/Boats]] (boats are the groups of containers that I assemble for different purposes) | * [[Docker/Boats]] (boats are the groups of containers that I assemble for different purposes) | ||
==Flags== | |||
[[Category:Linux]] | [[Category:Linux]] | ||
[[Category:Server]] | [[Category:Server]] | ||
[[Category:Deployment]] | [[Category:Deployment]] | ||
Latest revision as of 03:14, 28 February 2018
Deployment is about getting the infrastructure you need, and getting it all ready/set/go for launching and running lots of services.
Most important deployment page is here: Deployment/New Node Checklist
2018
Droplet deployment guide: Deployment/Wisko
Deployment Guides
This is a guide to small scale (handful of nodes) deployment, bare metal to Docker: Deployment/New Node Checklist
This is a coverage of boats (groups of Docker containers that ship together) and where you can go once you've gotten Docker running: Docker/Boats
More About Deploying
Small scale
You can do this on a small scale, as I've documented in a couple of places:
- Deployment/New Node Checklist (new procedure)
- Droplet (old but still useful procedure)
- Geodroplet (old but still useful procedure)
Big scale
if you deploy on a big scale, you can't rely on things like hard-coded IP addresses, so you use a load balancer that takes care of things on the backend. Then you just point all requests for your app or your service to the (backend) domain that handles the requests without busting a sweat.
Deployment tooling
Tooling:
- If you are going from bare metal to basic functional systems, can use things like Puppet or Chef. Back in the day it was Norton Ghost. Or a classroom filled with laptops that you installed an OS onto by hand.
Basic functional system to running apps and services by using Docker and Docker containers.
- Docker/Dockerhub (docker hub is where you get your containers)
- Docker/Basics (this is how you run your containers)
- Docker/Boats (boats are the groups of containers that I assemble for different purposes)