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
Copy file name to clipboardExpand all lines: src/content/docs/tech-recommendations/infrastructure.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ wip: true
9
9
10
10
**Your go-to option for most projects**
11
11
12
-
Think of Amplify as the "easy button" for hosting full-stack apps. You've got a React frontend and Node.js backend? Amplify handles it all. Just connect your GitHub repo and it automatically deploys your app, sets up SSL, distributes it via CDN, and even creates preview environments for your pull requests. It's basically zero DevOps work.
12
+
Think of Amplify as the "easy button" for hosting full-stack apps. You've got a React frontend and Node.js backend? Amplify handles it all. Just connect your GitHub repo and it automatically deploys your app, sets up SSL, distributes it via CDN, and even creates preview environments for your pull requests. It's very little DevOps work, it just needs to be configured behind the right firewalls. ([Ask Tech Ops](https://github.com/newjersey/internal-ops/issues/new?template=request_new_website_webapp.yaml)) to get started.
13
13
14
14
**Use Amplify when**: You're building a normal web app and don't have weird requirements. Start here unless you have a specific reason not to.
15
15
@@ -65,14 +65,14 @@ curl -fsSL https://get.docker.com/ | sh
65
65
66
66
Docker Engine can still be easily installed on Linux without Docker Desktop. For Windows machines (e.g. agency stakeholders), we suggest using WSL (see [Setting up a state Windows laptop](/innovation-engineering/guides/development/windows-wsl2-setup/)), which can be harangued into running containers using the Docker engine on Linux.
67
67
68
-
## Domain management
69
-
70
-
**Note**: Hosting on a subdomain (e.g. `projectname.nj.gov`) is way easier than hosting on a subpath of `nj.gov` (e.g. `nj.gov/agencyname/projectname`)
71
-
72
-
**TODO**: Add content about how to get a subdomain set up.
73
-
74
68
## Infrastructure as Code
75
69
76
70
- AWS CDK - the recommended IaC. It will package up a lambda for you
77
71
- Terraform/OpenTofu - used by a couple of projects, is also cloud-agnostic
78
72
- Serverless - we do not start new projects with Serverless due to cost and pain points, but have migrated existing projects on Serverless from v3 to v4
73
+
74
+
## Tech Ops Configurations
75
+
76
+
Need to connect Amplify, or set up a domain? Submit an [Operations Request Ticket](https://github.com/newjersey/internal-ops/issues/new?template=request_new_website_webapp.yaml) for a new web application.
77
+
78
+
**Note**: Hosting on a subdomain (e.g. `projectname.nj.gov`) is way easier than hosting on a subpath of `nj.gov` (e.g. `nj.gov/agencyname/projectname`)
0 commit comments