4.3.0 (#558)

Author: Archmonger

.github/workflows/release.yml

@@ -42,9 +42,6 @@ jobs:
 
 # Until we are transfered out of Jazzband, the workaround is releasing manually via personal PyPI accounts.
 # The following steps are required to release a new version of the package:
-# python -m pip install -U pip
-# python -m pip install -U -r requirements/build.txt
-# python -m pip install -U -r requirements.txt
-# python -m build --sdist --wheel --outdir dist .
-# twine check dist/*
+# python -m pip install -U pip && pip install -U -r requirements/build.txt && pip install -U -r requirements.txt
+# python -m build --sdist --wheel --outdir dist . && twine check dist/*
 # twine upload dist/*

README.rst

@@ -26,6 +26,7 @@ It is made to:
 - Deal easily with remote archiving
 - Keep your development database up to date
 - Use Crontab or Celery to setup automated backups
+- Manually backup and restore via Django management commands
 
 Docs
 ====
@@ -42,160 +43,6 @@ restore mechanisms, apply compression and/or encryption and use the storage syst
 It gives a simple interface to backup and restore your database or media
 files.
 
-Management Commands
-===================
-
-dbbackup
---------
-
-Backup your database to the specified storage. By default this will backup all
-databases specified in your settings.py file and will not delete any old
-backups. You can optionally specify a server name to be included in the backup
-filename.
-
-::
-
-  Usage: ./manage.py dbbackup [options]
-  
-  Options:
-    --noinput             Tells Django to NOT prompt the user for input of any
-                          kind.
-    -q, --quiet           Tells Django to NOT output other text than errors.
-    -c, --clean           Clean up old backup files
-    -d DATABASE, --database=DATABASE
-                          Database to backup (default: everything)
-    -s SERVERNAME, --servername=SERVERNAME
-                          Specify server name to include in backup filename
-    -z, --compress        Compress the backup files
-    -e, --encrypt         Encrypt the backup files
-    -o OUTPUT_FILENAME, --output-filename=OUTPUT_FILENAME
-                          Specify filename on storage
-    -O OUTPUT_PATH, --output-path=OUTPUT_PATH
-                          Specify where to store on local filesystem
-    -x EXCLUDE_TABLES, --exclude-tables=EXCLUDE_TABLES
-                          Exclude tables data from backup (-x 'public.table1, public.table2')
-
-dbrestore
----------
-
-Restore your database from the specified storage. By default this will lookup
-the latest backup and restore from that. You may optionally specify a
-servername if you you want to backup a database image that was created from a
-different server. You may also specify an explicit local file to backup from.
-
-::
-
-  Usage: ./manage.py dbrestore [options]
-  
-  Options:
-    --noinput             Tells Django to NOT prompt the user for input of any
-                          kind.
-    -d DATABASE, --database=DATABASE
-                          Database to restore
-    -i INPUT_FILENAME, --input-filename=INPUT_FILENAME
-                          Specify filename to backup from
-    -I INPUT_PATH, --input-path=INPUT_PATH
-                          Specify path on local filesystem to backup from
-    -s SERVERNAME, --servername=SERVERNAME
-                          Use a different servername backup
-    -c, --decrypt         Decrypt data before restoring
-    -p PASSPHRASE, --passphrase=PASSPHRASE
-                          Passphrase for decrypt file
-    -z, --uncompress      Uncompress gzip data before restoring
-    -n SCHEMA, --schema SCHEMA
-                        Specify schema(s) to restore. Can be used multiple times.
-    -r, --no-drop         Don't clean (drop) the database. This only works with mongodb and postgresql.
-    --pg-options PG_OPTIONS
-                        Additional pg_restore options, e.g. '--if-exists --no-owner'. Use quotes.
-
-mediabackup
------------
-
-Backup media files by get them one by one, include in a TAR file. ::
-
-  Usage: ./manage.py mediabackup [options]
-  
-  Options:
-    --noinput             Tells Django to NOT prompt the user for input of any
-                          kind.
-    -q, --quiet           Tells Django to NOT output other text than errors.
-    -c, --clean           Clean up old backup files
-    -s SERVERNAME, --servername=SERVERNAME
-                          Specify server name to include in backup filename
-    -z, --compress        Compress the archive
-    -e, --encrypt         Encrypt the backup files
-    -o OUTPUT_FILENAME, --output-filename=OUTPUT_FILENAME
-                          Specify filename on storage
-    -O OUTPUT_PATH, --output-path=OUTPUT_PATH
-                          Specify where to store on local filesystem
-
-mediarestore
-------------
-
-Restore media files from storage backup to your media storage. ::
-
-  Usage: ./manage.py mediarestore [options]
-  
-  Options:
-    --noinput             Tells Django to NOT prompt the user for input of any
-                          kind.
-    -q, --quiet           Tells Django to NOT output other text than errors.
-    -i INPUT_FILENAME, --input-filename=INPUT_FILENAME
-                          Specify filename to backup from
-    -I INPUT_PATH, --input-path=INPUT_PATH
-                          Specify path on local filesystem to backup from
-    -e, --decrypt         Decrypt data before restoring
-    -p PASSPHRASE, --passphrase=PASSPHRASE
-                          Passphrase for decrypt file
-    -z, --uncompress      Uncompress gzip data before restoring
-    -r, --replace         Replace existing files
-
-Tests
-=====
-
-Tests are stored in `dbbackup.tests` and to run them you must launch:
-
-::
-
-    python runtests.py
-
-In fact, ``runtests.py`` acts as a ``manage.py`` file and all Django commands
-are available. So you could launch:
-
-::
-
-    python runtests.py shell
-
-to get a Python shell configured with the test project. Also all test
-command options are available and usable to run only a selection of tests.
-See `Django test command documentation`_ for more information about it.
-
-.. _`Django test command documentation`: https://docs.djangoproject.com/en/stable/topics/testing/overview/#running-tests
-
-There are even functional tests: ::
-
-    ./functional.sh
-
-See documentation for details.
-
-To run the tests across all supported versions of Django and Python, you
-can use Tox. Firstly install Tox:
-
-::
-
-    pip install tox
-
-To run the tests just use the command ``tox`` in the command line.  If you
-want to run the tests against just one specific test environment you can run
-``tox -e <testenv>``.  For example, to run the tests with Python3.9 and
-Django3.2 you would run:
-
-::
-
-    tox -e py39-django32
-
-The available test environments can be found in ``tox.ini``.
-
 Contributing
 ============
 

dbbackup/VERSION

@@ -1 +1 @@
-4.2.1
+4.3.0

docs/changelog.rst

@@ -4,6 +4,11 @@ Changelog
 Unreleased
 ----------
 
+* Nothing (yet)!
+
+4.3.0 (2025-05-09)
+----------
+
 * Add generic `--pg-options` to pass custom options to postgres.
 * Add option `--if-exists` for pg_dump command
 * Empty string as HOST for postgres unix domain socket connection is now supported.

setup.py

@@ -43,10 +43,11 @@ def get_test_requirements():
         "amazon",
         "s3",
         "dropbox",
+        "sqlite",
     ],
     packages=find_packages(),
     classifiers=[
-        "Development Status :: 4 - Beta",
+        "Development Status :: 5 - Production/Stable",
         "Environment :: Web Environment",
         "Environment :: Console",
         "Framework :: Django :: 3.2",