1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
|
%global _empty_manifest_terminate_build 0
Name: python-django-hurricane
Version: 1.3.4
Release: 1
Summary: Hurricane is an initiative to fit Django perfectly with Kubernetes.
License: MIT License
URL: https://github.com/Blueshoe/django-hurricane
Source0: https://mirrors.aliyun.com/pypi/web/packages/44/20/4a2c1b04825bd90b7b74ff528a0e121451c9c35bba76db15caaf1a2d8bbb/django-hurricane-1.3.4.tar.gz
BuildArch: noarch
Requires: python3-tornado
Requires: python3-Django
Requires: python3-asgiref
Requires: python3-pika
Requires: python3-requests
Requires: python3-debugpy
Requires: python3-pydevd-pycharm
%description
<br />
<br />
<!-- PROJECT LOGO -->
<br />
<div align="center">
<h3 align="center">Hurricane</h3>
<p align="center">
An initiative to fit Django perfectly with Kubernetes. It is supposed to cover many capabilities in order to run
Django in a cloud-native environment, including a Tornado-powered Django app server.
<br />
<a href="https://django-hurricane.readthedocs.io/en/latest/"><strong>Explore the docs »</strong></a>
<br />
<br />
<a href="https://django-hurricane.io/">Hurricane website</a>
·
<a href="https://django-hurricane.readthedocs.io/en/latest/usage.html">User's guide</a>
·
<a href="https://django-hurricane.io/basic-app/">Guide to the first Hurricane-based Application</a>
</p>
</div>
## Intro
Django was developed with the *batteries included*-approach and already handles most of the challenges around
web development with grace. It was initially developed at a time when web applications got deployed and run on a server
(physical or virtual). With its *pragmatic design* it enabled many developers to keep up with changing requirements,
performance and maintenance work.
However, service architectures have become quite popular for complex applications in the past few years. They provide
a modular style based on the philosophy of dividing overwhelming software projects into smaller and more controllable
parts. The advantage of highly specialized applications gained prominence among developers, but introduces new
challenges to the IT-operation.
However, with the advent of Kubernetes and the cloud-native development philosophy a couple of new possibilities emerged
to run those service-based applications even better. Kubernetes is a wonderful answer for just as many IT-operation
requirements as Django is for web development. The inherent monolithic design of Django can be tempting to roll out
recurring operation patterns with each application. It's not about getting Django to run in a
Kubernetes cluster (you may already solved this), it's about integrating Django as tightly as possible with Kubernetes
in order to harness the full power of that platform. Creating the most robust, scalable and secure applications
with Django by leveraging the existing expertise of our favorite framework is the main goal of this initiative.
Hurricane is supposed to make the most out of the existing Django ecosystem without reinventing the wheel.
We will collect best-practices and opinions about how to run Django in Kubernetes and put them on Hurricane's roadmap.
### Application Server
Why another app server instead of *uwsgi*, *gunicorn* or *mod_wsgi*? We need a cloud-native app server which is
much more tidily coupled to the Django application itself. Think of special url routes for Kubernetes probes! Building a
special View in each and every Django application is not an appropriate solution. What about the Kubernetes Metrics API?
That's all something we **don't** want to take care of in our Django code.
Those traditional app servers (i.e. uwsgi et.al.) have a highly optimized process model for bare-server deployments with
many CPUs, multiple threads and so on. In Kubernetes the scaling of an application is done through the Replication-value
in a workload description manifest. This is no longer something we configure with app server parameters.
## Installation
Hurricane can be installed from a Python Package Index:
```bash
pip3 install hurricane
```
Add *"hurricane"* to your *INSTALLED_APPS*:
```python
INSTALLED_APPS += (
'hurricane',
)
```
You can start the Hurricane server with a following command:
```python
python manage.py serve --autoreload --static
```
Ouput of this command looks as following:
```
System check identified some issues:
2022-05-04 02:19:07,521 INFO hurricane.server.general Tornado-powered Django web server
2022-05-04 02:19:07,521 INFO hurricane.server.general Starting probe application running on port 8001 with route liveness-probe: /alive, readiness-probe: /ready, startup-probe: /startup
2022-05-04 02:19:07,523 INFO hurricane.server.general Starting HTTP Server on port 8000
2022-05-04 02:19:07,524 INFO hurricane.server.general Startup time is 0.0026285648345947266 seconds
```
There are many options that can be used in a combination with the serve command. Please refer to the [documentation](https://django-hurricane.readthedocs.io/en/latest/usage.html) to learn more about the options.
Django-hurricane works best in combination with Kubernetes, as it includes the inbuilt health-probes, i.e. liveness, readiness and startup probes. Additionally, it is possible to implement custom checks. These checks will be executed after the standard django checks. Follow our guide to learn [how to write a custom check](https://django-hurricane.io/custom-checks/).
## Commercial Support
Hurricane is developed and maintained by [Blueshoe](https://www.blueshoe.de).
If you need any help implementing with hurricane or you want to tell us about the use-case, how you use hurricane, please contact us: hurricane@blueshoe.de.
%package -n python3-django-hurricane
Summary: Hurricane is an initiative to fit Django perfectly with Kubernetes.
Provides: python-django-hurricane
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-django-hurricane
<br />
<br />
<!-- PROJECT LOGO -->
<br />
<div align="center">
<h3 align="center">Hurricane</h3>
<p align="center">
An initiative to fit Django perfectly with Kubernetes. It is supposed to cover many capabilities in order to run
Django in a cloud-native environment, including a Tornado-powered Django app server.
<br />
<a href="https://django-hurricane.readthedocs.io/en/latest/"><strong>Explore the docs »</strong></a>
<br />
<br />
<a href="https://django-hurricane.io/">Hurricane website</a>
·
<a href="https://django-hurricane.readthedocs.io/en/latest/usage.html">User's guide</a>
·
<a href="https://django-hurricane.io/basic-app/">Guide to the first Hurricane-based Application</a>
</p>
</div>
## Intro
Django was developed with the *batteries included*-approach and already handles most of the challenges around
web development with grace. It was initially developed at a time when web applications got deployed and run on a server
(physical or virtual). With its *pragmatic design* it enabled many developers to keep up with changing requirements,
performance and maintenance work.
However, service architectures have become quite popular for complex applications in the past few years. They provide
a modular style based on the philosophy of dividing overwhelming software projects into smaller and more controllable
parts. The advantage of highly specialized applications gained prominence among developers, but introduces new
challenges to the IT-operation.
However, with the advent of Kubernetes and the cloud-native development philosophy a couple of new possibilities emerged
to run those service-based applications even better. Kubernetes is a wonderful answer for just as many IT-operation
requirements as Django is for web development. The inherent monolithic design of Django can be tempting to roll out
recurring operation patterns with each application. It's not about getting Django to run in a
Kubernetes cluster (you may already solved this), it's about integrating Django as tightly as possible with Kubernetes
in order to harness the full power of that platform. Creating the most robust, scalable and secure applications
with Django by leveraging the existing expertise of our favorite framework is the main goal of this initiative.
Hurricane is supposed to make the most out of the existing Django ecosystem without reinventing the wheel.
We will collect best-practices and opinions about how to run Django in Kubernetes and put them on Hurricane's roadmap.
### Application Server
Why another app server instead of *uwsgi*, *gunicorn* or *mod_wsgi*? We need a cloud-native app server which is
much more tidily coupled to the Django application itself. Think of special url routes for Kubernetes probes! Building a
special View in each and every Django application is not an appropriate solution. What about the Kubernetes Metrics API?
That's all something we **don't** want to take care of in our Django code.
Those traditional app servers (i.e. uwsgi et.al.) have a highly optimized process model for bare-server deployments with
many CPUs, multiple threads and so on. In Kubernetes the scaling of an application is done through the Replication-value
in a workload description manifest. This is no longer something we configure with app server parameters.
## Installation
Hurricane can be installed from a Python Package Index:
```bash
pip3 install hurricane
```
Add *"hurricane"* to your *INSTALLED_APPS*:
```python
INSTALLED_APPS += (
'hurricane',
)
```
You can start the Hurricane server with a following command:
```python
python manage.py serve --autoreload --static
```
Ouput of this command looks as following:
```
System check identified some issues:
2022-05-04 02:19:07,521 INFO hurricane.server.general Tornado-powered Django web server
2022-05-04 02:19:07,521 INFO hurricane.server.general Starting probe application running on port 8001 with route liveness-probe: /alive, readiness-probe: /ready, startup-probe: /startup
2022-05-04 02:19:07,523 INFO hurricane.server.general Starting HTTP Server on port 8000
2022-05-04 02:19:07,524 INFO hurricane.server.general Startup time is 0.0026285648345947266 seconds
```
There are many options that can be used in a combination with the serve command. Please refer to the [documentation](https://django-hurricane.readthedocs.io/en/latest/usage.html) to learn more about the options.
Django-hurricane works best in combination with Kubernetes, as it includes the inbuilt health-probes, i.e. liveness, readiness and startup probes. Additionally, it is possible to implement custom checks. These checks will be executed after the standard django checks. Follow our guide to learn [how to write a custom check](https://django-hurricane.io/custom-checks/).
## Commercial Support
Hurricane is developed and maintained by [Blueshoe](https://www.blueshoe.de).
If you need any help implementing with hurricane or you want to tell us about the use-case, how you use hurricane, please contact us: hurricane@blueshoe.de.
%package help
Summary: Development documents and examples for django-hurricane
Provides: python3-django-hurricane-doc
%description help
<br />
<br />
<!-- PROJECT LOGO -->
<br />
<div align="center">
<h3 align="center">Hurricane</h3>
<p align="center">
An initiative to fit Django perfectly with Kubernetes. It is supposed to cover many capabilities in order to run
Django in a cloud-native environment, including a Tornado-powered Django app server.
<br />
<a href="https://django-hurricane.readthedocs.io/en/latest/"><strong>Explore the docs »</strong></a>
<br />
<br />
<a href="https://django-hurricane.io/">Hurricane website</a>
·
<a href="https://django-hurricane.readthedocs.io/en/latest/usage.html">User's guide</a>
·
<a href="https://django-hurricane.io/basic-app/">Guide to the first Hurricane-based Application</a>
</p>
</div>
## Intro
Django was developed with the *batteries included*-approach and already handles most of the challenges around
web development with grace. It was initially developed at a time when web applications got deployed and run on a server
(physical or virtual). With its *pragmatic design* it enabled many developers to keep up with changing requirements,
performance and maintenance work.
However, service architectures have become quite popular for complex applications in the past few years. They provide
a modular style based on the philosophy of dividing overwhelming software projects into smaller and more controllable
parts. The advantage of highly specialized applications gained prominence among developers, but introduces new
challenges to the IT-operation.
However, with the advent of Kubernetes and the cloud-native development philosophy a couple of new possibilities emerged
to run those service-based applications even better. Kubernetes is a wonderful answer for just as many IT-operation
requirements as Django is for web development. The inherent monolithic design of Django can be tempting to roll out
recurring operation patterns with each application. It's not about getting Django to run in a
Kubernetes cluster (you may already solved this), it's about integrating Django as tightly as possible with Kubernetes
in order to harness the full power of that platform. Creating the most robust, scalable and secure applications
with Django by leveraging the existing expertise of our favorite framework is the main goal of this initiative.
Hurricane is supposed to make the most out of the existing Django ecosystem without reinventing the wheel.
We will collect best-practices and opinions about how to run Django in Kubernetes and put them on Hurricane's roadmap.
### Application Server
Why another app server instead of *uwsgi*, *gunicorn* or *mod_wsgi*? We need a cloud-native app server which is
much more tidily coupled to the Django application itself. Think of special url routes for Kubernetes probes! Building a
special View in each and every Django application is not an appropriate solution. What about the Kubernetes Metrics API?
That's all something we **don't** want to take care of in our Django code.
Those traditional app servers (i.e. uwsgi et.al.) have a highly optimized process model for bare-server deployments with
many CPUs, multiple threads and so on. In Kubernetes the scaling of an application is done through the Replication-value
in a workload description manifest. This is no longer something we configure with app server parameters.
## Installation
Hurricane can be installed from a Python Package Index:
```bash
pip3 install hurricane
```
Add *"hurricane"* to your *INSTALLED_APPS*:
```python
INSTALLED_APPS += (
'hurricane',
)
```
You can start the Hurricane server with a following command:
```python
python manage.py serve --autoreload --static
```
Ouput of this command looks as following:
```
System check identified some issues:
2022-05-04 02:19:07,521 INFO hurricane.server.general Tornado-powered Django web server
2022-05-04 02:19:07,521 INFO hurricane.server.general Starting probe application running on port 8001 with route liveness-probe: /alive, readiness-probe: /ready, startup-probe: /startup
2022-05-04 02:19:07,523 INFO hurricane.server.general Starting HTTP Server on port 8000
2022-05-04 02:19:07,524 INFO hurricane.server.general Startup time is 0.0026285648345947266 seconds
```
There are many options that can be used in a combination with the serve command. Please refer to the [documentation](https://django-hurricane.readthedocs.io/en/latest/usage.html) to learn more about the options.
Django-hurricane works best in combination with Kubernetes, as it includes the inbuilt health-probes, i.e. liveness, readiness and startup probes. Additionally, it is possible to implement custom checks. These checks will be executed after the standard django checks. Follow our guide to learn [how to write a custom check](https://django-hurricane.io/custom-checks/).
## Commercial Support
Hurricane is developed and maintained by [Blueshoe](https://www.blueshoe.de).
If you need any help implementing with hurricane or you want to tell us about the use-case, how you use hurricane, please contact us: hurricane@blueshoe.de.
%prep
%autosetup -n django-hurricane-1.3.4
%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-hurricane -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.4-1
- Package Spec generated
|
