<p dir="ltr">i need help urgently i bought a domain and now i don't know how to proceed it says to me that i can add 2 dns server in 24 hours let someone explain to me how to proceed </p>
<div class="gmail_quote">8. okt. 2020 11:15 PM je oseba "Valentin V. Bartenev" <<a href="mailto:vbart@nginx.com">vbart@nginx.com</a>> napisala:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I'm glad to announce a new release of NGINX Unit.<br>
<br>
It is yet another big release, featuring ASGI support for Python and a long list<br>
of other improvements and bug fixes.<br>
<br>
ASGI 3.0 is a modern standardized interface that enables writing natively<br>
asynchronous web applications making use of the async/await feature available<br>
inlatest versions of Python. Now, Unit fully supports it along with WSGI.<br>
Even more, Unit automatically detects the interface your Python app is using<br>
(ASGI or WSGI); the configuration experience remains the same, though. Also,<br>
our take on ASGI relies on Unit's native high-perf capabilities to implement<br>
WebSockets.<br>
<br>
To learn more about the new feature, check out the documentation:<br>
<br>
- <a href="https://unit.nginx.org/configuration/#python" rel="noreferrer" target="_blank">https://unit.nginx.org/<wbr>configuration/#python</a><br>
<br>
In addition, we've prepared for you a couple of howtos on configuring popular<br>
ASGI-based frameworks with Unit:<br>
<br>
- Quart: <a href="https://unit.nginx.org/howto/quart/" rel="noreferrer" target="_blank">https://unit.nginx.org/howto/<wbr>quart/</a> (note a simple WebSocket app)<br>
<br>
- Starlette: <a href="https://unit.nginx.org/howto/starlette/" rel="noreferrer" target="_blank">https://unit.nginx.org/howto/<wbr>starlette/</a><br>
<br>
Finally, we've updated the Django howto to include the ASGI alternative:<br>
<br>
- <a href="https://unit.nginx.org/howto/django/" rel="noreferrer" target="_blank">https://unit.nginx.org/howto/<wbr>django/</a><br>
<br>
<br>
Changes with Unit 1.20.0 08 Oct 2020<br>
<br>
*) Change: the PHP module is now initialized before chrooting; this<br>
enables loading all extensions from the host system.<br>
<br>
*) Change: AVIF and APNG image formats added to the default MIME type<br>
list.<br>
<br>
*) Change: functional tests migrated to the pytest framework.<br>
<br>
*) Feature: the Python module now fully supports applications that use<br>
the ASGI 3.0 server interface.<br>
<br>
*) Feature: the Python module now has a built-in WebSocket server<br>
implementation for applications, compatible with the HTTP & WebSocket<br>
ASGI Message Format 2.1 specification.<br>
<br>
*) Feature: automatic mounting of an isolated "/tmp" file system into<br>
chrooted application environments.<br>
<br>
*) Feature: the $host variable contains a normalized "Host" request<br>
value.<br>
<br>
*) Feature: the "callable" option sets Python application callable<br>
names.<br>
<br>
*) Feature: compatibility with PHP 8 RC 1. Thanks to Remi Collet.<br>
<br>
*) Feature: the "automount" option in the "isolation" object allows to<br>
turn off the automatic mounting of language module dependencies.<br>
<br>
*) Bugfix: "pass"-ing requests to upstreams from a route was broken; the<br>
bug had appeared in 1.19.0. Thanks to 洪志道 (Hong Zhi Dao) for<br>
discovering and fixing it.<br>
<br>
*) Bugfix: the router process could crash during reconfiguration.<br>
<br>
*) Bugfix: a memory leak occurring in the router process; the bug had<br>
appeared in 1.18.0.<br>
<br>
*) Bugfix: the "!" (non-empty) pattern was matched incorrectly; the bug<br>
had appeared in 1.19.0.<br>
<br>
*) Bugfix: fixed building on platforms without sendfile() support,<br>
notably NetBSD; the bug had appeared in 1.16.0.<br>
<br>
<br>
I would very much like to highlight one of these changes. Perhaps the least<br>
noticeable, it is still important for the entire project: our functional tests<br>
moved to a more feature-rich pytest framework from the native Python unittest<br>
module that we've used previously. This change should enable us to write more<br>
sophisticated tests, boosting the overall quality of our future releases.<br>
<br>
All in all, this is a genuinely solid release, but I'm still more excited<br>
about the things yet to come. Yes, even more great features are coming our<br>
way very shortly! Right now, we are tinkering with route matching patterns<br>
to support regular expressions; working on keepalive connection caching;<br>
adding multithreading to application modules; and finally, fabricating the<br>
metrics API!<br>
<br>
We encourage you to follow our roadmap on GitHub, where your ideas and requests<br>
are always more than welcome:<br>
<br>
- <a href="https://github.com/orgs/nginx/projects/1" rel="noreferrer" target="_blank">https://github.com/orgs/nginx/<wbr>projects/1</a><br>
<br>
Stay tuned!<br>
<br>
wbr, Valentin V. Bartenev<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
unit mailing list<br>
<a href="mailto:unit@nginx.org">unit@nginx.org</a><br>
<a href="https://mailman.nginx.org/mailman/listinfo/unit" rel="noreferrer" target="_blank">https://mailman.nginx.org/<wbr>mailman/listinfo/unit</a></blockquote></div>