Genez-io · andreia-oca · Feb 10, 2025 · Jan 21, 2025 · Jan 22, 2025 · Jan 22, 2025
diff --git a/docs/frameworks/django.md b/docs/frameworks/django.md
@@ -266,6 +266,7 @@ This file will contain the configuration needed to deploy your backend using Gen
 3. You might need to replace the `entry` field with the name of your wsgi application file.
 4. You might need to replace the `path` field with the path relative at **genezio.yaml** file.
 5. This example configuration works if **genezio.yaml** is in the same directory as your `manage.py` file and the Django app is named `project_name`.
+6. The `runtime` field is the Python runtime to use for your Django app, currently, the supported runtimes are: [python3.9.x, python3.10.x, python3.11.x, python3.12.x, python3.13.x]
    :::
 
 ```yaml title="genezio.yaml"
@@ -284,6 +285,8 @@ backend:
     name: python
     # The package manager used by the backend.
     packageManager: pip
+    # The runtime to use for your Django app.
+    runtime: python3.13.x
   # Information about the backend's functions.
   functions:
     # The name (label) of the function.
@@ -336,6 +339,7 @@ Open a web browser and navigate to [http://localhost:8000](http://localhost:8000
 
 Finally, deploy your project. A browser window will open, and you will be prompted to log in to your Genezio account and
 authorize the CLI to make the deployment.
+
 Run the following command in your terminal:
 
 ```bash
@@ -355,6 +359,14 @@ After that, you can deploy your project without the `--env` flag.
 For more information about environment variables, you can check
 the [official documentation](/docs/project-structure/backend-environment-variables.md).
 
+:::note
+During the deployment process, Genezio automatically installs all dependencies specified in your `requirements.txt` file using:
+- The correct architecture (Linux x86)
+- The Python runtime specified in `genezio.yaml`
+
+This process ensures compatibility with our serverless infrastructure, defaulting to the latest Python 3.13.x version.
+:::
+
 ## See your app in Genezio Dashboard
 
 After deploying your application, you can test it to ensure it's running correctly. To verify that your Django app is

