backup server side executed python scripts for managing linux and windows system and application data backups, developed by adminsys for adminsys
Go to file
2020-11-20 14:26:37 +01:00
deb check if link exists before creating it 2017-03-30 11:58:23 +02:00
doc TISBackup documentation , EN version 2020-11-20 14:13:28 +01:00
iniparse Fist commit 2013-05-23 10:19:43 +02:00
lib/huey added support for rpm packaging and basic support for deb 2017-03-29 18:01:35 +02:00
libtisbackup comment DSSKey and add ed25519 2020-11-20 14:13:27 +01:00
rpm minor cleanup 2017-03-29 19:51:17 +02:00
samples changement du path btrfs 2020-11-20 14:13:25 +01:00
scripts added support for rpm packaging and basic support for deb 2017-03-29 18:01:35 +02:00
static Use new based theme on bootstrap 2015-07-03 16:18:48 +02:00
templates Disable automatic boot for copies vm 2015-10-16 17:12:04 +02:00
.gitignore - add backup Samba4 support 2015-12-23 15:27:36 +01:00
config.py Fix bugs with huey 2015-07-08 16:02:14 +02:00
README.md README.md 2020-11-20 10:58:47 +01:00
tasks.py Fix bugs with huey 2015-07-08 16:02:14 +02:00
tisbackup_gui.py forgot that print 2020-11-20 14:11:17 +01:00
tisbackup.py More precise exception handling 2020-11-20 14:11:16 +01:00

TIS-backup Documentation

This is the documentation repository of the TIS-backup project. The documentation is provided under the license CC-BY-SA.

How to contribute?

You must install documentation tools and requirements before doing anything:

sudo sh ./install_requirements.sh

Once installed, pre-commit checks (lint/syntax) are launched prior to committing your changes. To launch tests manually, you can run the following:

pre-commit run --all-files

This should (take a while because sphinx-build) return :

Trim Trailing Whitespace.................................................Passed
Fix End of Files.........................................................Passed
rst ``code`` is two backticks............................................Passed
sphinx build.............................................................Passed

How to push documentation to public ?

Pushing the documentation through a rsync is bad.

To publish WAPT documentation to public, a 'release-' tag must be set using git.

Once a release tag has been set, it creates a tagged build which must be launched manually in Jenkins.

git add *
git commit -m 'I have checked it builds without errors, trust me'
git push
git tag -a release-1.8.1.6694-doc -m "WAPT documentation publish for 1.8.1.6694"
git push origin --tags

Once that tag has been pushed, in Jenkins you have to re-scan the multi-branche project and go to Tags tab, select your tag and build it.

Wait for the entire build to go through, it will publish everything according to JenkinsFile procedure.