rtbackup 0.1.21

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 212b6a678d4e7dd3153fe755cf6b87a13cbe51a7
+  data.tar.gz: 9f6a0e378d592e3d176cbe43c3c468205c6f678d
+SHA512:
+  metadata.gz: 37b4351eda5c87677080a75d3ad039f09143fb73e61b39ab1ba957edfc5feb45f08742436c411aa3fd9920ba04fb46353edc6faef4054856190b7e06e90dc9c3
+  data.tar.gz: 637e3a49d44b4a5b1485c150b119b5169c9c9abc37553687760eb7b4c34f3e84bfb0edb41b227eab21820def3daace3f562c197754856e554b50f2bf453d8159

data/.gitignore

@@ -0,0 +1,13 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+
+# rspec failure tracking
+.rspec_status
+*.gem
+.vscode/settings.json

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,15 @@
+inherit_from: .rubocop_todo.yml
+
+# inherit_from: .rubocop_todo.yml
+
+Layout/IndentationWidth:
+  Width: 4
+
+Metrics/LineLength:
+  Max: 100
+
+Metrics/MethodLength:
+  Max: 20
+
+Style/Documentation:
+  Enabled: false

data/.rubocop_todo.yml

@@ -0,0 +1,35 @@
+# This configuration was generated by
+# `rubocop --auto-gen-config`
+# on 2018-03-30 15:34:28 +0700 using RuboCop version 0.54.0.
+# The point is for the user to remove these configuration records
+# one by one as the offenses are removed from the code base.
+# Note that changes in the inspected code, or installation of new
+# versions of RuboCop, may require this file to be generated again.
+
+# Offense count: 5
+# Configuration parameters: CountComments, ExcludedMethods.
+Metrics/BlockLength:
+  Max: 69
+
+# Offense count: 1
+# Configuration parameters: CountComments.
+Metrics/ClassLength:
+  Max: 110
+
+# Offense count: 1
+# Configuration parameters: AllowHeredoc, AllowURI, URISchemes, IgnoreCopDirectives, IgnoredPatterns.
+# URISchemes: http, https
+Metrics/LineLength:
+  Max: 102
+
+# Offense count: 1
+# Configuration parameters: CountKeywordArgs.
+Metrics/ParameterLists:
+  Max: 6
+
+# Offense count: 1
+# Configuration parameters: MinNameLength, AllowNamesEndingInNumbers, AllowedNames, ForbiddenNames.
+# AllowedNames: io, id, to
+Naming/UncommunicativeMethodParamName:
+  Exclude:
+    - 'bin/server_backup'

data/.ruby-version

@@ -0,0 +1 @@
+2.3.1

data/.travis.yml

