Bekaarcoder’s Blog

As my projects grew, I started using compiled languages—specifically TypeScript.

In my previous post, I successfully got a multi-container database and backend system running.

Up until now, I have only run single containers in isolation.

When containerizing frontend applications like React, Vue, or Angular, you hit a structural fork in the road.

One of the most frustrating things when containerizing applications is waiting for build steps to finish.

One of the core rules of building modern software (according to the famous Twelve-Factor App methodology) is that configuration must be strictly separated from code.

When I first started running docker build ., I noticed a line in my terminal output that read something like: => [internal] load build context => => transferring context: 10.49MB Wait, 10.5 MB?

As I started writing more advanced Dockerfiles, I noticed two instructions that seemed to do almost the exact same thing: CMD and ENTRYPOINT.

Now that I know how to run a basic container, I wanted to build something more practical: a containerized web server that serves a custom webpage.

When I first heard about Docker, it sounded like magic.