diff --git a/docs/frameworks/ember.md b/docs/frameworks/ember.md
@@ -0,0 +1,151 @@
+---
+description: Learn how to deploy an Ember application with Genezio.
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+# Ember
+
+<head>
+    <title>Ember | Genezio Documentation</title>
+</head>
+
+[Ember.js](https://emberjs.com/) is a productive, battle-tested JavaScript framework for building modern web applications. It includes everything you need to build rich user interfaces that work on any device.
+
+:::tip
+Get started in no time with the [Ember template](https://app.genez.io/start/deploy?repository=https://github.com/Genez-io/ember-getting-started).
+:::
+
+# Deployment
+
+Learn how to deploy an existing Ember app using Genezio, a serverless deployment platform that simplifies app management and reduces costs.
+
+## Prerequisites
+
+### 1. Install genezio
+
+Use your preferred package manager to install Genezio:
+
+<Tabs>
+  <TabItem className="tab-item" value="npm" label="npm">
+<div id="step1-install-npm">
+  ```
+  npm install genezio -g
+  ```
+  </div>
+  </TabItem>
+  <TabItem className="tab-item" value="pnpm" label="pnpm">
+  <div id="step1-install-pnpm">
+  ```
+  pnpm add -g genezio
+  ```
+  </div>
+  </TabItem>
+  <TabItem  className="tab-item" value="yarn" label="yarn">
+  <div id="step1-install-yarn">
+  ```
+  yarn add global genezio
+  ```
+  </div>
+  </TabItem>
+</Tabs>
+
+### 2. Start from an existing Ember template
+
+Create an Ember app using the following steps:
+
+<details>
+  <summary>**Create an Ember App**</summary>
+
+<h3> 1. Fork our Ember template repository on GitHub </h3>
+
+Go to https://github.com/Genez-io/ember-getting-started/fork and fork the repo.
+
+
+<h3> 2. Clone the newly created repository locally </h3>
+
+
+```bash
+git clone YOUR_REPO_URL
+cd ember-getting-started
+```
+
+<h3> 3. Run the Ember App locally </h3>
+
+Run the following command to start the Ember.js app locally:
+
+<div>
+  ```bash
+  ember serve
+  ```
+</div>
+
+<h3> 4. Test the Ember App locally </h3>
+
+Open a web browser and navigate to http://localhost:4200/ to see the app running.
+
+</details>
+
+## Create the Genezio Configuration File
+
+Now, create a `genezio.yaml` file in the root directory of your project.
+
+This file will contain the configuration needed to deploy your backend using Genezio. Here is an example configuration.
+
+:::info
+1. This example configuration works if **genezio.yaml** is in the same directory as your main application file.
+2. You might need to replace the `publish` directory value if it is different in your project.
+:::
+
+```yaml title="genezio.yaml"
+# Learn more about Genezio YAML at https://genezio.com/docs/project-structure/genezio-configuration-file/
+name: genezio-project
+region: us-east-1
+yamlVersion: 2
+frontend:
+    path: .
+    publish: dist
+    scripts:
+        deploy:
+            - npm install
+        build:
+            - npm run build
+        start:
+            - npm install
+            - npm run start
+```
+
+This configuration file specifies the project name, deployment region, and details about the frontend.
+
+## Deploy the app
+
+In your terminal run the following command to deploy your app to the Genezio cloud:
+
+<div>
+  ```bash
+  genezio deploy
+  ```
+</div>
+
+You should now see 2 URLs in the terminal window with the following format:
+
+```bash
+$ App Dashboard URL: https://app.genez.io/project/<project-id>/<stage-id>
+$ Frontend URL: https://<subdomain>.app.genez.io
+```
+
+## Next Steps
+
+After setting up the template, here are some recommended next steps:
+
+ <ul>
+    <li><a href="/docs/features/custom-domain-configuration/">Add Custom Domain</a></li>
+    <li><a href="./docs/features/deployments/">Learn more about Backend Deployment</a></li>
+</ul>
+
+## Support <a href="#support" id="support"></a>
+
+We invite you to join our community on [Discord](https://discord.gg/uc9H5YKjXv) for further information and help.
+
+**Happy Learning!**
diff --git a/docs/frameworks/fastapi.md b/docs/frameworks/fastapi.md
@@ -197,6 +197,7 @@ This file will contain the configuration needed to deploy your backend using Gen
 3. You might need to replace the `entry` field with the name of your main application file.
 4. You might need to replace the `path` field with the path relative at **genezio.yaml** file.
 5. This example configuration works if **genezio.yaml** is in the same directory as your main application file.
+6. The `runtime` field is the Python runtime to use for your FastAPI app, currently, the supported runtimes are: [python3.9.x, python3.10.x, python3.11.x, python3.12.x, python3.13.x]
    :::
 
 ```yaml title="genezio.yaml"
@@ -215,6 +216,8 @@ backend:
     name: python
     # The package manager used by the backend.
     packageManager: pip
+    # The runtime to use for your FastAPI app.
+    runtime: python3.13.x
   # Information about the backend's functions.
   functions:
     # The name (label) of the function.
@@ -286,6 +289,14 @@ After that, you can deploy your project without the `--env` flag.
 For more information about environment variables, you can check
 the [official documentation](/docs/project-structure/backend-environment-variables.md).
 
+:::note
+During the deployment process, Genezio automatically installs all dependencies specified in your `requirements.txt` file using:
+- The correct architecture (Linux x86)
+- The Python runtime specified in `genezio.yaml`
+
+This process ensures compatibility with our serverless infrastructure, defaulting to the latest Python 3.13.x version.
+:::
+
 ## See your app in Genezio Dashboard
 
 After deploying your application, you can test it to ensure it's running correctly. To verify that your FastAPI app is

diff --git a/docs/frameworks/flask.md b/docs/frameworks/flask.md
@@ -198,6 +198,7 @@ This file will contain the configuration needed to deploy your backend using Gen
 3. You might need to replace the `entry` field with the name of your main application file.
 4. You might need to replace the `path` field with the path relative at **genezio.yaml** file.
 5. This example configuration works if **genezio.yaml** is in the same directory as your main application file.
+6. The `runtime` field is the Python runtime to use for your Flask app, currently, the supported runtimes are: [python3.9.x, python3.10.x, python3.11.x, python3.12.x, python3.13.x]
    :::
 
 ```yaml title="genezio.yaml"
@@ -216,6 +217,8 @@ backend:
     name: python
     # The package manager used by the backend.
     packageManager: pip
+    # The runtime to use for your Flask app.
+    runtime: python3.13.x
   # Information about the backend's functions.
   functions:
     # The name (label) of the function.
@@ -287,6 +290,14 @@ After that, you can deploy your project without the `--env` flag.
 For more information about environment variables, you can check
 the [official documentation](/docs/project-structure/backend-environment-variables.md).
 
+:::note
+During the deployment process, Genezio automatically installs all dependencies specified in your `requirements.txt` file using:
+- The correct architecture (Linux x86)
+- The Python runtime specified in `genezio.yaml`
+
+This process ensures compatibility with our serverless infrastructure, defaulting to the latest Python 3.13.x version.
+:::
+
 ## See your app in Genezio Dashboard
 
 After deploying your application, you can test it to ensure it's running correctly. To verify that your Flask app is