You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[Understanding your Nimbella Project](#Understanding-Your-Nimbella-Project)
26
+
-[Cleaning your Nimbella Namespace](#Cleaning-your-Nimbella-Namespace)
27
+
-[Exporting Environment Variables to Serverless APIs](#Exporting-Environment-Variables-to-Serverless-APIs)
28
+
-[Example Projects](#Example-Projects)
29
+
-[Support](#Support)
30
+
-[License](#License)
30
31
31
32
## Add-On Setup
32
33
@@ -114,11 +115,11 @@ Your Nimbella project may also include a `web` folder which can be deployed to t
114
115
web = true
115
116
```
116
117
117
-
## Cleaning your Nimbella Namespace
118
+
####Cleaning your Nimbella Namespace
118
119
119
120
The Nimbella project configuration (`project.yml`) allows for cleaning your namespace, or deployed API package. See [the documentation](https://docs.nimbella.com/configuration#adding-project-configuration) for more details on sanitizing the namespace between deployments.
120
121
121
-
## Exporting Environment Variables to Serverless APIs
122
+
####Exporting Environment Variables to Serverless APIs
122
123
123
124
If your serverless APIs require environment variables, you have to export the variables explicitly in the `plugins.input` section of the `netlify.toml` file. This is to avoid exporting the entire environment to your APIs, and instead selecting exporting only the variables the actions need access to.
0 commit comments