@@ -0,0 +1,5 @@
+sudo: false
+language: ruby
+rvm:
+  - 2.5.0
+before_install: gem install bundler -v 1.16.1

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at tgannon@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,8 @@
+# frozen_string_literal: true
+
+source 'https://rubygems.org'
+
+git_source(:github) { |repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in server_backups.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,89 @@
+PATH
+  remote: .
+  specs:
+    server_backups (0.1.21)
+      activesupport (~> 5.1)
+      aws-sdk-s3 (~> 1.8)
+      main (~> 6.2)
+      slack-notifier (~> 2.3)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activesupport (5.1.5)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (~> 0.7)
+      minitest (~> 5.1)
+      tzinfo (~> 1.1)
+    addressable (2.5.2)
+      public_suffix (>= 2.0.2, < 4.0)
+    arrayfields (4.9.2)
+    aws-partitions (1.73.0)
+    aws-sdk-core (3.17.1)
+      aws-partitions (~> 1.0)
+      aws-sigv4 (~> 1.0)
+      jmespath (~> 1.0)
+    aws-sdk-kms (1.5.0)
+      aws-sdk-core (~> 3)
+      aws-sigv4 (~> 1.0)
+    aws-sdk-s3 (1.8.2)
+      aws-sdk-core (~> 3)
+      aws-sdk-kms (~> 1)
+      aws-sigv4 (~> 1.0)
+    aws-sigv4 (1.0.2)
+    chronic (0.10.2)
+    concurrent-ruby (1.0.5)
+    crack (0.4.3)
+      safe_yaml (~> 1.0.0)
+    diff-lcs (1.3)
+    fattr (2.4.0)
+    hashdiff (0.3.7)
+    i18n (0.9.5)
+      concurrent-ruby (~> 1.0)
+    jmespath (1.3.1)
+    main (6.2.2)
+      arrayfields (~> 4.7, >= 4.7.4)
+      chronic (~> 0.6, >= 0.6.2)
+      fattr (~> 2.2, >= 2.2.0)
+      map (~> 6.1, >= 6.1.0)
+    map (6.6.0)
+    minitest (5.11.3)
+    public_suffix (3.0.2)
+    rake (10.5.0)
+    rspec (3.7.0)
+      rspec-core (~> 3.7.0)
+      rspec-expectations (~> 3.7.0)
+      rspec-mocks (~> 3.7.0)
+    rspec-core (3.7.1)
+      rspec-support (~> 3.7.0)
+    rspec-expectations (3.7.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.7.0)
+    rspec-mocks (3.7.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.7.0)
+    rspec-support (3.7.1)
+    safe_yaml (1.0.4)
+    slack-notifier (2.3.2)
+    thread_safe (0.3.6)
+    tzinfo (1.2.5)
+      thread_safe (~> 0.1)
+    vcr (4.0.0)
+    webmock (3.3.0)
+      addressable (>= 2.3.6)
+      crack (>= 0.3.2)
+      hashdiff
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.16)
+  rake (~> 10.5)
+  rspec (~> 3.0)
+  server_backups!
+  vcr (~> 4.0)
+  webmock (~> 3.3)
+
+BUNDLED WITH
+   1.16.1

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2018 Tyler Gannon
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,174 @@
+# Backup Website and Mysql databases to S3
+
+Automated backup and recovery solution capable of restoring files and databases
+to a given point in time.
+
+* Incremental backups of files using [GNU Tar](https://www.gnu.org/software/tar/)
+* Incremental backups of databases using binary logging
+* Files are stored in a structured manner within an Amazon S3 bucket using
+[AWS S3 SDK gem](https://github.com/aws/aws-sdk-ruby)
+
+**Key assumptions made:**
+
+* All databases except system databases will be backed up.
+* Mysql database only.
+* Mysql binary logging is turned on.
+* The **GNU** (not BSD) version of _tar_.  The GNU version includes --listed-incremental, which is needed for incremental backups.
+
+## Installation
+
+Download the installation package from https://gitlab.com/zigzagau/server_backups/tags
+Find the latest tag and download server_backups-0.x.x.gem from there.
+Copy that file to your server.
+
+### Ubuntu
+
+```bash
+
+sudo apt install ruby ruby-dev zlib1g-dev
+sudo gem install server_backups-0.x.x.gem
+
+```
+
+### Configure Mysql Bin Logging
+
+Add the following to your `my.cnf`, or on Ubuntu you might want to add it to `/etc/mysql/mysql.conf.d/mysqld.conf`
+```
+[mysqld]
+...
+server-id               = 1     # Set it nicely if using replication
+log_bin                 = /var/log/mysql/mysql-bin.log   #  Or your favorite location
+
+```
+
+Then restart mysql:
+
+```
+sudo service mysql restart
+```
+
+### Grant user read access to mysql binary logs and also to your web root
+
+```bash
+# Make sure you know what the group ownership is, for your web root.
+sudo usermod -a -G www-data ubuntu
+sudo usermod -a -G mysql ubuntu
+```
+
+###
+
+## Usage
+
+### Set up a configuration file
+
+Copy `backup_conf.sample.yml` to `~/.backup_conf.yml` and edit the settings.
+Alternatively you can put the file anywhere, and then specify the path to the file
+using the `-c` parameter, or even pipe a config file in through stdin.
+
+The latter option is useful if you'd like to keep passwords and keys in variables,
+rather than saving them to the filesystem.
+
+```bash
+envsubst < back_conf.yml.tmpl | server_backup daily -c -
+```
+
+### Set up your crontab.
+
+* Use `crontab -e` to edit cron configuration.
+
+**Sample Crontab configuration**
+
+```
+
+# Once per month:
+3 0 1 * * /usr/local/bin/server_backup monthly
+# Once per week:
+5 0 * * 0 /usr/local/bin/server_backup weekly
+# Once per day:
+5 0 *  * 1-6 /usr/local/bin/server_backup daily
+# And incremental backups once per hour
+5 1-23 * * * /usr/local/bin/server_backup incremental
+
+```
+
+### Command line parameters
+
+#### 1) For taking backups:
+
+some examples
+
+```bash
+# Take a full backup and store it in the monthly backups location.
+server_backup monthly
+
+# Take a full backup as normal, but instead of backing up all databases,
+# only back up `mydatabase`.
+server_backup daily -d mydatabase
+
+server_backup daily -f  # only back up the files, not the database(s)
+server_backup daily -b  # only back up the database(s), not the files
+
+# Take an incremental backup, but load the given configuration file.
+server_backup incremental -c /etc/my_backup_configuration.cnf
+
+```
+
+#### 2) List (or search) time zones for help with configuration
+
+```bash
+server_backup zones  # list all
+server_backup zones america  # case insensitive search for zones containing a string
+```
+
+#### 3) Restore backups
+
+```bash
+# Restore up to the latest backup data available on s3
+server_backup restore
+
+# Restore up to two days ago at 3pm in the configured
+# time zone (see config file).
+server_backup restore --up_to='two days ago at 3:00 PM'
+
+# To make it easier to decide what time your restore point
+# should be, you can write the restore point time in any time
+# zone and it will be translated to the server's normal time zone.
+#
+# This way, if the server is in UTC and you're in Singapore, you
+# don't necessarily have to do any confusing time maths in order
+# to restore back to what time it was before you made a mistake
+# and updated a wordpress plugin.  ;)
+server_backup restore --up_to='March 28 12:00 PM' --time_zone='Singapore'
+
+```
+
+```
+NAME
+  server_backup
+
+SYNOPSIS
+  server_backup (restore|zones) backup_type [options]+
+
+PARAMETERS
+  backup_type (1 -> symbol(backup_type))
+      specifies the backup type to perform [incremental | daily | weekly |
+      monthly]
+  --config=config, -c (0 ~> config=~/.backup_conf.yml)
+      load configuration from YAML file
+  --database=database, -d (default ~> database=all)
+      Which database to back up, defaults to all non-system databases.
+  --db_only, -b (default ~> false)
+      If specified
+  --files_only=[files_only], -f (de ~> files_only)
+      Only work with files.
+  --help, -h
+```
+
+### Restore your application
+
+```bash
+website_backup restore app_name
+```
+
+
+* Everything in /var/www