Skip to content

Use Queue system instead of locking for updates and such #2

@Nixellion

Description

@Nixellion

Use just 1 script:

  • Perform checks
  • Perform actions that are in the queue

Script

Run as cron every 10 minutes.

Check script should run through all required checks:

  • Check game updates
  • Check mod updates
  • ...?

It runs as a cron, and if any actions are required it creates a queue.yaml file in the end with names of functions corresponding to required actions. It also adds a datetime when update should happen and notifies everyone that update will happen about an hour from now. If queue.yaml already exists it looks if there's anything not checked in there and checks for those things.

For example if there's already a game update queued it should only keep checking for mod updates. So in case some mod gets updated by the time the restart happens it can have a chance to queue that too.

After checking it should check if .now is >= scheduled date. If not - send update notification.

If yes - send 5 minute warning and then "Game restarts in 10 seconds, ready or not, here I come!" only in-game.

Then:

  • Stop server
  • Run queued actions
  • Delete queue file
  • Start server
  • Wait a few minutes
  • Send notification that server should be back up and running

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions