So today I discovered that there's a cron job that holds non-reproducible state that died, and now our system is fucked.

The cron job doesn't live inside any source control. This morning it entered a terminal state, and because it overwrites its state there's no way to revert it.

I'm currently waiting for the database rollback and have rewritten it in a reproducible/idempotent way.

you are viewing a single comment's thread
view the rest of the comments
[–] 141 points 1 year ago (17 children)
  • [–] [S] 117 points 1 year ago (14 children)

    He does charge a consulting fee to "fix" these issues

    Almost all of them are dumb shit like this, where something is built in super hacky and dumbass ways.

  • source
  • parent
  • hideshow 14 child comments
  • [–] 59 points 1 year ago* (2 children)

    Smart man. This is how we fight being replaced by AI.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 14 points 1 year ago (9 children)

    Super hacky and dumb? Sign me up 😂

  • source
  • parent
  • hideshow 9 child comments
  • [–] 8 points 1 year ago (8 children)

    Me running all my services in tmux

  • source
  • parent
  • hideshow 8 child comments
  • [–] 4 points 1 year ago (6 children)

    that might be a stupid question, but why would you running all services in tmux be a bad idea? a co-worker of mine is doing exactly that right now, which is why I'm asking.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 4 points 1 year ago (4 children)

    It's not horrible, like it'll do the job just fine, it's just probably a better idea to use systemd and like, containers and whatnot, but I couldn't be arsed to fiddle with all that for Jellyfin, caddy reverse proxy, and two modded Minecraft servers, so shell scripts and tmux won the day. It takes a little extra time to restart everything after an update, and maybe I'll get the motivation to do things "correctly™" one day, but today is not that day.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 6 points 1 year ago* (2 children)

    Use the tmux resurrect plugin. It will restore your tmux session to its previous state after a restart, including programs if you like.

    You can put off doing things "correctly™" even longer.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 1 year ago (1 child)

    The "here's how you keep doing this poorly but more efficiently" energy on display here is a refreshing change of pace from the usual "here's how you do this correctly" crap peddled by normies (including me). You have my respect.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago* (last edited 1 year ago)
    1. They're all gone when you restart
    2. It doesn't properly deal with logging
    3. You can't set up dependencies between services but that doesn't matter due to point 1

    I recommend using systemd services and/or docker compose instead. systemd services are files that describe which program / script to run and when (like after networking is active or after a certain other service is loaded).

  • source
  • parent