%global _empty_manifest_terminate_build 0 Name: python-django-check-migration-wtf Version: 1.4.0 Release: 1 Summary: A line of description License: GLP3 URL: https://github.com/antonioIrizar/django-check-migration-wtf Source0: https://mirrors.nju.edu.cn/pypi/web/packages/d2/34/75e2524631482d4b2e1ef0851e787636b9eb170d0e817e87ab3dfdb990ee/django-check-migration-wtf-1.4.0.tar.gz BuildArch: noarch Requires: python3-Django Requires: python3-PyGithub %description # django-check-migration-wtf ## Description **django-check-migration-wtf** is an extension for Django to check migrations and notify you if their are secure to do on environments with zero downtime. In some situations Django Migration system generate migrations to need do a downtime because they are blocking operation or you write custom migration than can block you database. Actually this extension only works for backends of PostgresSQL and Postgis, versions support 11, 12, 13 and 14. **Advise**: this extension notify you for common blocking operations on database. Anyway you should review your migrations and understand their. ## Configuration It is really simple ### Installation Install the package with the typical tool (pip): `pip install django-check-migration-wtf` ### Add to your project Add app on your settings: ```python INSTALLED_APPS = [ 'django_check_migration_wtf', ..., ] ``` ### Add some optional vars Add some optional setup on your settings: * `CHECK_MIGRATION_WTF_PSQL_VERSION` It is to know your PostgresSQL Version by default it is 9 * The next following vars are for use github integration: * `CHECK_MIGRATION_WTF_GITHUB_TOKEN` Token to can use API of github, It only need permission of reading of repo. * `CHECK_MIGRATION_WTF_REPO_NAME` Name of repository on Github ## Usage It is really easy to use. It is execute by a typical django command like `makemigrations` or `migrate`... It has two mode of usage. ### Local First execute your `makemigrations` and you can do your custome modifications. Then **before** execute command `migrate` execute the following command: `python manage.py check_migration` It will search all migrations that are not apply to the system (like `showmigrations`) and it will analyze if they are secure to do. You can have two possibilities: * When the migration or migrations are **secure**, you get the following response: ![image info](./images/migration-ok.png) * When the migration or migrations are **not secure**, you get the following response: ![image info](./images/migration-bad.png) ### Github This is reality an option of command to execute it on your continues integration. It will search you migrations comparing the base branch and your current branch and the analyze it `python manage.py check_migration --github ` ## Limitations * This extension not analyze code inside of `RunPython` * Github option to work correctly suppose your migrations are inside of directory **migrations** %package -n python3-django-check-migration-wtf Summary: A line of description Provides: python-django-check-migration-wtf BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-django-check-migration-wtf # django-check-migration-wtf ## Description **django-check-migration-wtf** is an extension for Django to check migrations and notify you if their are secure to do on environments with zero downtime. In some situations Django Migration system generate migrations to need do a downtime because they are blocking operation or you write custom migration than can block you database. Actually this extension only works for backends of PostgresSQL and Postgis, versions support 11, 12, 13 and 14. **Advise**: this extension notify you for common blocking operations on database. Anyway you should review your migrations and understand their. ## Configuration It is really simple ### Installation Install the package with the typical tool (pip): `pip install django-check-migration-wtf` ### Add to your project Add app on your settings: ```python INSTALLED_APPS = [ 'django_check_migration_wtf', ..., ] ``` ### Add some optional vars Add some optional setup on your settings: * `CHECK_MIGRATION_WTF_PSQL_VERSION` It is to know your PostgresSQL Version by default it is 9 * The next following vars are for use github integration: * `CHECK_MIGRATION_WTF_GITHUB_TOKEN` Token to can use API of github, It only need permission of reading of repo. * `CHECK_MIGRATION_WTF_REPO_NAME` Name of repository on Github ## Usage It is really easy to use. It is execute by a typical django command like `makemigrations` or `migrate`... It has two mode of usage. ### Local First execute your `makemigrations` and you can do your custome modifications. Then **before** execute command `migrate` execute the following command: `python manage.py check_migration` It will search all migrations that are not apply to the system (like `showmigrations`) and it will analyze if they are secure to do. You can have two possibilities: * When the migration or migrations are **secure**, you get the following response: ![image info](./images/migration-ok.png) * When the migration or migrations are **not secure**, you get the following response: ![image info](./images/migration-bad.png) ### Github This is reality an option of command to execute it on your continues integration. It will search you migrations comparing the base branch and your current branch and the analyze it `python manage.py check_migration --github ` ## Limitations * This extension not analyze code inside of `RunPython` * Github option to work correctly suppose your migrations are inside of directory **migrations** %package help Summary: Development documents and examples for django-check-migration-wtf Provides: python3-django-check-migration-wtf-doc %description help # django-check-migration-wtf ## Description **django-check-migration-wtf** is an extension for Django to check migrations and notify you if their are secure to do on environments with zero downtime. In some situations Django Migration system generate migrations to need do a downtime because they are blocking operation or you write custom migration than can block you database. Actually this extension only works for backends of PostgresSQL and Postgis, versions support 11, 12, 13 and 14. **Advise**: this extension notify you for common blocking operations on database. Anyway you should review your migrations and understand their. ## Configuration It is really simple ### Installation Install the package with the typical tool (pip): `pip install django-check-migration-wtf` ### Add to your project Add app on your settings: ```python INSTALLED_APPS = [ 'django_check_migration_wtf', ..., ] ``` ### Add some optional vars Add some optional setup on your settings: * `CHECK_MIGRATION_WTF_PSQL_VERSION` It is to know your PostgresSQL Version by default it is 9 * The next following vars are for use github integration: * `CHECK_MIGRATION_WTF_GITHUB_TOKEN` Token to can use API of github, It only need permission of reading of repo. * `CHECK_MIGRATION_WTF_REPO_NAME` Name of repository on Github ## Usage It is really easy to use. It is execute by a typical django command like `makemigrations` or `migrate`... It has two mode of usage. ### Local First execute your `makemigrations` and you can do your custome modifications. Then **before** execute command `migrate` execute the following command: `python manage.py check_migration` It will search all migrations that are not apply to the system (like `showmigrations`) and it will analyze if they are secure to do. You can have two possibilities: * When the migration or migrations are **secure**, you get the following response: ![image info](./images/migration-ok.png) * When the migration or migrations are **not secure**, you get the following response: ![image info](./images/migration-bad.png) ### Github This is reality an option of command to execute it on your continues integration. It will search you migrations comparing the base branch and your current branch and the analyze it `python manage.py check_migration --github ` ## Limitations * This extension not analyze code inside of `RunPython` * Github option to work correctly suppose your migrations are inside of directory **migrations** %prep %autosetup -n django-check-migration-wtf-1.4.0 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-django-check-migration-wtf -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Fri May 05 2023 Python_Bot - 1.4.0-1 - Package Spec generated