Django Deploy
Django Deploy is an experimental tool designed to make it easier to deploy new and existing Django applications on public clouds (e.g. Kubernetes Engine).
Currently, Django Deploy can only
- Deploy to Google App Engine.
- Deploy to Kubernetes Engine.
- Deploy applications created using its own template code.
Django Deploy is an experimental project not officially supported by Google.
Here is an example usage:
$ django-cloud-deploy new 11 steps to setup your new project [1/11] In order to deploy your application, you must allow Django Deploy to access your Google account. Press [Enter] to open a browser window to allow access [2/11] Enter a Google Cloud Platform Project ID, or leave blank to use [django-799931]: my-cool-site [3/11] Enter a Google Cloud Platform project name, or leave blank to use [Django Project]: My Cool Site [4/11] In order to deploy your application, you must enable billing for your Google Cloud Project. You have the following existing billing accounts: 1. My Billing Account Please enter your numeric choice or press [Enter] to create a new billing account: 1 [5/11] Enter a password for the default database user "postgres" Password: Password (again): [6/11] Enter a new directory path to store project source, or leave blank to use [/usr/local/google/home/bquinlan/my-cool-site]: [7/11] Enter a Django project name, or leave blank to use [mysite]: mycoolsite [8/11] Enter a Django app name, or leave blank to use [home]: mycoolapp [9/11] Enter a name for the Django superuser, or leave blank to use [admin]: myname [10/11] Enter a password for the Django superuser "myname" Password: Password (again): [11/11] Enter a e-mail address for the Django superuser, or leave blank to use [test@example.com]: myname@example.com
Getting Started
For the fastest path to a working Django application running in the cloud, see the Quickstart.
Deploy an existing application
For detailed instructions on how to deploy an existing Django project, see the HOWTO.
Building a new application
For detailed instructions on how to create a new Django project and then deploy and update it, see the HOWTO.
Development Workflow (Linux)
Verify that Python 3.5 or later is installed:
python3 -V
Clone the project and cd to it's directory:
git clone https://github.com/GoogleCloudPlatform/django-cloud-deploy
cd django-cloud-deploy
Create a new virtual environment:
virtualenv -p python3 venv
source venv/bin/activate
Install Django Deploy in edit mode:
pip install -e .
Run it:
django-cloud-deploy new
Code modifications will be reflected in the next run of django-cloud-deploy.
Contribute
Check out our CONTRIBUTING to find out how you can help.
License
This project is licensed under the Apache License - see the LICENSE file for details
This is not an officially supported Google product.
Status
Django Deploy is an experimental project not officially supported by Google.
Metadata
Release files for django-cloud-deploy 0.3.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-cloud-deploy-0.3.4.tar.gz | 100.1 kB | Without provenance | Details for django-cloud-deploy-0.3.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_cloud_deploy-0.3.4-py3-none-any.whl | Python 3 | none | any | Details for django_cloud_deploy-0.3.4-py3-none-any.whl |
Total release size: 274.5 kB
Release files / django-cloud-deploy-0.3.4.tar.gz
| Download URL | django-cloud-deploy-0.3.4.tar.gz |
|---|---|
| Size | 100.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ca3199324a1654a275231ac87df9b31c17bd69d46d20090fd46cd032ee3aebfb
|
|
BLAKE2b-256 checksum How to use checksums |
a74a2f99737348a6833c1dbaf05624182bc5905dfaba7173deffe79c598ad6f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.0
|
Release files / django_cloud_deploy-0.3.4-py3-none-any.whl
| Download URL | django_cloud_deploy-0.3.4-py3-none-any.whl |
|---|---|
| Size | 174.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
628d071124a52e8178a5c50c6427e62dbfa0dff2d4e137d2a2e009bd1111a91b
|
|
BLAKE2b-256 checksum How to use checksums |
197ac7b0138c1457a5598d17bef9fb46a56e8559d91e316a6ae5e3a64c6fdc46
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.0
|
Security for django-cloud-deploy 0.3.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.