deploydb
Deploy your database objects automatically when the git branch is updated.
- Production-ready! ⚙️
- Easy-to-use 🔨
- Customizable 🔧
Installation
Install the latest package. pip install deploydb
Usage
1- Create configuration file ( json file or dict )
| Property | Description |
|---|---|
local_path |
where the local repository will be located |
https_url or ssh_url |
address to be listen |
target_branch |
branch to handle changes |
db_creds |
a list of server credentials |
Example: config.json
{
"local_path": "",
"https_url": "",
"ssh_url": "",
"target_branch": "main",
"db_creds": {
"driver": "ODBC Driver 17 for SQL Server",
"server": "server-address-or-instance-name",
"user": "your-username",
"passw": "your-password"
}
}
2- Listener will listen every changes with sync method.
from deploydb import Listener
deploy = Listener('config.json')
deploy.sync(loop=True)
Repo Generator
If you does not have any existing repository. You can easily export your database objects then create your repository.
from deploydb import RepoGenerator
scripter = RepoGenerator(
config="config.json",
export_path="path-to-export",
includes=[], # Default takes all databases from the given credential if not specified.
excludes=[]
)
scripter.run()
RepoGenerator will extract objects structure as below.
.
├── Databases
│ ├── Your-Db-Name
│ │ ├── DDLs
│ │ ├── DMLs
│ │ ├── Functions
│ │ ├── Stored-Procedures
│ │ ├── Tables
│ │ ├── Triggers
│ │ ├── Types
│ │ └── Views
│ └── Database-N
└── README.md
TODO
-
Creating Services for Continuous Integration
- Windows Service
- Linux Systemd Service
-
Getting Notifications
- Microsoft Teams Webhook Integration
- Slack Webhook Integration
Metadata
Release files for deploydb 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| deploydb-0.2.3.tar.gz | 19.1 kB | Without provenance | Details for deploydb-0.2.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| deploydb-0.2.3-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for deploydb-0.2.3-py2.py3-none-any.whl |
Total release size: 32.0 kB
Release files / deploydb-0.2.3.tar.gz
| Download URL | deploydb-0.2.3.tar.gz |
|---|---|
| Size | 19.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fed2a20c8df893724305994ac13a64a0673e89bce2f99ffe4f67e083f929fa2f
|
|
BLAKE2b-256 checksum How to use checksums |
7cfc42cacc5628c0922fb7c538690beb1c9e6d8c07590862c67192c838980f07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.2.0 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.7.9
|
Release files / deploydb-0.2.3-py2.py3-none-any.whl
| Download URL | deploydb-0.2.3-py2.py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
e3cf411316376883973265e982062066aab1d469b0be7e5565cc2b92dbc86ccf
|
|
BLAKE2b-256 checksum How to use checksums |
61bfb6e9efc624b145917f039d46180b3695367a9bcaf78f73f98eaedeb0a36e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.2.0 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.7.9
|
Security for deploydb 0.2.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.