4 ms·

I am presently developing a project that runs five back-end servers and two front-end servers. I ended up solving the same issues of ports with traefik, like th

by hknmtt 3y ago

I am presently developing a project that runs five back-end servers and two front-end servers. I ended up solving the same issues of ports with traefik, like the author. But it must be said that traefik's configuration is a nightmare to get working as you need it to. Also ssl certificates are still humongous pain in the ass to get going on local machine even in 2023. And you cannot ignore them on local because of those retarded CORS that only bring pain and suffering to the developers and literally nothing to the consumer. I do not use docker compose because each server is in active development so I cannot compile it into an image and I have to spin them all up manually. But I will use docker compose after i am done for front-end developers so they can keep developing the UI locally.

nikita2206 3y ago
> I do not use docker compose because each server is in active development so I cannot compile it into an image I’m curious to know, are you actively developing all 5+2 codebases, or could you theoretically run half of them in docker and another half (the ones you’re actively changing) on the host?
- hknmtt 3y ago
  It is one code base with multiple servers in it. It is a 5x Go + 2x Quasar. Mostly two Go servers are actively developed while the remaining three are quite static with sporadic changes. The UI servers are in active development with hotreload.
  - nikita2206 3y ago
    Aha nice to know thanks!
throwaway6835-8 3y ago
> I do not use docker compose because each server is in active development so I cannot compile it into an image That's something I've seen many times said by many people but I don't understand. Your code can be mounted from the host into the container. There's no need to rebuild images with each change. Inside such "development" container some form of watcher/auto-rebuild can run and recompile & restart your program after changes are made in code. Isn't it standard practice?
- hknmtt 3y ago
  By definition containers are static. Of course I could use them but it would essentially only add one step into the build process and I would gain absolutely noting from it. And I have no reason to use containers only for the sake of using them.
  - throwaway6835-8 3y ago
    > I would gain absolutely noting from it What about isolation? Of runtime, ports, dependencies?
    - hknmtt 3y ago
      I already have that. Plus, you might have missed that I am talking about development environment.
StrangeSmells01 3y ago
> I do not use docker compose because each server is in active development so I cannot compile it into an image I think a lot of people here can't imagine how this is possible. Docker is literally just the same thing as what's running on the server except in a chroot environment. And it gives you a ton of benefits like isolation, portability, infrastructure as code, a layer of security, etc.

by hknmtt 3y ago

nikita2206 3y ago

> I do not use docker compose because each server is in active development so I cannot compile it into an image I’m curious to know, are you actively developing all 5+2 codebases, or could you theoretically run half of them in docker and another half (the ones you’re actively changing) on the host?

hknmtt 3y ago
It is one code base with multiple servers in it. It is a 5x Go + 2x Quasar. Mostly two Go servers are actively developed while the remaining three are quite static with sporadic changes. The UI servers are in active development with hotreload.
- nikita2206 3y ago
  Aha nice to know thanks!

throwaway6835-8 3y ago

> I do not use docker compose because each server is in active development so I cannot compile it into an image That's something I've seen many times said by many people but I don't understand. Your code can be mounted from the host into the container. There's no need to rebuild images with each change. Inside such "development" container some form of watcher/auto-rebuild can run and recompile & restart your program after changes are made in code. Isn't it standard practice?

hknmtt 3y ago
By definition containers are static. Of course I could use them but it would essentially only add one step into the build process and I would gain absolutely noting from it. And I have no reason to use containers only for the sake of using them.
- throwaway6835-8 3y ago
  > I would gain absolutely noting from it What about isolation? Of runtime, ports, dependencies?
  - hknmtt 3y ago
    I already have that. Plus, you might have missed that I am talking about development environment.

StrangeSmells01 3y ago

> I do not use docker compose because each server is in active development so I cannot compile it into an image I think a lot of people here can't imagine how this is possible. Docker is literally just the same thing as what's running on the server except in a chroot environment. And it gives you a ton of benefits like isolation, portability, infrastructure as code, a layer of security, etc.