Project

simple_backup

0.0
Repository is archived
No commit activity in last 3 years
No release in over 3 years
There's a lot of open issues
simple_backuptmaczukin/simple_backupHomepageDocumentationSource CodeBug Tracker
Backup tool with simple DSL for configuration
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
16,281
Stars
1
Forks
0
Watchers
3
 Releases
Current version
0.4.3
Total releases
7
First release
2015-04-15
Latest release
2015-04-23
 Issues
Open Issues
8
Closed Issues
1
Total Issues
9
Issue Closure Rate
11%
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2015-04-20
Reverse Dependencies
0

 Dependencies

Development

rake
~> 10.0

Runtime

colorize
~> 0.7.5
mail
~> 2.6.3
mysql2
~> 0.3.18
 Project Readme

SimpleBackup

Gem Version License MIT

Backup tool with simple DSL definition.

Tool is under heavy development and its API should be treat as unstable.

Why?

I needed an backup tool, that:

  • works on *nix systems,
  • works in command line (I don't need GUI),
  • has a simple declarative configuration mechanism,
  • can store different backups in different places, with optional PGP encryption,
  • is extendable (handling new sources, handling new backends, handling new filters etc.).

I haven't found that kind of backup tool so I decided to write my own. When I started this project I was also in the process of ruby learning and this project seemed to be a good excersise for ruby programming.

Will this project be really usable and unusual? The history will judge :)

Bugs, feedback

If you want to report a bug, please create a GitHub issue.

If you need help, please create a issue or contact me (but I preffer issues). You can find my e-mail on my website, or tweet me.

Contribution

If You want to contribute to the project, please feel free to fork it, create your feature/bug/hotfix branch and create a new pull request. I am using "git-flow"-like workflow to work with this repository:

  1. There are two long-living branches: development and master. Master is always a "production" version. Development should always be in the "production ready" state.
  2. There will be no release branches.
  3. All production versions are tagged and merged from master into development.

If you want to add new feature, please create "feature/..." branch from development. If you want to fix a non-critical bug, please create "bug/..." branch from development. If you want to fix a "must-be-fixed-immediatly" bug, please create "hotfix/..." branch from master.

SimpleBackup is versioned using Semantic Versioning specification. Please follow the specification when contributing - especially when creating a hotfixes (which always should be an a.b.X changes - so the backward compatibility must be preserved).

If you want to help but you don't know what to do - look at TODO list. TODO list was moved to Issues.

License

This is free sofware licensed under MIT license. See LICENSE file.