Set of tools helping in versioning projects
---- ENGLISH ----
PyVersioning
Required
python 2.7
SQLAlchemy
How it works?
This program can create and manage version of databases and file system.
In file example.py you must set:
Engine with path to versioned project, flag to ignore empty folders, list of regular expressions for files to include and exclude
fs_engine = FSVersionerEngine(PROJECT, True, [r'^.*py$'], [r'^.*\\storage\\.*$',])
Database and table, where program keeps data about file system, f.e:
fs_database = SQLDatabase('postgresql://postgres:postgres@localhost/versioning', 'fs_version')
Versioner manager with database, engine and path to file with version information
fs_versioner = FSVersionCommander(fs_database, fs_engine, '.version')
command: python example.py fs list
action: Shows list of file system versions
command: python example.py fs current/actual/latest
action: Shows details about current/actual/latest file system version
command: python example.py fs changed/outdated
action: Checks if file system was changed / is outdated
command: python example.py fs del <name>
action: Deletes file system version with <name> from database
command: python example.py fs set <name>
action: Manually sets file system version [version with name <name> must exist]
command: python example.py fs bump [<level=0>]
action: Creates new file system version, raising number depending on actual and <level> [bump 0: 1.2.3 -> 1.2.4; bump 2: 1.2.3 -> 2.0.0]
command: python example.py fs diff [<name1=None> [<name2=--ACTUAL-->]]
action: Shows changes between versions with names <name1> and <name2>
Database, which we want to versioning and db, where program keeps data about versionised fb, f.e:
db_versioner = DBVersionCommander('postgresql://postgres:postgres@localhost/vers_test3', 'postgresql://postgres:postgres@localhost/vers_control')
command: python example.py db, python example.py db check
action: Check version db.
command: python example.py db create
action: Create new version db, if changes will be detected.
---- POLSKI ----
PyVersioning
Wymagania:
python 2.7
SQLAlchemy
Działanie:
Program pozwala na wersjonowanie schematów baz danych oraz systemu plików.
W pliku example.py należy odpowiednie ścieżki:
Silnik wraz ze ścieżką do versionowanego projektu, flagą ignorującą puste foldery, listę wyrażeń regularnych by zawrzeć/wykluczyć pliki
fs_engine = FSVersionerEngine(PROJECT, True, [r'^.*py$'], [r'^.*\\storage\\.*$',])
Ścieżka do bazy danych oraz nazwa kolumny w której będziemy trzymać dane odnośnie plików, np:
fs_database = SQLDatabase('postgresql://postgres:postgres@localhost/versioning', 'fs_version')
Menedżer wersji z bazą danych, silnikiem i ścieżką do pliku z inforamcją o wersji
fs_versioner = FSVersionCommander(fs_database, fs_engine, '.version')
komenda: python example.py fs list
działanie: wyświetla listę wersji systemu plików
komenda: python example.py fs current/actual/latest
działanie: Wyświetla szczegóły odnośnie bierzącej/aktualnej/najnowszej wersji systemu plików
komenda: python example.py fs changed/outdated
działanie: Sprawdza czy system plików uległ zmianie / jest nieaktualny
komenda: python example.py fs del <name>
działanie: Usuwa wersję systemu plików o nazwie <name> z bazy danych
komenda: python example.py fs set <name>
działanie: Ręcznie ustawia wersję systemu plików [wersja o nazwie <name> musi istnieć w bazie danych]
komenda: python example.py fs bump [<level=0>]
działanie: Tworzy nową wersję systemu plików, podnosząc numer w stosunku do aktualnego w zależności od <level> [bump 0: 1.2.3 -> 1.2.4; bump 2: 1.2.3 -> 2.0.0]
komenda: python example.py fs diff [<name1=None> [<name2=--ACTUAL-->]]
działanie: Pokazuje zmiany między wersjami o nazwach <name1> i <name2>
Pierwsza ścieżka jest bazy którą chcemy wersjonować, druga do bazy w której będziemy trzyamć dane.
db_versioner = DBVersionCommander('postgresql://postgres:postgres@localhost/vers_test3', 'postgresql://postgres:postgres@localhost/vers_control')
komenda: python example.py db, python example.py db check
działanie: sprawdza wersje bazy
komenda: python example.py db create
działanie: tworzy nową wersje bazy jeżeli wykryje zmiany
Metadata
Release files for py_versioning 1.0.0
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 |
|---|---|---|---|---|
| py_versioning-1.0.0.tar.gz | 12.0 kB | Without provenance | Details for py_versioning-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| py_versioning-1.0.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for py_versioning-1.0.0-py2.py3-none-any.whl |
Total release size: 28.4 kB
Release files / py_versioning-1.0.0.tar.gz
| Download URL | py_versioning-1.0.0.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32cf0dfe61cffc3004686ee59aad0c049180d3907e854f860a0b4bbd0d158068
|
|
BLAKE2b-256 checksum How to use checksums |
cd7d10b38f6f45522d4c2af5cbb3ad086eeb803aa2ce66a115fc805f2cdf3892
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / py_versioning-1.0.0-py2.py3-none-any.whl
| Download URL | py_versioning-1.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 16.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
0ac9baed89379ebee11b1ece85b539ae233d3ebddd28f352c3a8e956bb63d75a
|
|
BLAKE2b-256 checksum How to use checksums |
a99ada14187d826c8fa616f3083d21934aad7ed1c5305e10b7ad4a86d083feea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for py_versioning 1.0.0
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.