per page, with , order by , clip by
Results of 1 - 10 of about 195 for How to (0.004 sec.)
how (195), to (957)
Contributing code — Django 6.1 ドキュメント 16648
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Contributing code ¶ So you'd like to write some code, documentation or tests to improve Django? There are several ways you can help Django's develop ... ment. Tutorials ¶ The Django tutorial contains a whole section that walks you step-by-step through the contributing code process. Dja ... ngoにはじめて貢献する How-to ガイド ¶ If you already have some familiarity with the processes and principles, our documentation also contains useful ... guidance on specific topics: How to submit a patch to Django for new and/or fixed behavior How to write and run tests How to run Django's unit tes ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/
Contributing code — Django 6.1 ドキュメント 16549
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Contributing code ¶ So you'd like to write some code, documentation or tests to improve Django? There are several ways you can help Django's develop ... ment. Tutorials ¶ The Django tutorial contains a whole section that walks you step-by-step through the contributing code process. Dja ... ngoにはじめて貢献する How-to ガイド ¶ If you already have some familiarity with the processes and principles, our documentation also contains useful ... guidance on specific topics: How to submit a patch to Django for new and/or fixed behavior How to write and run tests How to run Django's unit tes ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/
How to use Django with Granian — Django 6.1 ドキュメント 14291
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » How to use Django with Granian ¶ Granian is a Rust-based high-performance HTTP server for Python applications, supporting ASGI and WSGI interfaces. ... Django in Granian ¶ When Granian is installed, a granian command is available which runs WSGI applications. Granian needs to be called with the location of a module containing a WSGI application object named application , using the --interface wsg ... ypical Django project, invoking Granian would look like: granian myproject.wsgi:application --interface wsgi This will start one process listening on 127.0.0.1:8000 . It requires that your project be on the Python path; to ensure that, run this com ... mand from the same directory as your manage.py file. For more advanced usage, please read the Granian documentation . 目次 How to use Django with Granian Installing Granian Running Django in Granian 前のトピックへ WSGI とともにデプロイするには 次のト ...
https://man.mtool.work/django/6.1/howto/deployment/wsgi/granian.html
How to use Django with Granian — Django 6.1 ドキュメント 14279
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » How to use Django with Granian ¶ Granian is a Rust-based high-performance HTTP server for Python applications, supporting ASGI and WSGI interfaces. ... Django in Granian ¶ When Granian is installed, a granian command is available which runs ASGI applications. Granian needs to be called with the location of a module containing an ASGI application object, followed by what the application is called ... ypical Django project, invoking Granian would look like: granian myproject.asgi:application --interface asgi This will start one process listening on 127.0.0.1:8000 . It requires that your project be on the Python path; to ensure that, run this com ... mand from the same directory as your manage.py file. For more advanced usage, please read the Granian documentation . 目次 How to use Django with Granian Installing Granian Running Django in Granian 前のトピックへ Django を Daphne とともに使う 次のト ...
https://man.mtool.work/django/6.1/howto/deployment/asgi/granian.html
How to use Django's Content Security Policy — Django 6.1 ドキュメント 11937
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » How to use Django's Content Security Policy ¶ Basic config ¶ Content Security Policy (CSP) を有効にするには、Django プロジェクトで次のように設定しま ... す: Add the CSP middleware to your MIDDLEWARE setting: MIDDLEWARE = [ # ... "django.middleware.csp.ContentSecurityPolicyMiddleware" , # ... ] Configure ... h). The CSP Settings docs provide more details about the differences between these two: from django.utils.csp import CSP # To enforce a CSP policy: SECURE_CSP = { "default-src" : [ CSP . SELF ], # Add more directives to be enforced. } # Or for repo ... ache. See the reference documentation on Nonce usage for implementation details and important caching considerations. 目次 How to use Django's Content Security Policy Basic config Nonce config 前のトピックへ REMOTE_USER で認証する 次のトピックへ Dja ...
https://man.mtool.work/django/6.1/howto/csp.html
Django's Tasks framework — Django 6.1 ドキュメント 11277
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django's Tasks framework ¶ New in Django 6.0: For older Django versions, the django-tasks backport is available. For a web application, there's ofte ... n more than just turning HTTP requests into HTTP responses. For some functionality, it may be beneficial to run code outside the request-response cycle. That's where ... background Tasks come in. Background Tasks can offload work to be run outside the request-response cycle, to be run elsewhere, potentially at a later date. This keeps requests fast, red ... Store. These workers run outside the request-response lifecycle. Configuring a Task backend ¶ The Task backend determines how and where Tasks are stored for execution and how they are executed. Different Task backends have different characteristics ...
https://man.mtool.work/django/6.1/topics/tasks.html
Working with Git and GitHub — Django 6.1 ドキュメント 11203
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Working with Git and GitHub ¶ This section explains how the community can contribute code to Django via pull requests. If you're interested in how m ... ergers handle them, see プルリクエストの取り扱い . Below, we are going to show how to create a GitHub pull request containing the changes for Trac ticket #xxxxx. By creating a fully-ready pull req ... uest, you will make the reviewer's job easier, meaning that your work is more likely to be merged into Django. You could also upload a traditional patch to Trac, but it's less practical for reviews. Git のインス ... tance: "all tests pass under SQLite and MySQL". Pull requests at GitHub have only two states: open and closed. The merger who will deal with your pull request has only two options: merge it or close it. For this reason, it isn't useful to make a pul ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
Djangoソースコードレポジトリ — Django 6.1 ドキュメント 11127
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Djangoソースコードレポジトリ ¶ Djangoアプリケーションを本番環境にデプロイするときは、 公式パッケージのDjangoリリース をほぼ常に使いたくなるでしょう。 ... ントはコードレポジトリの構成とそこでの作業方法と調査方法について説明しています。 大局的な概要 ¶ The Django source code repository uses Git to track changes to the code over time, so you'll need a copy of the Git client (a program called git ) on your ... computer, and you'll want to familiarize yourself with the basics of how Git works. Git's website offers downloads for various operating systems. The s ... re and move over to the documentation for contributing to Django , which covers things like the preferred coding style and how to generate and submit a patch. Stable branches ¶ Django uses branches to prepare for releases of Django. Each major relea ...
https://man.mtool.work/django/6.1/internals/git.html
Django 1.7 リリースノート — Django 6.1 ドキュメント 10987
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.7 リリースノート ¶ September 2, 2014 Django 1.7 へようこそ! このリリースノートでは、 バージョン 1.7 の新機能 と、Django 1.6 以前からアップグ ... 3.4. We highly recommend and only officially support the latest release of each series. The Django 1.6 series is the last to support Python 2.6. Django 1.7 is the first release to support Python 3.4. This change should affect only a small number o ... f Django users, as most operating-system vendors today are shipping Python 2.7 or newer as their default version. If you're still using Python 2.6, ... however, you'll need to stick to Django 1.6 until you can upgrade your Python version. Per our support policy , Django 1.6 wil ...
https://man.mtool.work/django/6.1/releases/1.7.html
Django 1.7 リリースノート — Django 6.1 ドキュメント 10987
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.7 リリースノート ¶ September 2, 2014 Django 1.7 へようこそ! このリリースノートでは、 バージョン 1.7 の新機能 と、Django 1.6 以前からアップグ ... 3.4. We highly recommend and only officially support the latest release of each series. The Django 1.6 series is the last to support Python 2.6. Django 1.7 is the first release to support Python 3.4. This change should affect only a small number o ... f Django users, as most operating-system vendors today are shipping Python 2.7 or newer as their default version. If you're still using Python 2.6, ... however, you'll need to stick to Django 1.6 until you can upgrade your Python version. Per our support policy , Django 1.6 wil ...
https://man.mtool.work/django/6.1/releases/1.7.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT