151–156 of 156 posts
Docker, really? Sounds like brain surgery in order to make a jam sandwich to me.
I love stuff like this. People will remark about how this is a waste of time, others will say it is absolutely necessary, even more will laud it just for the fun of doing it. I'm in the middle camp. I wish software/systems engineers would spend more time optomising for size and performance.
The difference between a systems engineer and a software engineer is that to a systems engineer a half functioning 5MB docker image is okay but to a software engineer a fully functional 5GB Node image is fine.
Docker, really? Sounds like brain surgery in order to make a jam sandwich to me.
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.
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?
Earlier quoted context omitted.
It's a good way to compartmentalize if you've got a lot going on on a single machine.
> compartmentalize a static website, srsly?
Earlier quoted context omitted.
> compartmentalize a static website, srsly?
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.
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?
Earlier quoted context omitted.
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.
> 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?
...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.