tencent cloud

Serverless Cloud Function

Release Notes and Announcements
Release Notes
Announcements
User Guide
Product Introduction
Overview
Related Concepts
How It Works
Strengths
Scenarios
Related Products
Purchase Guide
Billing Overview
Billing Mode
Billable Items and Billing Modes
Function Computing Power Support
Free Tier
SCF Pricing
Billing Example
Payment Overdue
Getting Started
Creating Event Function in Console
User Guide
Quota Management
Managing Functions
Web Function Management
Log Management
Concurrence Management
Trigger Management
Function URL
A Custom Domain Name
Version Management
Alias Management
Permission Management
Running Instance Management
Plugin Management
Managing Monitors and Alarms
Network Configuration
Layer Management
Execution Configuration
Extended Storage Management
DNS Caching Configuration
Resource Managed Mode Management
Near-Offline Resource Hosting Model
Workflow
Triggers
Trigger Overview
Trigger Event Message Structure Summary
API Gateway Trigger
COS Trigger
CLS Trigger
Timer Trigger
CKafka Trigger
Apache Kafka Trigger
MQTT Trigger
Trigger Configuration Description
MPS Trigger
CLB Trigger Description
TencentCloud API Trigger
Development Guide
Basic Concepts
Testing a Function
Environment Variables
Dependency Installation
Using Container Image
Error Types and Retry Policies
Dead Letter Queue
Connecting SCF to Database
Automated Deployment
Cloud Function Status Code
Common Errors and Solutions
Developer Tools
Serverless Web IDE
Calling SDK Across Functions
Third-Party Tools
Code Development
Python
Node.js
Golang
PHP
Java
Custom Runtime
Deploying Image as Function
Web Framework Development
Deploying Framework on Command Line
Quickly Deploying Egg Framework
Quickly Deploying Express Framework
Quickly Deploying Flask Framework
Quickly Deploying Koa Framework
Quickly Deploying Laravel Framework
Quickly Deploying Nest.js Framework
Quickly Deploying Next.js Framework
Quickly Deploying Nuxt.js Framework
Quickly Deploying Django Framework
Use Cases
Overview
Solutions with Tencent Cloud Services
Business Development
TRTC Practices
COS Practices
CKafka Practice
CLS
CLB Practice
MPS
CDN
CDWPG
VOD
SMS
ES
Scheduled Task
Video Processing
Success Stories
Tencent Online Education
Online Video Industry
Tencent Online Education
Best Practice of Tencent IEG Going Global
API Documentation
History
Introduction
API Category
Making API Requests
Other APIs
Namespace APIs
Layer Management APIs
Async Event Management APIs
Trigger APIs
Function APIs
Function and Layer Status Description
Data Types
Error Codes
SDK Documentation
FAQs
General
Web Function
Billing FAQs
Network FAQs
Log FAQs
SCF utility class
Event Handling FAQs
API Gateway Trigger FAQs
Related Agreement
Service Level Agreement
Contact Us
Glossary

Quickly Deploying Django Framework

PDF
Focus Mode
Font Size
Last updated: 2025-10-28 14:40:04

Overview

This document describes how to quickly deploy a local Django project to the cloud through an HTTP-triggered function.

Prerequisites

Before using SCF, you need to sign up for a Tencent Cloud account and complete identity verification first.

Directions

Template deployment: Quick deployment of Django project

1. Log in to the SCF console and click Functions on the left sidebar.
2. Select the region and namespace where to create a function at the top of the page and click Create to enter the function creation process.
3. Select Template, enter Django in the search box, select the Django template, and click Next as shown below:


4. On the Create page, you can view and modify the specific configuration information of the template project.
5. Click Complete. After creating the HTTP-triggered function, you can view its basic information on the Function management page.
6. Click Trigger management on the left to view the access path and access your deployed Django project as shown below:


7. Click the access path URL to access the Django project as shown below:



Custom deployment: Quick migration of local project to cloud

Local development

1. Run the following command to confirm that Django has been installed in your local environment.
python -m pip install Django
2. Create the Hello World sample project locally.
django-admin startproject helloworld && cd helloworld
The directory structure is as follows:
$ tree
. manage.py Manager
|--***
| |-- __init__.py Package
| |-- settings.py Settings file
| |-- urls.py Route
| `-- wsgi.py Deployment
3. Run the python manage.py runserver command locally to start the bootstrap file. Below is the sample code:
$ python manage.py runserver
July 27, 2021 - 11:52:20
Django version 3.2.5, using settings 'helloworld.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.

4. Visit http://127.0.0.1:8000 in a browser, and you can access the sample Django project locally as shown below:



Deployment in cloud

Next, perform the following steps to make simple modifications to the locally created project, so that it can be quickly deployed through an HTTP-triggered function. The steps of project transformation for Django are as follows:
1. Install dependencies
1.1 As the Django dependency library is not provided in the standard cloud environment of SCF, you must install the dependencies and upload them together with the project code. Create the requirements.txt file first with the following content:
Django==3.1.3
1.2 Run the following command to install:
pip install -r requirements.txt -t .
Note:
As the initialized default project imports the db.sqlite3 library, install this dependency synchronously or configure comments for the DATABASES field in the setting.py file of the project.
2. Add the scf_bootstrap bootstrap file The listening port in the HTTP-triggered function must be 9000, so you need to change the listening address and port in the following way: create the scf_bootstrap bootstrap file in the project root directory and add the following content to it (which is used to configure environment variables, specify service bootstrap commands, and make sure that your service can be started normally through this file):
#!/bin/bash
/var/lang/python3/bin/python3 manage.py runserver 9000
3. After the creation is completed, you need to run the following command to modify the executable permission of the file. By default, the permission 777 or 755 is required for it to start normally. Below is the sample code:
chmod 777 scf_bootstrap
Note:
In the SCF environment, only files in the /tmp directory are readable/writable. We recommend you select /tmp when outputting files. If you select other directories, write will fail due to the lack of permissions.
If you want to output environment variables in the log, you need to add the -u parameter before the startup command, such as python -u app.py.
4. After the local configuration is completed, run the following command to start the service (with execution in the scf_bootstrap directory as an example) and make sure that your service can be normally started locally.
Note:
Be sure to change the python path to the local path during local testing.
./scf_bootstrap
5. Log in to the SCF console and click Functions on the left sidebar.
6. Select the region where to create a function at the top of the page and click Create to enter the function creation process.
7. Select Create from scratch and configure the options as prompted:
Function type: Select HTTP-triggered function.
Function name: Enter the name of your function.
Region: Enter your function deployment region, such as Chengdu.
Runtime environment: Select Python 3.6.
Submitting method: Select Local folder and upload your local project.
Function codes: Select the specific local folder where the function code is.
8. Click Complete.

Development management

After the deployment is completed, you can quickly access and test your web service in the SCF console and try out various features of SCF, such as layer binding and log management. In this way, you can enjoy the advantages of low cost and flexible scaling brought by the serverless architecture as shown below:



Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback