snapshot_archive 0.3.0 → 0.6.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 39922e21c1be277d98cd3286c0e5af704208c4699f8131d37691c9f9e1c789ab
-  data.tar.gz: 90d276037f30a35799d9e868f7ef391187d4ef1864ccec3dbb8d51a9108690c6
+  metadata.gz: ce054d819d2904bc09ce9745be4e7183e82865180c8dad43377618b5a2b9dc3f
+  data.tar.gz: b302b75328f3a33a50de9a7490177418030b599bf9cccaaacf55592a99406443
 SHA512:
-  metadata.gz: 1a2bf6c53eb910b5f2b2843104018db8e248cda32035fd6a5658b17c1fde22bd32de5d506e8b1cfa5308e4ceb56c4dbe66136a51e3e251b75155ebff1460f377
-  data.tar.gz: 70a956f0b31dbb41e30e72bc4bccb54fc0c6684e075637256a98306a34c54bbabe53f96c99a5041193522a80295baffea8d756c2331d1396df6c5be1e4ca3176
+  metadata.gz: 676aa9b24a464fc46ebaad107e5a7517a5243cf947e5d5ef49e4a941931b652339a6a0253e1097b62f1e103e441971538c0267e7300def7f11d5a53881c2fd08
+  data.tar.gz: d5f5c0094fb81ea474c40c951bedb4e965fe537ff35fadbd3329cd1f5232a2dc8570ea8faf82eef946e16b7c8f918f142087ba88949248bed063c9a90e4dea72

data/.ruby-version

@@ -1 +1 @@
-2.7.5
+3.2.3

data/CODE_OF_CONDUCT.md

@@ -1,84 +1 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at pete.kinnecom@appfolio.com. All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
-available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
+Be excellent to each other

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    snapshot_archive (0.3.0)
+    snapshot_archive (0.5.0)
       commander (~> 4.5)
 
 GEM

data/README.md

@@ -6,6 +6,9 @@ snapshot and restore it later! Build your own snapshotting behavior in a
 configuration file so that you can snapshot any stateful service you use during
 development.
 
+By default will make mysql backups for any development databases for the rails 
+app in your CWD.
+
 ## Installation
 
 ```

data/lib/snapshot_archive/archives.rb

@@ -35,7 +35,7 @@ module SnapshotArchive
       end
 
       def call
-        metadata.fetch("stores").each do |store_metadata|
+        metadata.fetch("stores").reverse.each do |store_metadata|
           store = Cfg.instance.store(store_metadata.fetch("type"))
           store.restore(store_metadata)
         end

data/lib/snapshot_archive/cfg.rb

@@ -44,6 +44,7 @@ module SnapshotArchive
         :pwd,
         :repository,
         :shell,
+        :store,
         :stores,
       ].each do |meth|
         define_method(meth) do |*args|

data/lib/snapshot_archive/formatters.rb

@@ -42,6 +42,9 @@ module SnapshotArchive
           path: #{dir}
           ----------------------
           #{message}
+
+          Full metadata:
+          #{JSON.pretty_generate(metadata.dig("archive", "stores"))}
         TXT
       end
     end

data/lib/snapshot_archive/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module SnapshotArchive
-  VERSION = "0.3.0"
+  VERSION = "0.6.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: snapshot_archive
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 0.6.0
 platform: ruby
 authors:
 - Pete Kinnecom
-autorequire: 
+autorequire:
 bindir: exe
 cert_chain: []
-date: 2022-04-19 00:00:00.000000000 Z
+date: 2024-03-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: commander
@@ -24,7 +24,7 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '4.5'
-description: 
+description:
 email:
 - git@k7u7.com
 executables:
@@ -54,7 +54,6 @@ files:
 - lib/snapshot_archive/shell.rb
 - lib/snapshot_archive/stores.rb
 - lib/snapshot_archive/version.rb
-- lib/template.txt
 - script/install
 - snapshot_archive.gemspec
 homepage: https://github.com/petekinnecom/snapshot_archive
@@ -64,7 +63,7 @@ metadata:
   allowed_push_host: https://rubygems.org
   homepage_uri: https://github.com/petekinnecom/snapshot_archive
   source_code_uri: https://github.com/petekinnecom/snapshot_archive
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -79,8 +78,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.3.4
-signing_key: 
+rubygems_version: 3.4.19
+signing_key:
 specification_version: 4
 summary: Save and restore snapshots of stateful services to a central archive. The
   default action is to backup all databases for the current rails apps, however, custom

data/lib/template.txt

@@ -1,5 +0,0 @@
-
-
-# Follows same rules as a git commit message. First line is summary, followed by
-# more detailed info. Set `export EDITOR="..."` to use a different editor for
-# this message. (eg. `export EDITOR="code --wait"` to use VSCode)