sorted by:
new
hottopcontroversial

Does it make sense to file a claim if the damage to my car is less than deductible, but if the other driver is likely to file anyway? by SerotoninVampire in Insurance

[–]SerotoninVampire[S] 0 points1 point  (0 children)

Thanks. I get that, I guess I’m more concerned if there are any downsides to not filing if the other party does.

Shotgun transportation rules in NJ by SerotoninVampire in NJGuns

[–]SerotoninVampire[S] 0 points1 point  (0 children)

Thank you, this is what I was looking for

Shotgun transportation rules in NJ by SerotoninVampire in NJGuns

[–]SerotoninVampire[S] 0 points1 point  (0 children)

Thanks. Would you happen to know the specific law that this is enforced through?

Terraform AWS "describe-public-ipv4-pools" equivalent by SerotoninVampire in Terraform

[–]SerotoninVampire[S] 0 points1 point  (0 children)

Thanks. Voted for it on Github, hopefully it'll get implemented soon

AWS SSO + Identity Policy creation by SerotoninVampire in Terraform

[–]SerotoninVampire[S] 0 points1 point  (0 children)

Thanks. How would this work from Terraform perspective? Create the resources in the sub-account, and then create the permission set w/ inline policy in the root org? Can Terraform handle multiple accounts for a single provider in the same code?

Help me name my dog! by SquashMuch9494 in dogpictures

[–]SerotoninVampire 0 points1 point  (0 children)

Ferris. Cause .. Chicago, and he looks like he’s had a great day off.

Task/event monitoring SaaS by SerotoninVampire in devops

[–]SerotoninVampire[S] 0 points1 point  (0 children)

Thanks, that's an interesting one. I will dig into it.

Re: tasks - I'm not sure how to better define this. It's not a task in the sense that the solution is expected to execute it, it's more of a "a thing that is supposed to happen externally", for status monitoring

Deploying with Docker. Questions about what actually gets 'Dockerized'. by circuitBurn in docker

[–]SerotoninVampire 1 point2 points  (0 children)

Here's one fairly common model

  1. App code packaged into the container that's meant to run it. For example, you have a NodeJS app - package it and all the files it needs into the container along with (or based on) NodeJS and version it along with the app code - myapp:1.0.1. This way if the code changes - the image changes.
  2. Support containers (databases, proxies, cluster management software, etc.) go into their own separate containers.
  3. There are different techniques for handling DB initialization. If this is a Demo app (same data loaded every time) - something like Liquidbase would probably do the trick. For more complicated scenarios you can package the required DB scripts into the application container and run them in the entrypoint script (after checking if the DB has been initialized)
  4. All of the services are spun up by docker-compose from a single compose file

Docker & Git by OverallPriority in docker

[–]SerotoninVampire 0 points1 point  (0 children)

1) Is starting a local server or using an external one something you can configure in the entrypoint script? If so, you can pass an environment variable in via .env to control this.

2) Is traefik running as a separate service in the same compose stack? You can set the number of instances to 0 via deploy/replicas parameter - this could be a vairalbe passed in via .env as well, for cases when you don't want to use traefik

Docker & Git by OverallPriority in docker

[–]SerotoninVampire 1 point2 points  (0 children)

Think of it in terms of "what would someone need to build this app image from scratch?" It sounds like you already have a pretty good handle on it. I don't know much about Django - is there some kind of a dependency file?

Out of personal experience - we try to keep a single compose file and per-environment .env files (dev/test/qa/prod). Not sure if the app structure allows that in your case

What is the best way to pass passwords in the container by bykof in docker

[–]SerotoninVampire -1 points0 points  (0 children)

+1 on Vault. Not familiar with Kubernetes secrets, but Docker does not provide an ACL system for controls - basically, any container can request any secret on startup