feat: overriding BACKUP_NAME and set RESTIC_HOSTNAME
          #274
        
          
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Follow-up to / part of itzg/docker-mc-backup#247
This contains a breaking change: the new
mcbackup.resticHostnamefield is required for users ofmcbackup.backupMethod: restic.I think that it is sensible to require the
mcbackup.resticHostnameinstead of defaulting to e.g.,minecraftServer.worldSaveNameas this could have a side effect in the grouping of the restic snapshots and thus could lead to unexpected deletion of snapshots.