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
{{ message }}
This repository was archived by the owner on May 20, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/guides/nodejs/api-with-nextjs.mdx
+24-18Lines changed: 24 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -392,37 +392,43 @@ Pressing `ctrl + a + k` will end the application.
392
392
393
393
## Deploy to the cloud
394
394
395
-
### Deploy the Nitric API
395
+
At this point, you can deploy what you've built to any of the supported cloud providers. In this example we'll deploy to AWS. Start by setting up your credentials and configuration for the [nitric/aws provider](/providers/pulumi/aws).
396
396
397
-
Setup credentials and cloud specific configuration:
397
+
Next, we'll need to create a `stackfile` (deployment target). A stack is a deployed instance of an application. You might want separate stacks for each environment, such as stacks for `dev`, `test`, and `prod`. For now, let's start by creating a file for the `dev` stack.
398
398
399
-
- [AWS](/providers/pulumi/aws)
400
-
- [Azure](/providers/pulumi/azure)
401
-
- [GCP](/providers/pulumi/gcp)
399
+
The `stacknew` command below will create a stack named `dev` that uses the `aws` provider.
402
400
403
-
Create a stack, which is a deployment target for your application.
404
-
405
-
```
406
-
nitricstacknew
401
+
```bash
402
+
nitricstacknewdevaws
407
403
```
408
404
405
+
Edit the stack file `nitric.dev.yaml` and set your preferred AWS region, for example `us-east-1`.
Copy file name to clipboardExpand all lines: docs/guides/nodejs/expressjs.mdx
+22-21Lines changed: 22 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,8 +46,9 @@ You can go ahead and open this new project in your editor of choice. You should
46
46
├── node_modules
47
47
│ ├── ...
48
48
├── .gitignore
49
-
├── index.js
50
49
├── nitric.yaml
50
+
├── node.dockerfile
51
+
├── node.dockerfile.dockerignore
51
52
├── package.json
52
53
├── README.md
53
54
└── yarn.lock
@@ -150,38 +151,38 @@ This is where the true value of Nitric shines. You don't need to perform any man
150
151
151
152
To perform the deployment we'll create a `stack`, stacks give Nitric the configuration needed for a specific cloud instance of this project, such as the provider and region.
152
153
153
-
The new stack command can help you create the stack by following prompts.
154
+
The `stack new`command below will create a stack named `dev` that uses the `aws` provider.
154
155
155
156
```bash
156
-
nitric stack new
157
+
nitric stack new dev aws
157
158
```
158
159
159
-
This command will create a file named `nitric.dev.yaml`, with contents like this:
160
+
Edit the stack file `nitric.dev.yaml` and set your preferred AWS region, for example `us-east-1`.
Copy file name to clipboardExpand all lines: docs/guides/nodejs/fastify.mdx
+23-22Lines changed: 23 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,8 +46,9 @@ You can go ahead and open this new project in your editor of choice. You should
46
46
├── node_modules
47
47
│ ├── ...
48
48
├── .gitignore
49
-
├── index.js
50
49
├── nitric.yaml
50
+
├── node.dockerfile
51
+
├── node.dockerfile.dockerignore
51
52
├── package.json
52
53
├── README.md
53
54
└── yarn.lock
@@ -168,40 +169,40 @@ At this point, we can stop the running application and try to deploy it to a clo
168
169
169
170
This is where the true value of Nitric shines. You don't need to perform any manual cloud deployment activities or add solutions like Terraform to get this project into your cloud environment, Nitric takes care of that for you.
170
171
171
-
To perform the deployment we'll create a `stack`, stacks give Nitric the config needed for a specific cloud instance of this project, such as the provider and region.
172
+
To perform the deployment we'll create a `stack`, stacks give Nitric the configuration needed for a specific cloud instance of this project, such as the provider and region.
172
173
173
-
The new stack command can help you create the stack by following prompts.
174
+
The `stack new`command below will create a stack named `dev` that uses the `aws` provider.
174
175
175
176
```bash
176
-
nitric stack new
177
+
nitric stack new dev aws
177
178
```
178
179
179
-
This command will create a file named `nitric.dev.yaml`, with contents like this:
180
+
Edit the stack file `nitric.dev.yaml` and set your preferred AWS region, for example `us-east-1`.
0 commit comments