-
Notifications
You must be signed in to change notification settings - Fork 258
feat(srv): add doc on how to deploy website MTA-6545 #5596
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
761c8ff
feat(srv): add doc on how to deploy website MTA-6545
SamyOubouaziz 228ed40
feat(srv): update
SamyOubouaziz 6e8c9bb
feat(srv): update
SamyOubouaziz bb1302f
feat(srv): update
SamyOubouaziz f256422
feat(srv): update
SamyOubouaziz 95afd3d
feat(srv): update
SamyOubouaziz 3e98c47
feat(srv): update
SamyOubouaziz 7d36f0c
feat(srv): update
SamyOubouaziz 243d958
feat(srv): update
SamyOubouaziz 7a83e6e
feat(srv): update
SamyOubouaziz 6c746f4
feat(srv): update
SamyOubouaziz 4542f17
feat(srv): update
SamyOubouaziz 1737f34
feat(srv): update
SamyOubouaziz 9c8ffdd
feat(srv): update
SamyOubouaziz 3a81da9
Apply suggestions from code review
SamyOubouaziz c58ddc2
Apply suggestions from code review
SamyOubouaziz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
159 changes: 159 additions & 0 deletions
159
tutorials/hosting-django-webapp-serverless-containers/index.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,159 @@ | ||
| --- | ||
| title: Hosting a Django web app with Serverless Containers | ||
| description: This page provides guidelines on how to host and deploy dynamic Django web applications using Scaleway Serverless Containers | ||
| tags: deploy host website webapp python django containerize application docker dockerfile | ||
| products: | ||
| - containers | ||
| - container-registry | ||
| dates: | ||
| validation: 2025-10-06 | ||
| posted: 2025-10-06 | ||
| validation_frequency: 12 | ||
| difficulty: beginner | ||
| usecase: | ||
| - application-hosting | ||
| - deploy-external-software | ||
| - website-hosting | ||
| ecosystem: | ||
| - third-party | ||
| --- | ||
|
|
||
| import Requirements from '@macros/iam/requirements.mdx' | ||
|
|
||
| [Django](https://www.djangoproject.com/) is a robust Python framework designed for rapid development of secure and maintainable web applications. Hosting Django on [Scaleway Serverless Containers](/serverless-containers/) provides automatic scaling, simplified deployment, and reduced infrastructure management. This deployment method allows your application to efficiently handle varying workloads, while you can optimize resource usage, and focus on writing code and delivering features rather than maintaining servers. | ||
|
|
||
| <Requirements /> | ||
|
|
||
| - A Scaleway account logged into the [console](https://console.scaleway.com) | ||
| - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization | ||
| - Installed [Docker](https://docs.docker.com/get-started/get-docker/) or [Docker Engine](https://docs.docker.com/engine/install/) | ||
| - [Created a Scaleway Container Registry namespace](/container-registry/how-to/create-namespace/) and [logged into it](/container-registry/how-to/connect-docker-cli/) | ||
|
|
||
| ## Create and host a basic Django web application | ||
|
|
||
| To host a [Django](https://www.djangoproject.com/) web application on **Scaleway Serverless Containers**, you need to create a Django project, define your views and URLs, and containerize it using a production-ready `Dockerfile`. The container will run a WSGI server (like Gunicorn) to serve your app. After building the image locally, push it to the [Scaleway Container Registry](/container-registry/) and deploy it via [Scaleway Serverless Containers](/serverless-containers/). | ||
|
|
||
| ### Create your app and test it locally | ||
|
|
||
| 1. In a terminal, create a new directory and navigate into it: | ||
| ```bash | ||
| mkdir my-django-app | ||
| cd my-django-app | ||
| ``` | ||
|
|
||
| 2. Create a virtual environment and install Django: | ||
|
|
||
| <Tabs id="python-venv"> | ||
| <TabsTab label="Linux/macOS"> | ||
| ```bash | ||
| python3 -m venv venv | ||
| source venv/bin/activate | ||
| pip install django gunicorn | ||
| ``` | ||
| </TabsTab> | ||
| <TabsTab label="Windows"> | ||
| ```bash | ||
| python -m venv venv | ||
| venv\Scripts\activate | ||
| pip install django gunicorn | ||
| ``` | ||
| </TabsTab> | ||
| </Tabs> | ||
|
|
||
| 3. Start a new Django project: | ||
| ```bash | ||
| django-admin startproject myproject . | ||
| ``` | ||
|
|
||
| 4. Verify the project structure: | ||
| ``` | ||
| my-django-app/ | ||
| ├── myproject/ | ||
| │ ├── __init__.py | ||
| │ ├── settings.py # Configuration | ||
| │ ├── urls.py # URL routing | ||
| │ └── wsgi.py # WSGI application entry point | ||
| ├── manage.py # CLI for Django commands | ||
| └── venv/ # Virtual environment (excluded from Docker) | ||
| ``` | ||
|
|
||
| 5. Create a `requirements.txt` file and add the following code to it: | ||
| ```txt | ||
| Django==5.1.* | ||
| gunicorn==21.2.* | ||
| ``` | ||
|
|
||
| 6. Run the following command to test the app locally: | ||
| ```bash | ||
| python manage.py runserver | ||
| ``` | ||
| Visit [http://localhost:8000](http://localhost:8000) to see the default Django welcome page. | ||
|
|
||
| ### Build the app image and push it to Scaleway Container Registry | ||
|
|
||
| Before building and pushing your image, ensure you have [created a Scaleway Container Registry namespace](/container-registry/how-to/create-namespace/), and [logged into it with the Docker CLI](/container-registry/how-to/connect-docker-cli/). | ||
|
|
||
| 1. Create a `Dockerfile` at the root of your Django app: | ||
| ```dockerfile | ||
| # Use a lightweight Python image | ||
| FROM python:3.11-slim | ||
|
|
||
| # Set working directory | ||
| WORKDIR /app | ||
|
|
||
| # Install system dependencies | ||
| RUN apt-get update && apt-get install -y --no-install-recommends \ | ||
| && rm -rf /var/lib/apt/lists/* | ||
|
|
||
| # Copy and install Python dependencies | ||
| COPY requirements.txt . | ||
| RUN pip install --no-cache-dir -r requirements.txt | ||
|
|
||
| # Copy the rest of the application | ||
| COPY . . | ||
|
|
||
| # Expose port | ||
| EXPOSE 8000 | ||
|
|
||
| # Run Gunicorn as the entrypoint | ||
| CMD ["gunicorn", "--bind", "0.0.0.0:8000", "myproject.wsgi:application"] | ||
| ``` | ||
|
|
||
| 2. Edit the `settings.py` file of your project with the code below to allow the Scaleway endpoint corresponding to your region, and remove unwanted endpoints: | ||
|
|
||
| ```py | ||
| ALLOWED_HOSTS = [ | ||
| '.fr-par.scw.cloud', | ||
| '.nl-ams.scw.cloud', | ||
| '.pl-waw.scw.cloud' | ||
| ] | ||
| ``` | ||
|
|
||
| 3. Build, tag, and push the image to Scaleway Container Registry: | ||
| ```bash | ||
| docker build \ | ||
| --platform linux/amd64 \ | ||
| --push \ | ||
| -t <CONTAINER_REGISTRY_ENDPOINT>/my-django-app:latest . | ||
| ``` | ||
| <Message type="note"> | ||
| You can find your Container Registry endpoint in the **Overview** tab of your Container Registry namespace in the [Scaleway console](https://console.scaleway.com/registry/namespaces). | ||
| </Message> | ||
|
|
||
| ### Deploy your app using Serverless Containers | ||
|
|
||
| 1. [Deploy a Serverless Container](/serverless-containers/how-to/deploy-container/) with the following settings: | ||
| - **Registry**: Scaleway Container Registry | ||
| - **Registry namespace**: The namespace where you pushed your image | ||
| - **Container port**: `8000` as it is the [port](/serverless-containers/reference-content/port-parameter-variable/) exposed in the dockerfile. | ||
| - **Resources**: `500 mVCPU` and `512 MB` memory | ||
| - **Autoscaling**: Set minimum scale to `1` to avoid [cold starts](/serverless-containers/concepts/#cold-start) (optional) | ||
|
|
||
| Deployment may take up to a minute. | ||
|
|
||
| 2. Once the container is **ready**, click the **container endpoint** in the **Overview** tab. Your Django app will be live and accessible to anyone with the link. | ||
|
|
||
| ## Going further | ||
|
|
||
| - You can deploy an existing Django project by building and pushing its container image as shown above. | ||
| - [Add a custom domain](/serverless-containers/how-to/add-a-custom-domain-to-a-container/) to your deployed app. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.