5 ms·

So he basically followed it's the future story? (https://circleci.com/blog/its-the-future/ https://circleci.com/blog/its-the-future/)

by vittore 10y ago

gkop 10y ago
For what it's worth, CircleCI is going all-in on containers: https://circleci.com/blog/say-hello-to-circleci-2-0/ https://circleci.com/blog/say-hello-to-circleci-2-0/
devoply 10y ago
Now he can finally deploy WordPress.
- vittore 10y ago
  You did not read it lol, he deployed Ghost!
  - devoply 10y ago
    You caught me :( But close enough. Point being overkill.
tracker1 10y ago
While funny, there are uses for the types of orchestration that containers can provide... for me, it's kind of awesome that finding a script for an automated deployment of any subject is now as simple as searching: <subject> dockerfile And voila, I have the steps to install <subject> ... ;-) I'm being a little snarky, but I do think that the dockerfile is pretty cool by itself, and wouldn't even mind seeing other automation frameworks use the dockerfile and the swarm configs for other purposes.
- toomuchtodo 10y ago
  For sure! But please, for the love of Vint Cerf, don't go into production with boilerplate containerization configs.
  - tracker1 10y ago
    I usually just start with the published dockerfiles and modify as needed... Really depends on my own usage.
- vittore 10y ago
  Well, it is funny, because after all that he just installed Ghost on it. We are using containers for pretty much same purpose - try it out different things and just throw it onto one of our dokku boxes - fast and easy way to play with something without investing heavily.
joesmo 10y ago
Lol. I was thinking similarly. If this is what you need to do to get Kubernets up in production, Kubernetes is far from production ready. Sadly, this type of UX is the norm in the ops world and everyone is expected to build out a custom in-house solution on top even though everyone is doing the exact same thing. AWS was built on this insane model, promising companies that they don't need operations when the need was shifted from hardware onto software, not eliminated. The devops movement has decided it is also fine with this as long as they can automate the dozens of moving parts using dozens of other moving parts. Surely nothing will fail then. Even products that manage a really great UX like Docker itself fail when it comes to providing a proper UX for higher level tools like docker swarm. I'd like to think that the industry is moving forward towards better, higher-level abstractions (like Kubernets or Heroku) but it seems to me it's only moving sideways, just like it did with the adoption of VMs.
discordianfish 10y ago
Pretty much! :) No, for real: It looks like I failed to communicate the intent very well. I do NOT recommend setting up such infrastructure for running Ghost. I do recommend such setup (not necessarily on DO though), if you have a sufficiently complex stack and you want to be able to deploy to it quickly. This is often the case if you're have multiple teams who want to deploy independently and you can't wait for building and spinning up VM images. Or if you're running on bare metal and can't get away with something like Docker + a few shell scripts. In my case I just run this way-to-complex-stack because I've worked in the space (at Docker and Mesosphere to be specific) and want to stay in touch with the space.

So he basically followed it's the future story? (https://circleci.com/blog/its-the-future/ https://circleci.com/blog/its-the-future/)

by vittore 10y ago

So he basically followed it's the future story? (https://circleci.com/blog/its-the-future/ https://circleci.com/blog/its-the-future/)

gkop 10y ago

For what it's worth, CircleCI is going all-in on containers: https://circleci.com/blog/say-hello-to-circleci-2-0/ https://circleci.com/blog/say-hello-to-circleci-2-0/

devoply 10y ago

Now he can finally deploy WordPress.

vittore 10y ago
You did not read it lol, he deployed Ghost!
- devoply 10y ago
  You caught me :( But close enough. Point being overkill.

tracker1 10y ago

While funny, there are uses for the types of orchestration that containers can provide... for me, it's kind of awesome that finding a script for an automated deployment of any subject is now as simple as searching: <subject> dockerfile And voila, I have the steps to install <subject> ... ;-) I'm being a little snarky, but I do think that the dockerfile is pretty cool by itself, and wouldn't even mind seeing other automation frameworks use the dockerfile and the swarm configs for other purposes.

toomuchtodo 10y ago
For sure! But please, for the love of Vint Cerf, don't go into production with boilerplate containerization configs.
- tracker1 10y ago
  I usually just start with the published dockerfiles and modify as needed... Really depends on my own usage.
vittore 10y ago
Well, it is funny, because after all that he just installed Ghost on it. We are using containers for pretty much same purpose - try it out different things and just throw it onto one of our dokku boxes - fast and easy way to play with something without investing heavily.

joesmo 10y ago

Lol. I was thinking similarly. If this is what you need to do to get Kubernets up in production, Kubernetes is far from production ready. Sadly, this type of UX is the norm in the ops world and everyone is expected to build out a custom in-house solution on top even though everyone is doing the exact same thing. AWS was built on this insane model, promising companies that they don't need operations when the need was shifted from hardware onto software, not eliminated. The devops movement has decided it is also fine with this as long as they can automate the dozens of moving parts using dozens of other moving parts. Surely nothing will fail then. Even products that manage a really great UX like Docker itself fail when it comes to providing a proper UX for higher level tools like docker swarm. I'd like to think that the industry is moving forward towards better, higher-level abstractions (like Kubernets or Heroku) but it seems to me it's only moving sideways, just like it did with the adoption of VMs.

discordianfish 10y ago

Pretty much! :) No, for real: It looks like I failed to communicate the intent very well. I do NOT recommend setting up such infrastructure for running Ghost. I do recommend such setup (not necessarily on DO though), if you have a sufficiently complex stack and you want to be able to deploy to it quickly. This is often the case if you're have multiple teams who want to deploy independently and you can't wait for building and spinning up VM images. Or if you're running on bare metal and can't get away with something like Docker + a few shell scripts. In my case I just run this way-to-complex-stack because I've worked in the space (at Docker and Mesosphere to be specific) and want to stay in touch with the space.