Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/danielrosehill/github-backup-approaches
A list of various approaches to backing up Github accounts, periodically updated
https://github.com/danielrosehill/github-backup-approaches
Last synced: 6 days ago
JSON representation
A list of various approaches to backing up Github accounts, periodically updated
- Host: GitHub
- URL: https://github.com/danielrosehill/github-backup-approaches
- Owner: danielrosehill
- Created: 2024-07-22T19:25:10.000Z (4 months ago)
- Default Branch: main
- Last Pushed: 2024-08-09T15:23:14.000Z (3 months ago)
- Last Synced: 2024-08-09T17:04:55.957Z (3 months ago)
- Size: 5.86 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Github Backup Approaches
What's stopping you from making more liberal use of the amazing features that Github has to offer for open-sourcing projects, discovering and contributing to other codebases, etc?
For me the answer is simple but it might surprise some:
**Backups!**
I have a strong aversion to creating data on the cloud that is not thoroughly backed-up and every time I create a lot of data I think to myself: *"how can I make sure that I retain access to this in all eventualities, including getting locked out of this particular cloud?"*
As a minimum viable standard for backups, I like to follow the tried-and-trusted `3-2-1` rule even if it has since been deprecated in enterprise use in favor of more elaborate systems like `3-2-1-1-0` (and others). But hey: individual developers aren't enterprises and 3-2-1 is good enough for me.
The purpose of this repository is to open-source my thinking and progress in finding robust solutions to Github *account* backup, particularly for those who have scaled to hundreds or thousands of repositories.
Over time I aim to include, at least:
- An overview of backup solutions currently on the market
- A few scripts for DIY Github backups (and links to existing projects, or those which have been attempted)
- Thoughts on how to backup specific data "pools" in a Github account beyond repositories (for example, the list of repositories that users "*star*")
- Ideas and suggestions## Formatting
I enjoy writing in markdown and so many of my repos just consist of `.md` files. This one will probably continue in a similar format although I will add a few scripts as I create them.
## Repository Map
### Commercial Github Backup Solutions
These are listed in a file by that name (more or less) in the main repo.
### Github Github Backup Projects
Backup scripts and utilities for Github authored by third parties and shared on Github (for the most part). These are typically community driven non-commercial open-source projects.
## Author
Daniel Rosehill
(public at danielrosehill dot com)## Licensing
All my GitHub repositories are licensed under [Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/).
### Summary of the License
The Creative Commons Attribution 4.0 International (CC BY 4.0) license allows others to:
- **Share**: Copy and redistribute the material in any medium or format.
- **Adapt**: Remix, transform, and build upon the material for any purpose, even commercially.The licensor cannot revoke these freedoms as long as you follow the license terms.
#### License Terms
- **Attribution**: You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
- **No additional restrictions**: You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.For the full legal code, please visit the [Creative Commons website](https://creativecommons.org/licenses/by/4.0/legalcode).