rtyler
/
brokenco.de
1
0
Fork 0
Code Pull Requests Releases Activity

Fix some typoes

This commit is contained in:
R. Tyler Croy 2017-04-24 18:05:38 -07:00
parent f01c26d450
commit c3f85066b7
No known key found for this signature in database
GPG Key ID: 1426C7DC3F51E16F
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
_posts/2017-03-14-on-containers-in-production.md
View File

@ -54,7 +54,7 @@ personal and partly for the Jenkins project, the benefits are as follows.
By using containers I enjoy much faster and easier application deployment,
without needing to change any existing infrastructure. In essence,
infrastructure which already exists and is capable of running a Docker
container is capable of running a JavaScript, Python, or Java applications
container is capable of running JavaScript, Python, or Java applications
without any modifications.
For a mostly mixed infrastructure like that of the Jenkins project, this can be
@ -271,8 +271,8 @@ into your containers, and it will most certainly be ugly.
You should no longer be afraid of using contianers in production. There are
certainly caveats and challenges to address, but I assert those downsides are
far outweighed by the benefits to the organization. Astute readers might be
wondering at this point when I will talk about containers and security, but
frankly, I don't see anything novel about security with containers. Firstly, do
wondering at this point, when I will talk about containers and security?
Frankly, I don't see anything novel about security with containers. Firstly, do
not assume containers provide you any additional layer of security. Secondly,
the patch lifecycle, while differently managed compared to traditional package
management, is still more or less the same.