• 1 Post
  • 42 Comments
Joined 2 years ago
cake
Cake day: June 8th, 2023

help-circle

  • The & is an indicator to most shells to run this command in “the background”. Try and run ( sleep 10; echo hi ) & - you’ll see you get your shell prompt back, where you can run more commands, but 10 second later you’ll see that ‘hi’ come through. ‘blocking’ is the default behavior, if you don’t add the & you’re still going get the hi in ten seconds, but you don’t get a prompt because your shell’s execution is blocked until your command is done.

    The doc here is indicating that you havea choice between autostart_blocking.sh and autostart.sh, the latter of which would be run with a &. They could have expressed this better.

    As for why your script didn’t work, I’d try executing it in a terminal to see what error message comes up.



  • check out Supreme Commander, it’s a game from the erra of good RTSes, and I think has some of the features you’re taking about, e.g. beforehand of multiple bases, automation… you can do things like produce x units, send them to this area, have them start doing this patrol, etc. You can pause the game, to make these orders too. My favorite gimmick though, is that the map is zoomable, from a classic here’s your dudes and tanks view, up into a strategic view with icons representing everything. This also opens up the ability to have units be different sizes. vehicles are appropriately larger than infantry, and you can have giant mechs to which other units are literally ants.










  • Not sure what you’re doing, but if we’re talking about a bog standard service backed by a db, I don’t think having automated reverts of that data is the best idea. you might lose something! That said, triggering a snapshot of your db as a step before deployment is a pretty reasonable idea.

    Reverting a service back to a previous version should be straightforward enough, and any dedicated ci/cd tool should have an API to get you information from the last successful deploy, whether that is the actual artifact you’re deploying, or a reference to a registry.

    As you’re probably entirely unsurprised by, there are a ton of ways to skin this cat. you might consider investing in preventative measures, testing your data migration in a lower environment, splitting out db change commits from service logic commits, doing some sort of blue/green or canary deployment.

    I get fairly nerd-sniped when it comes to build pipelines so happy to talk more concretely if you’d like to provide some more details!