Extensions

Extend SAMMI's functionality with our community made extensions.

Auto Deck Backup

Developed by:
Rating | Utilities | views

Overview

Auto Deck Backup is an extension that allows you to automatically backup your decks to local and cloud (Github) storage. You can set the interval for backups and choose the storage location.

Features

  • Backup Decks Locally
  • Backup Decks to Github (optional)
  • Set Backup Interval
  • Automatically delete old backups (local only)
  • Cloud backup comes with encryption
  • Premade deck with all available commands and explanations

Important Note

  • The extension may not properly work on non Windows devices.
  • The developer is not responsible for any data loss or corruption due to the use of this extension, nor for any issues with the cloud storage provider.

Special thanks goes to:
My amazing Patrons.
Thank you so much!

If you would like to support me developing SAMMI itself and my extensions, you can join my Patreon, which will give you access to all my upcoming creations for completely free and priority help on any of my extensions.

DISCLAIMER: The extension is provided as is. The developer has no obligation to provide maintenance and support services or handle any bug reports.
Feel free to edit the extension for your own use. You may not distribute, sell or publish it without the author’s permission.


Additional Information
Version 1.0 Requires SAMMI 2024.2.0^ Stream Platform Any Updated May 24, 2024
Setup
  1. Install the extension. You can follow the Extension Install Guide.
  2. Configure the extension inside the Settings button in the premade deck that comes with the extension:
    1. Local Backups
      • Enable Local Backups - Check this option to enable local backups.
      • Backup Folder Path - Specify the full folder path where the backup files will be saved. - By default, it’s in your SAMMI/ext/Auto Deck Backup folder.
      • Backp Freq. - Set how often to back up your files, in minutes.
      • Auto Remove Old Backups - Choose whether to automatically delete old backup files
      • Max. Backup Days - Set the maximum number of days to keep backup files (if Auto Remove Old Backups is enabled.)
    2. Cloud Backups
      • Enable Local Backups - Check this option to enable cloud backups.
      • Backp Freq. - Set how often to back up your files, in minutes.
      • Github Username - Your GitHub username, which will be used to back up your decks
      • Github Repo - Name of the GitHub repository where you want to back up your decks.
      • Github Branch - Name of the GitHub branch where you want to back up your decks. - The default is main when you create a new repository.
      • Github token - your fine grained GitHub token with write access to this backup repository.
      • Encryption password - Set a password to encrypt your deck data with AES 256. - The more complex the password, the more secure the files will be. - WARNING: If you forget your password, you will NOT be able to restore your files, and I will not be able to help you.

      Please don’t forget to regularly manually clear your backup repository of old backup files.

    3. Click on Save and Ok to save the button, and reload your Bridge.
      Your decks data should now be automatically backed up depending on the settings you’ve chosen.
      Please double check the backups are getting created. If you encounter any issues, please try using paths that do NOT contain any special or non English characters.
      The extension will automatically load when you connect to Bridge.

How to setup your Github account and repository for backups

  1. First, create a new GitHub account if you don’t have one yet.
  2. Navigate to GitHub, click on the + sign dropdown, and select New Repository.
    image
    image
  3. Set the name for your new repository, and make it Private. Click on Create Repository.
    image
    image
  4. Click on your profile icon and go to Settings. Click on Developer settings in the left bar all the way down.
    image
    image
  5. Click on Personal access tokens and then Fine-grained tokens. Click on Generate new token:
    image
    image
  6. Adjust the settings as follows:
    • Name your new token and set its expiration date (you’ll need to refresh it in SAMMI when it expires).
    • Under Repository Access, choose Only select repositories and select the backup repository you created in step 2.
      image
      image
    • Under Permissions - Repository permissions, select Contents - Read and write.
      image
      image
    • Click on Generate token.
      image
      image
    • Save the generated token somewhere safe, and input it in the GitHub Token box inside the Settings button in your premade deck.
      image
      image

How to restore your decks from a backup

Local Backups

  1. Manually back up your current decks_data.json file found in SAMMI/json/decks_data.json. You can locate this file by pressing Open Current Decks Data Folder button in the premade deck.
  2. Navigate to the backup folder by pressing Open Local Backup Folder button
  3. Find and rename the backup file you wish to restore to decks_data.json.
  4. Move this renamed file to SAMMI/json folder, replacing the existing decks_data.json file.
    WARNING: This will overwrite your current decks data.
  5. Reopen SAMMI.

Cloud Backups

  1. Manually back up your current decks_data.json file found in SAMMI/json/decks_data.json. You can locate this folder by pressing Open Current Decks Data Folder button in the premade deck.
  2. Navigate to the repository by pressing“Open Backup Repository button.
  3. Download the file you wish to restore.
  4. Use “Decrypt Cloud Backup File” button to decrypt this file.
  5. Rename the decrypted backup file to decks_data.json.
  6. Move this renamed file to SAMMI/json folder, replacing the existing decks_data.json file.
    WARNING: This will overwrite your current decks data.
  7. Reopen SAMMI.
Privacy Policy
This developer has disclosed that it will not collect or use your data.

This developer declares that your data is:

  • Not being sold to third parties.
  • Not being used or transferred for purposes that are unrelated to the extension's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Reviews

Coming soon!