summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCoprDistGit <infra@openeuler.org>2023-06-20 05:00:22 +0000
committerCoprDistGit <infra@openeuler.org>2023-06-20 05:00:22 +0000
commit81e8b5f26639fe1491733edd10ed145b24171d42 (patch)
treef5c86c7311cd7c13f49de012017a937be3bf9931
parentedacf2945eb60f9dc910349496302ced28d82562 (diff)
automatic import of python-django-queue-manageropeneuler20.03
-rw-r--r--.gitignore1
-rw-r--r--python-django-queue-manager.spec105
-rw-r--r--sources1
3 files changed, 107 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore
index e69de29..833ba79 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/django-queue-manager-1.3.9.tar.gz
diff --git a/python-django-queue-manager.spec b/python-django-queue-manager.spec
new file mode 100644
index 0000000..355886f
--- /dev/null
+++ b/python-django-queue-manager.spec
@@ -0,0 +1,105 @@
+%global _empty_manifest_terminate_build 0
+Name: python-django-queue-manager
+Version: 1.3.9
+Release: 1
+Summary: A simple app that provides a Message Queue System using a socket as broker, this app, make you able to manage an ordered queue of tasks (with calling a simple queuing function form API).Simple to setup, easy to manage and scalable, the queue can be remotized to another server,you can use multiple istance of the application, and easly manage multiple broker and relatives queues.This app, will integrate into your DB backend and serves three table with the states of the queue.
+License: GNU GPLv3
+URL: http://www.fardellasimone.com/
+Source0: https://mirrors.aliyun.com/pypi/web/packages/23/d8/3c348ec051976d3855c6f0efad84c0a31ce681fea5e8e06ff0613d91e292/django-queue-manager-1.3.9.tar.gz
+BuildArch: noarch
+
+
+%description
+The same ``django_queue_manager`` app can run from another server, and provide a
+seprate server queue for the async tasks.
+Here is a simple way to do it:
+1. The queue server should be similar to the main django server, just
+ without a webserver.
+2. Deploy your django code to these two remotes: the main with the
+ web-server, and the queue server
+3. Open firewalls ports between the main django server, and the queue
+ server, and between the main django database and the queue server host
+4. On the django main server, change the host and port details directly from the admin site.
+That's it!
+For any support/issue request, contact the author: fardella.simone@gmail.com
+
+%package -n python3-django-queue-manager
+Summary: A simple app that provides a Message Queue System using a socket as broker, this app, make you able to manage an ordered queue of tasks (with calling a simple queuing function form API).Simple to setup, easy to manage and scalable, the queue can be remotized to another server,you can use multiple istance of the application, and easly manage multiple broker and relatives queues.This app, will integrate into your DB backend and serves three table with the states of the queue.
+Provides: python-django-queue-manager
+BuildRequires: python3-devel
+BuildRequires: python3-setuptools
+BuildRequires: python3-pip
+%description -n python3-django-queue-manager
+The same ``django_queue_manager`` app can run from another server, and provide a
+seprate server queue for the async tasks.
+Here is a simple way to do it:
+1. The queue server should be similar to the main django server, just
+ without a webserver.
+2. Deploy your django code to these two remotes: the main with the
+ web-server, and the queue server
+3. Open firewalls ports between the main django server, and the queue
+ server, and between the main django database and the queue server host
+4. On the django main server, change the host and port details directly from the admin site.
+That's it!
+For any support/issue request, contact the author: fardella.simone@gmail.com
+
+%package help
+Summary: Development documents and examples for django-queue-manager
+Provides: python3-django-queue-manager-doc
+%description help
+The same ``django_queue_manager`` app can run from another server, and provide a
+seprate server queue for the async tasks.
+Here is a simple way to do it:
+1. The queue server should be similar to the main django server, just
+ without a webserver.
+2. Deploy your django code to these two remotes: the main with the
+ web-server, and the queue server
+3. Open firewalls ports between the main django server, and the queue
+ server, and between the main django database and the queue server host
+4. On the django main server, change the host and port details directly from the admin site.
+That's it!
+For any support/issue request, contact the author: fardella.simone@gmail.com
+
+%prep
+%autosetup -n django-queue-manager-1.3.9
+
+%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-queue-manager -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 1.3.9-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..235a564
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+f3d3d513c08e5a15171f060c8b1fa116 django-queue-manager-1.3.9.tar.gz