4 ms·

Docker, really? Sounds like brain surgery in order to make a jam sandwich to me.

by mro_name 5y ago

Casteil 5y ago
It's a good way to compartmentalize if you've got a lot going on on a single machine.
- mro_name 5y ago
  > compartmentalize a static website, srsly?
  - Casteil 5y ago
    Uh, yeah? Could host dozens (or even hundreds) of different sites/domains with different degrees of functionality in different languages/frameworks for different clients on one machine.
    - mro_name 5y ago
      > have millions of files Congratulations. I have millions of files on my static sites. So what? Would you recommend a container for each? To what purpose? > different degrees of functionality We're still talking static sites. There is no 'functionality', right?
      - Casteil 5y ago
        > Congratulations. I have millions of files on my static sites. So what? Would you recommend a container for each? To what purpose? ...what? Where are you quoting that from? No, I'm not recommending Docker if all you do is host static pages. > We're still talking static sites. No, I said "if you've got a lot going on on a single machine" - I didn't just mean static sites. I did respond with "different sites/domains with different degrees of functionality in different languages/frameworks", which means a variety of services, e.g. one client may be a static page, another might use a backend/API in Node, and another in C#/.NET - etc.. heck, you might even used containerized DBs for some of them. Hence Docker.
nilsandrey 5y ago
Locally could be easier to rely on background run of a docker image instead of another console serving the files, just to run and forget, just use it by the dependent project you probably could be working on (Dependent on the static content). I'm agreed on the cloud it's better use the plethora of services available for static content directly like Cloudflare.
- mro_name 5y ago
  > plethora of services available for static content when I think of static content, I think of buying a domain name + shared hosting for monthly EUR 2,-. And not assigning rights nor control but having a legal claim on both service and name. Am I missing something?

Docker, really? Sounds like brain surgery in order to make a jam sandwich to me.

Casteil 5y ago

It's a good way to compartmentalize if you've got a lot going on on a single machine.

mro_name 5y ago
> compartmentalize a static website, srsly?
- Casteil 5y ago
  Uh, yeah? Could host dozens (or even hundreds) of different sites/domains with different degrees of functionality in different languages/frameworks for different clients on one machine.
  - mro_name 5y ago
    > have millions of files Congratulations. I have millions of files on my static sites. So what? Would you recommend a container for each? To what purpose? > different degrees of functionality We're still talking static sites. There is no 'functionality', right?
    - Casteil 5y ago
      > Congratulations. I have millions of files on my static sites. So what? Would you recommend a container for each? To what purpose? ...what? Where are you quoting that from? No, I'm not recommending Docker if all you do is host static pages. > We're still talking static sites. No, I said "if you've got a lot going on on a single machine" - I didn't just mean static sites. I did respond with "different sites/domains with different degrees of functionality in different languages/frameworks", which means a variety of services, e.g. one client may be a static page, another might use a backend/API in Node, and another in C#/.NET - etc.. heck, you might even used containerized DBs for some of them. Hence Docker.

nilsandrey 5y ago

Locally could be easier to rely on background run of a docker image instead of another console serving the files, just to run and forget, just use it by the dependent project you probably could be working on (Dependent on the static content). I'm agreed on the cloud it's better use the plethora of services available for static content directly like Cloudflare.

mro_name 5y ago
> plethora of services available for static content when I think of static content, I think of buying a domain name + shared hosting for monthly EUR 2,-. And not assigning rights nor control but having a legal claim on both service and name. Am I missing something?