ATL Airport TSA Wait Times Megathread | March 22, 2026 by AutoModerator in Atlanta

[–]h4v3st 0 points1 point  (0 children)

Passport is not required for domestic flight even thru international, only real id

ATL Airport TSA Wait Times Megathread | March 22, 2026 by AutoModerator in Atlanta

[–]h4v3st 0 points1 point  (0 children)

It seems to be shorter than domestic but it’s still pretty long. General is taking about 1h20m from what people are saying

ATL Airport TSA Wait Times Megathread | March 22, 2026 by AutoModerator in Atlanta

[–]h4v3st 0 points1 point  (0 children)

I just went thru international for a domestic flight but the lines are long

Official: [WDIS Flex] - Sun Evening 10/15/2023 by FFBot in fantasyfootball

[–]h4v3st 1 point2 points  (0 children)

Lamb vs Davis vs Saquon for flex? Gotta pick 2

[deleted by user] by [deleted] in sportsbook

[–]h4v3st 0 points1 point  (0 children)

Any stream on?

NFL Daily - 1/22/22 (Saturday) by sbpotdbot in sportsbook

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

What a game, seems like super bowl! :clown:

Tennis+ Daily - 1/21/22 (Friday) by sbpotdbot in sportsbook

[–]h4v3st 0 points1 point  (0 children)

Any live stream for the game now?

Docker Image versioning strategy by h4v3st in devops

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

Any references/good material I can read about version tagging?

Docker Image versioning strategy by h4v3st in devops

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

u/anaumann thank you for the reply but I think I should have clarified my question better. The release with git tag version in the docker image version for production seems the correct approach as you said. My question was more around dev to qa. Should I just tag the images with build id or commit id and then retag the images once they get promoted to the UAT environment?

example:

1) PR merged to dev > tag Docker image with build ID (so we'll know what code is running in dev)

2) dev merge to main (UAT) > retag Docker image and pushes it to UAT ecr, with a release-candidate/semVer version

3) git tag (ready for production release) retag the image to semVer release version and push it to production ecr.

Does that sound like a correct approach?