├── .github
└── workflows
│ ├── export-repo-secrets.yml
│ └── publish.yaml
├── .gitignore
├── LICENSE
├── README.md
├── backend
├── CONTRIBUTING.md
├── Dockerfile
├── LICENSE
├── README.md
└── src
│ ├── .env
│ ├── app.js
│ ├── controllers
│ └── product.js
│ ├── models
│ └── Product.js
│ ├── package-lock.json
│ ├── package.json
│ ├── routes
│ └── product.js
│ ├── server.js
│ └── utils
│ ├── apiFeatures.js
│ └── catchAsync.js
├── data
├── Dockerfile
├── data.js
├── docker-healthcheck.sh
├── init.sh
└── products.json
└── frontend
├── .dockerignore
├── Dockerfile
└── client
├── README.md
├── package-lock.json
├── package.json
├── public
├── favicon.ico
├── favicon.png
├── index.html
├── logo192.png
├── logo512.png
├── manifest.json
└── robots.txt
└── src
├── App.jsx
├── components
├── cartProduct
│ └── CartProduct.jsx
├── filters
│ ├── Checkbox.jsx
│ ├── Sizes.jsx
│ └── checkbox.css
├── footer
│ └── Footer.jsx
├── header
│ ├── Header.jsx
│ ├── StoreHeader.jsx
│ └── header.module.css
├── loader
│ ├── Loader.css
│ └── Loader.jsx
└── products
│ ├── Product.jsx
│ ├── ProductsGrid.jsx
│ └── products.module.css
├── context
├── cartContext.js
└── cartReducer.js
├── img
├── classic_boba.png
├── ginger_boba.png
├── mango_chill.png
├── matcha_chill.png
├── matcha_latte.png
├── pulumipus_chill.png
├── science.png
├── strawberry_chill.png
├── taro_boba.png
├── taro_chill.png
└── thai_boba.png
├── index.css
├── index.js
├── serviceWorker.js
├── setupProxy.js
├── utils
└── fetch.js
└── views
├── cart
├── Cart.jsx
└── cart.module.css
├── homepage
└── Home.jsx
└── product
├── ViewProduct.jsx
└── product.module.css
/.github/workflows/export-repo-secrets.yml:
--------------------------------------------------------------------------------
1 | permissions: write-all # Equivalent to default permissions plus id-token: write
2 | name: Export secrets to ESC
3 | on: [ workflow_dispatch ]
4 | jobs:
5 | export-to-esc:
6 | runs-on: ubuntu-latest
7 | name: export GitHub secrets to ESC
8 | steps:
9 | - name: Generate a GitHub token
10 | id: generate-token
11 | uses: actions/create-github-app-token@v1
12 | with:
13 | app-id: 1256780 # Export Secrets GitHub App
14 | private-key: ${{ secrets.EXPORT_SECRETS_PRIVATE_KEY }}
15 | - name: Export secrets to ESC
16 | uses: pulumi/esc-export-secrets-action@v1
17 | with:
18 | organization: pulumi
19 | org-environment: github-secrets/pulumi-tutorial-pulumi-fundamentals
20 | exclude-secrets: EXPORT_SECRETS_PRIVATE_KEY
21 | github-token: ${{ steps.generate-token.outputs.token }}
22 | oidc-auth: true
23 | oidc-requested-token-type: urn:pulumi:token-type:access_token:organization
24 | env:
25 | GITHUB_SECRETS: ${{ toJSON(secrets) }}
26 |
--------------------------------------------------------------------------------
/.github/workflows/publish.yaml:
--------------------------------------------------------------------------------
1 | permissions: write-all # Equivalent to default permissions plus id-token: write
2 | name: Publish to Docker Hub
3 | on:
4 | push:
5 | branches:
6 | - main
7 | env:
8 | REGISTRY: docker.io
9 | FRONT_IMAGE_NAME: ${{ github.repository }}-frontend
10 | BACK_IMAGE_NAME: ${{ github.repository }}-backend
11 | DATABASE_IMAGE_NAME: ${{ github.repository }}-database
12 | ESC_ACTION_OIDC_AUTH: true
13 | ESC_ACTION_OIDC_ORGANIZATION: pulumi
14 | ESC_ACTION_OIDC_REQUESTED_TOKEN_TYPE: urn:pulumi:token-type:access_token:organization
15 | ESC_ACTION_ENVIRONMENT: github-secrets/pulumi-tutorial-pulumi-fundamentals
16 | ESC_ACTION_EXPORT_ENVIRONMENT_VARIABLES: false
17 |
18 | jobs:
19 | push-front-to-registry:
20 | name: Publish frontend image to Docker Hub
21 | runs-on: ubuntu-latest
22 | steps:
23 | - name: Fetch secrets from ESC
24 | id: esc-secrets
25 | uses: pulumi/esc-action@v1
26 | - name: Checkout
27 | uses: actions/checkout@v3
28 |
29 | - name: Log into Docker Hub
30 | uses: docker/login-action@v2
31 | with:
32 | username: ${{ steps.esc-secrets.outputs.DOCKERHUB_USERNAME }}
33 | password: ${{ steps.esc-secrets.outputs.DOCKERHUB_TOKEN }}
34 |
35 | - name: Add front metadata for Docker Hub
36 | id: meta-front
37 | uses: docker/metadata-action@v3
38 | with:
39 | images: ${{ env.REGISTRY }}/${{ env.FRONT_IMAGE_NAME }}
40 | flavor: |
41 | latest=true
42 |
43 |
44 | - name: Set up QEMU
45 | uses: docker/setup-qemu-action@v2
46 |
47 | - name: Set up Docker Buildx
48 | uses: docker/setup-buildx-action@v2
49 |
50 | - name: Build and push frontend image
51 | uses: docker/build-push-action@v3
52 | with:
53 | context: ./frontend/
54 | platforms: linux/amd64,linux/arm64
55 | push: true
56 | tags: ${{ steps.meta-front.outputs.tags }}
57 | labels: ${{ steps.meta-front.outputs.labels }}
58 |
59 | push-back-to-registry:
60 | name: Publish backend image to Docker Hub
61 | runs-on: ubuntu-latest
62 | steps:
63 | - name: Fetch secrets from ESC
64 | id: esc-secrets
65 | uses: pulumi/esc-action@v1
66 | - name: Checkout
67 | uses: actions/checkout@v3
68 |
69 | - name: Log into Docker Hub
70 | uses: docker/login-action@v2
71 | with:
72 | username: ${{ steps.esc-secrets.outputs.DOCKERHUB_USERNAME }}
73 | password: ${{ steps.esc-secrets.outputs.DOCKERHUB_TOKEN }}
74 |
75 | - name: Add back metadata for Docker Hub
76 | id: meta-back
77 | uses: docker/metadata-action@v3
78 | with:
79 | images: ${{ env.REGISTRY }}/${{ env.BACK_IMAGE_NAME }}
80 | flavor: |
81 | latest=true
82 |
83 |
84 | - name: Set up QEMU
85 | uses: docker/setup-qemu-action@v2
86 |
87 | - name: Set up Docker Buildx
88 | uses: docker/setup-buildx-action@v2
89 |
90 | - name: Build and push backend image
91 | uses: docker/build-push-action@v3
92 | with:
93 | context: ./backend/
94 | platforms: linux/amd64,linux/arm64
95 | push: true
96 | tags: ${{ steps.meta-back.outputs.tags }}
97 | labels: ${{ steps.meta-back.outputs.labels }}
98 |
99 | push-db-to-registry:
100 | name: Publish database image to Docker Hub
101 | runs-on: ubuntu-latest
102 | steps:
103 | - name: Fetch secrets from ESC
104 | id: esc-secrets
105 | uses: pulumi/esc-action@v1
106 | - name: Checkout
107 | uses: actions/checkout@v3
108 |
109 | - name: Log into Docker Hub
110 | uses: docker/login-action@v2
111 | with:
112 | username: ${{ steps.esc-secrets.outputs.DOCKERHUB_USERNAME }}
113 | password: ${{ steps.esc-secrets.outputs.DOCKERHUB_TOKEN }}
114 |
115 | - name: Add data metadata for Docker Hub
116 | id: meta-data
117 | uses: docker/metadata-action@v3
118 | with:
119 | images: ${{ env.REGISTRY }}/${{ env.DATABASE_IMAGE_NAME }}
120 | flavor: |
121 | latest=true
122 |
123 |
124 | - name: Set up QEMU
125 | uses: docker/setup-qemu-action@v2
126 |
127 | - name: Set up Docker Buildx
128 | uses: docker/setup-buildx-action@v2
129 |
130 | - name: Build and push database image
131 | uses: docker/build-push-action@v3
132 | with:
133 | context: ./data/
134 | platforms: linux/amd64,linux/arm64
135 | push: true
136 | tags: ${{ steps.meta-data.outputs.tags }}
137 | labels: ${{ steps.meta-data.outputs.labels }}
138 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # MacOS
2 | .DS_Store
3 | Icon?
4 | ._*
5 |
6 | # General building
7 | build/
8 | *.tgz
9 |
10 | # npm/yarn
11 | node_modules
12 | .npm/
13 | .yarn/
14 | *.log*
15 |
16 | # IDE
17 | .idea/
18 | */.idea/
19 | .vscode/
20 | */.vscode/
21 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | Apache License
2 | Version 2.0, January 2004
3 | http://www.apache.org/licenses/
4 |
5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6 |
7 | 1. Definitions.
8 |
9 | "License" shall mean the terms and conditions for use, reproduction,
10 | and distribution as defined by Sections 1 through 9 of this document.
11 |
12 | "Licensor" shall mean the copyright owner or entity authorized by
13 | the copyright owner that is granting the License.
14 |
15 | "Legal Entity" shall mean the union of the acting entity and all
16 | other entities that control, are controlled by, or are under common
17 | control with that entity. For the purposes of this definition,
18 | "control" means (i) the power, direct or indirect, to cause the
19 | direction or management of such entity, whether by contract or
20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the
21 | outstanding shares, or (iii) beneficial ownership of such entity.
22 |
23 | "You" (or "Your") shall mean an individual or Legal Entity
24 | exercising permissions granted by this License.
25 |
26 | "Source" form shall mean the preferred form for making modifications,
27 | including but not limited to software source code, documentation
28 | source, and configuration files.
29 |
30 | "Object" form shall mean any form resulting from mechanical
31 | transformation or translation of a Source form, including but
32 | not limited to compiled object code, generated documentation,
33 | and conversions to other media types.
34 |
35 | "Work" shall mean the work of authorship, whether in Source or
36 | Object form, made available under the License, as indicated by a
37 | copyright notice that is included in or attached to the work
38 | (an example is provided in the Appendix below).
39 |
40 | "Derivative Works" shall mean any work, whether in Source or Object
41 | form, that is based on (or derived from) the Work and for which the
42 | editorial revisions, annotations, elaborations, or other modifications
43 | represent, as a whole, an original work of authorship. For the purposes
44 | of this License, Derivative Works shall not include works that remain
45 | separable from, or merely link (or bind by name) to the interfaces of,
46 | the Work and Derivative Works thereof.
47 |
48 | "Contribution" shall mean any work of authorship, including
49 | the original version of the Work and any modifications or additions
50 | to that Work or Derivative Works thereof, that is intentionally
51 | submitted to Licensor for inclusion in the Work by the copyright owner
52 | or by an individual or Legal Entity authorized to submit on behalf of
53 | the copyright owner. For the purposes of this definition, "submitted"
54 | means any form of electronic, verbal, or written communication sent
55 | to the Licensor or its representatives, including but not limited to
56 | communication on electronic mailing lists, source code control systems,
57 | and issue tracking systems that are managed by, or on behalf of, the
58 | Licensor for the purpose of discussing and improving the Work, but
59 | excluding communication that is conspicuously marked or otherwise
60 | designated in writing by the copyright owner as "Not a Contribution."
61 |
62 | "Contributor" shall mean Licensor and any individual or Legal Entity
63 | on behalf of whom a Contribution has been received by Licensor and
64 | subsequently incorporated within the Work.
65 |
66 | 2. Grant of Copyright License. Subject to the terms and conditions of
67 | this License, each Contributor hereby grants to You a perpetual,
68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69 | copyright license to reproduce, prepare Derivative Works of,
70 | publicly display, publicly perform, sublicense, and distribute the
71 | Work and such Derivative Works in Source or Object form.
72 |
73 | 3. Grant of Patent License. Subject to the terms and conditions of
74 | this License, each Contributor hereby grants to You a perpetual,
75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76 | (except as stated in this section) patent license to make, have made,
77 | use, offer to sell, sell, import, and otherwise transfer the Work,
78 | where such license applies only to those patent claims licensable
79 | by such Contributor that are necessarily infringed by their
80 | Contribution(s) alone or by combination of their Contribution(s)
81 | with the Work to which such Contribution(s) was submitted. If You
82 | institute patent litigation against any entity (including a
83 | cross-claim or counterclaim in a lawsuit) alleging that the Work
84 | or a Contribution incorporated within the Work constitutes direct
85 | or contributory patent infringement, then any patent licenses
86 | granted to You under this License for that Work shall terminate
87 | as of the date such litigation is filed.
88 |
89 | 4. Redistribution. You may reproduce and distribute copies of the
90 | Work or Derivative Works thereof in any medium, with or without
91 | modifications, and in Source or Object form, provided that You
92 | meet the following conditions:
93 |
94 | (a) You must give any other recipients of the Work or
95 | Derivative Works a copy of this License; and
96 |
97 | (b) You must cause any modified files to carry prominent notices
98 | stating that You changed the files; and
99 |
100 | (c) You must retain, in the Source form of any Derivative Works
101 | that You distribute, all copyright, patent, trademark, and
102 | attribution notices from the Source form of the Work,
103 | excluding those notices that do not pertain to any part of
104 | the Derivative Works; and
105 |
106 | (d) If the Work includes a "NOTICE" text file as part of its
107 | distribution, then any Derivative Works that You distribute must
108 | include a readable copy of the attribution notices contained
109 | within such NOTICE file, excluding those notices that do not
110 | pertain to any part of the Derivative Works, in at least one
111 | of the following places: within a NOTICE text file distributed
112 | as part of the Derivative Works; within the Source form or
113 | documentation, if provided along with the Derivative Works; or,
114 | within a display generated by the Derivative Works, if and
115 | wherever such third-party notices normally appear. The contents
116 | of the NOTICE file are for informational purposes only and
117 | do not modify the License. You may add Your own attribution
118 | notices within Derivative Works that You distribute, alongside
119 | or as an addendum to the NOTICE text from the Work, provided
120 | that such additional attribution notices cannot be construed
121 | as modifying the License.
122 |
123 | You may add Your own copyright statement to Your modifications and
124 | may provide additional or different license terms and conditions
125 | for use, reproduction, or distribution of Your modifications, or
126 | for any such Derivative Works as a whole, provided Your use,
127 | reproduction, and distribution of the Work otherwise complies with
128 | the conditions stated in this License.
129 |
130 | 5. Submission of Contributions. Unless You explicitly state otherwise,
131 | any Contribution intentionally submitted for inclusion in the Work
132 | by You to the Licensor shall be under the terms and conditions of
133 | this License, without any additional terms or conditions.
134 | Notwithstanding the above, nothing herein shall supersede or modify
135 | the terms of any separate license agreement you may have executed
136 | with Licensor regarding such Contributions.
137 |
138 | 6. Trademarks. This License does not grant permission to use the trade
139 | names, trademarks, service marks, or product names of the Licensor,
140 | except as required for reasonable and customary use in describing the
141 | origin of the Work and reproducing the content of the NOTICE file.
142 |
143 | 7. Disclaimer of Warranty. Unless required by applicable law or
144 | agreed to in writing, Licensor provides the Work (and each
145 | Contributor provides its Contributions) on an "AS IS" BASIS,
146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147 | implied, including, without limitation, any warranties or conditions
148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149 | PARTICULAR PURPOSE. You are solely responsible for determining the
150 | appropriateness of using or redistributing the Work and assume any
151 | risks associated with Your exercise of permissions under this License.
152 |
153 | 8. Limitation of Liability. In no event and under no legal theory,
154 | whether in tort (including negligence), contract, or otherwise,
155 | unless required by applicable law (such as deliberate and grossly
156 | negligent acts) or agreed to in writing, shall any Contributor be
157 | liable to You for damages, including any direct, indirect, special,
158 | incidental, or consequential damages of any character arising as a
159 | result of this License or out of the use or inability to use the
160 | Work (including but not limited to damages for loss of goodwill,
161 | work stoppage, computer failure or malfunction, or any and all
162 | other commercial damages or losses), even if such Contributor
163 | has been advised of the possibility of such damages.
164 |
165 | 9. Accepting Warranty or Additional Liability. While redistributing
166 | the Work or Derivative Works thereof, You may choose to offer,
167 | and charge a fee for, acceptance of support, warranty, indemnity,
168 | or other liability obligations and/or rights consistent with this
169 | License. However, in accepting such obligations, You may act only
170 | on Your own behalf and on Your sole responsibility, not on behalf
171 | of any other Contributor, and only if You agree to indemnify,
172 | defend, and hold each Contributor harmless for any liability
173 | incurred by, or claims asserted against, such Contributor by reason
174 | of your accepting any such warranty or additional liability.
175 |
176 | END OF TERMS AND CONDITIONS
177 |
178 | APPENDIX: How to apply the Apache License to your work.
179 |
180 | To apply the Apache License to your work, attach the following
181 | boilerplate notice, with the fields enclosed by brackets "[]"
182 | replaced with your own identifying information. (Don't include
183 | the brackets!) The text should be enclosed in the appropriate
184 | comment syntax for the file format. We also recommend that a
185 | file or class name and description of purpose be included on the
186 | same "printed page" as the copyright notice for easier
187 | identification within third-party archives.
188 |
189 | Copyright [yyyy] [name of copyright owner]
190 |
191 | Licensed under the Apache License, Version 2.0 (the "License");
192 | you may not use this file except in compliance with the License.
193 | You may obtain a copy of the License at
194 |
195 | http://www.apache.org/licenses/LICENSE-2.0
196 |
197 | Unless required by applicable law or agreed to in writing, software
198 | distributed under the License is distributed on an "AS IS" BASIS,
199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200 | See the License for the specific language governing permissions and
201 | limitations under the License.
202 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Pulumi Fundamentals Tutorial
2 |
3 | The code in this repository is used in conjunction with the [Pulumi Learn "Pulumi Fundamentals" pathway](https://www.pulumi.com/learn/pulumi-fundamentals/). Details and full instructions for using this code are found there.
4 |
5 | ## Prerequisites
6 |
7 | You will need the following tools to complete this tutorial:
8 |
9 | * A [Pulumi account and token](https://www.pulumi.com/docs/pulumi-cloud/accounts#access-tokens)
10 | * If you don't have an account, go to the [signup page](https://app.pulumi.com/signup).
11 | * The [Pulumi CLI](https://www.pulumi.com/docs/cli/)
12 | * If you don't have the CLI, go to the [installation page](https://www.pulumi.com/docs/install/).
13 | * [Docker](https://docs.docker.com/get-docker/)
14 | * One of the following languages:
15 | * For the TypeScript/JavaScript version, Node.js 14 or later
16 | * For the Python version, Python 3.8 or later
17 | * For the Java version, Java 11 or later and Gradle 7.4 or later
18 | * For the YAML version, nothing specific!
19 |
--------------------------------------------------------------------------------
/backend/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contributing
2 |
3 | First off, thank you for considering contributing to Shopping Cart. It's people like you that make Shopping Cart a nice place to getting started on React and NodeJS.
4 |
5 | When contributing to this repository, please first discuss the change you wish to make via issue,
6 | email, or any other method with the owners of this repository before making a change.
7 |
8 | Please note we have a code of conduct, please follow it in all your interactions with the project.
9 |
10 | ## Pull Request Process
11 |
12 | 1. Ensure any install or build dependencies are removed before the end of the layer when doing a
13 | build.
14 | 1. Update the README.md with details of changes to the interface, this includes new environment
15 | variables, exposed ports, useful file locations and container parameters.
16 | 1. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
17 | do not have permission to do that, you may request the second reviewer to merge it for you.
18 | 1. Please link your pull request to an existing issue.
19 |
20 | ## Folder Structure
21 |
22 | ```bash
23 | ├── app.js
24 | ├── client
25 | │ ├── package.json
26 | │ ├── package-lock.json
27 | │ ├── public
28 | │ │ ├── favicon.ico
29 | │ │ ├── index.html
30 | │ │ ├── logo192.png
31 | │ │ ├── logo512.png
32 | │ │ ├── manifest.json
33 | │ │ └── robots.txt
34 | │ ├── README.md
35 | │ └── src
36 | │ ├── App.css
37 | │ ├── App.jsx
38 | │ ├── App.test.js
39 | │ ├── components
40 | │ │ ├── cartProduct
41 | │ │ │ └── CartProduct.jsx
42 | │ │ ├── checkbox
43 | │ │ │ └── Checkbox.jsx
44 | │ │ ├── footer
45 | │ │ │ └── Footer.jsx
46 | │ │ ├── header
47 | │ │ │ └── Header.jsx
48 | │ │ ├── loader
49 | │ │ │ ├── Loader.css
50 | │ │ │ └── Loader.jsx
51 | │ │ ├── product
52 | │ │ │ └── Product.jsx
53 | │ │ ├── select
54 | │ │ │ └── Select.jsx
55 | │ │ └── sizes
56 | │ │ ├── Sizes.css
57 | │ │ └── Sizes.jsx
58 | │ ├── context
59 | │ │ ├── cartContext.js
60 | │ │ └── cartReducer.js
61 | │ ├── index.css
62 | │ ├── index.js
63 | │ ├── serviceWorker.js
64 | │ ├── setupTests.js
65 | │ ├── utils
66 | │ │ └── fetch.js
67 | │ └── views
68 | │ ├── cart
69 | │ │ ├── Cart.css
70 | │ │ └── Cart.jsx
71 | │ └── products
72 | │ ├── Products.css
73 | │ └── Products.jsx
74 | ├── controllers
75 | │ └── product.js
76 | ├── data
77 | │ └── products.json
78 | ├── github
79 | ├── LICENSE
80 | ├── models
81 | │ └── Product.js
82 | ├── package.json
83 | ├── package-lock.json
84 | ├── README.md
85 | ├── routes
86 | │ └── product.js
87 | ├── server.js
88 | └── utils
89 | ├── apiFeatures.js
90 | └── catchAsync.js
91 | ```
92 |
93 | ## Scripts
94 |
95 | An explanation of the `package.json` scripts.
96 |
97 | | Command | Description |
98 | | --------------- | ------------------------------------------------------------------|
99 | | start | Start a production server for Shopping Cart |
100 | | dev | Start a nodemon dev server for the backend and front-end react |
101 | | server | Start a nodemon dev server for backend |
102 | | dev:server | Build the front-end and run a production server for Shopping Cart |
103 | | client | Start a dev server for Front-End |
104 | | heorku-postbuild| Build the Front-End for deploying to heroku |
105 |
106 | ## Technologies
107 |
108 | | Tech | Description |
109 | | --------------- | --------------------------------------------- |
110 | | NodeJs | JavaScript Runtime to create backend services |
111 | | Express | Server framework |
112 | | React | Front end user interface |
113 | | MongoDB | NoSQL Database to store Data |
114 | | Mongoose | Object Modelling for MongoDB |
115 |
116 | ## Code of Conduct
117 |
118 | ### Our Pledge
119 |
120 | In the interest of fostering an open and welcoming environment, we as
121 | contributors and maintainers pledge to making participation in our project and
122 | our community a harassment-free experience for everyone, regardless of age, body
123 | size, disability, ethnicity, gender identity and expression, level of experience,
124 | nationality, personal appearance, race, religion, or sexual identity and
125 | orientation.
126 |
127 | ### Our Standards
128 |
129 | Examples of behavior that contributes to creating a positive environment
130 | include:
131 |
132 | * Using welcoming and inclusive language
133 | * Being respectful of differing viewpoints and experiences
134 | * Gracefully accepting constructive criticism
135 | * Focusing on what is best for the community
136 | * Showing empathy towards other community members
137 |
138 | Examples of unacceptable behavior by participants include:
139 |
140 | * The use of sexualized language or imagery and unwelcome sexual attention or
141 | advances
142 | * Trolling, insulting/derogatory comments, and personal or political attacks
143 | * Public or private harassment
144 | * Publishing others' private information, such as a physical or electronic
145 | address, without explicit permission
146 | * Other conduct which could reasonably be considered inappropriate in a
147 | professional setting
148 |
149 | ### Our Responsibilities
150 |
151 | Project maintainers are responsible for clarifying the standards of acceptable
152 | behavior and are expected to take appropriate and fair corrective action in
153 | response to any instances of unacceptable behavior.
154 |
155 | Project maintainers have the right and responsibility to remove, edit, or
156 | reject comments, commits, code, wiki edits, issues, and other contributions
157 | that are not aligned to this Code of Conduct, or to ban temporarily or
158 | permanently any contributor for other behaviors that they deem inappropriate,
159 | threatening, offensive, or harmful.
160 |
161 | ### Scope
162 |
163 | This Code of Conduct applies both within project spaces and in public spaces
164 | when an individual is representing the project or its community. Examples of
165 | representing a project or community include using an official project e-mail
166 | address, posting via an official social media account, or acting as an appointed
167 | representative at an online or offline event. Representation of a project may be
168 | further defined and clarified by project maintainers.
169 |
170 | ### Enforcement
171 |
172 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
173 | reported by contacting the project team at shubham.battoo@hotmail.com. All
174 | complaints will be reviewed and investigated and will result in a response that
175 | is deemed necessary and appropriate to the circumstances. The project team is
176 | obligated to maintain confidentiality with regard to the reporter of an incident.
177 | Further details of specific enforcement policies may be posted separately.
178 |
179 | Project maintainers who do not follow or enforce the Code of Conduct in good
180 | faith may face temporary or permanent repercussions as determined by other
181 | members of the project's leadership.
182 |
183 | ### Attribution
184 |
185 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
186 | available at [http://contributor-covenant.org/version/1/4][version]
187 |
188 | [homepage]: http://contributor-covenant.org
189 | [version]: http://contributor-covenant.org/version/1/4/
190 |
--------------------------------------------------------------------------------
/backend/Dockerfile:
--------------------------------------------------------------------------------
1 | FROM node:14
2 |
3 | # Create app directory
4 | WORKDIR /usr/src/app
5 |
6 | COPY ./src/package*.json ./
7 |
8 | RUN npm install
9 | COPY ./src .
10 | RUN npm build
11 | EXPOSE 3000
12 |
13 | CMD [ "npm", "start" ]
--------------------------------------------------------------------------------
/backend/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2020 Shubham Battoo
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/backend/README.md:
--------------------------------------------------------------------------------
1 |
2 | Pulumipus Boba Tea Shop Demo using React and Express
3 |
4 |
5 | > MERN Shopping cart created with React, NodeJS, MongoDB
6 | >
7 | > Forked from https://github.com/shubhambattoo/shopping-cart
8 |
9 | ## Prerequisites
10 |
11 | If you are running from the tutorials, all you need is Pulumi and Docker. See
12 | [the start of the Docker lab](../README.md#Prerequisites) for more information.
13 |
14 | If you're running this app locally without the tutorial, you need the following tools:
15 |
16 | * NodeJS 12+
17 | * MongoDB installed locally
18 | * npm or yarn
19 |
20 | ## Getting Started
21 |
22 | Clone or Download
23 |
24 | ```sh
25 | git clone https://github.com/pulumi/tutorials.git
26 | cd tutorials/introduction-to-pulumi/docker/app/backend
27 | ```
28 |
29 | Run `npm install` to install all the dependencies
30 |
31 | Create a .env file:
32 |
33 | ```txt
34 | PORT=3000
35 | DATABASE_HOST=mongodb://yoururl/
36 | DATABASE_NAME=yourDBNAME
37 | NODE_ENV=development
38 | ```
39 |
40 | To import the mock product data to MongoDB, run the following command in your terminal from the app root:
41 |
42 | ```sh
43 | cd /data
44 | mongoimport --db [yourDBName] --collection products --file products.json --jsonArray
45 | ```
46 |
47 | To start up the backend services, run `npm start`. This command will start the backend service on port 3000.
48 |
49 | ## Client Side
50 |
51 | Development
52 |
53 | ```
54 | cd client
55 | npm install
56 | npm start
57 | ```
58 |
59 | This should start up the React application on port 3001.
60 |
61 | To view the web app, open [http://localhost:3001](http://localhost:3001).
62 |
63 | ## Contributing
64 |
65 | Contributions, issues and feature requests are welcome!
66 | Feel free to check [issues](https://github.com/pulumi/tutorials/issues) page.
67 |
68 | View [CONTRIBUTING.md](https://github.com/pulumi/tutorials/blob/master/CONTRIBUTING.md) to learn about the style guide, folder structure, scripts, and how to contribute.
69 |
70 | ## Contributors
71 |
72 |
77 | 
90 | 
101 | 
113 |