533 karma · joined November 18, 2012
It's a sleazy practice and it irks me that some people just shrug about it.
How is that less concerning? Rewording conclusions or the abstract, even subtly, can change the meaning of those words and of those sections.
I'm also trying to learn Docker Swarm mode and both the community and documentation are not as nearly comprehensive as Kubernetes'. And Docker's official documentation and tutorial has me provisioning 3 nodes on a cloud provider instead of just booting up a swarm on my local machine.
And then I see any # of combinations of Docker Swarm with tools like Terraform or Pulumi. It's just all so overwhelming.
I think I'm going to keep banging my head with Kube and its super verbose manifests until I finally get it.
https://docs.docker.com/cloud/aci-compose-features/ https://docs.docker.com/cloud/ecs-compose-features/
https://docs.docker.com/cloud/aci-compose-features/ https://docs.docker.com/cloud/ecs-compose-features/
https://docs.docker.com/cloud/aci-compose-features/
https://docs.docker.com/cloud/ecs-compose-features/
I haven't (successfully) used ACI to deploy my compose app. I'm hoping somebody else on this thread might have.
If you're into domain-driven design, I find F# makes it easier to model your code after your line of business. I also like how F# nudges my code into an "onion-layer" architecture, where the domain of my business logic is at the core and is wrapped around with functionality like reading and validating inputs from external sources.
I also like Elm and the idea of ReasonML, so I plan to seriously check out Fable, which compiles F# to Javascript, and Elmish. There's also Saturn, which is built on top of asp.net-core
What does hero-code mean?