Skip to content

Commit 8ef8a6a

Browse files
hendrikebbershendrikebbers
authored
Initial commit
0 parents  commit 8ef8a6a

22 files changed

+17861
-0
lines changed

‎.gitignore

+25
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
2+
3+
# dependencies
4+
/node_modules
5+
/.pnp
6+
.pnp.js
7+
8+
# testing
9+
/coverage
10+
11+
# production
12+
/build
13+
14+
# misc
15+
.DS_Store
16+
.env
17+
.env.local
18+
.env.development.local
19+
.env.test.local
20+
.env.production.local
21+
22+
npm-debug.log*
23+
yarn-debug.log*
24+
yarn-error.log*
25+
/.idea/

‎Dockerfile

+15
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
FROM node:16 AS build
2+
WORKDIR /app
3+
ARG BACKEND_URL=http://localhost:5050
4+
ENV REACT_APP_BACKEND_URL=${BACKEND_URL}
5+
RUN echo "The Backend URL is '$REACT_APP_BACKEND_URL'"
6+
COPY package*.json ./
7+
RUN npm install
8+
COPY . .
9+
RUN npm run build
10+
11+
FROM nginx:alpine
12+
COPY --from=build /app/build /usr/share/nginx/html
13+
COPY nginx/nginx.conf /etc/nginx/nginx.conf
14+
EXPOSE 8000
15+
CMD ["nginx", "-g", "daemon off;"]

‎LICENSE

+201
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,201 @@
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.

‎README.md

+102
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
# Open Elements Frontend Template
2+
3+
This repository contains a template for a frontend application that can be used to build new frontend applications for Open Elements.
4+
The template is based on [React](https://reactjs.org/) and can be build by using [npm](https://www.npmjs.com/) or [Docker](https://www.docker.com/).
5+
The application is designed to work with a [backend API](https://github.com/OpenElements/backend-template).
6+
7+
## Start the app locally with npm
8+
9+
To start the app locally, you need to have Node.js installed on your machine.
10+
First, you need to install the dependencies by running the following command in the root directory of the project:
11+
12+
```bash
13+
npm install
14+
```
15+
16+
This will install all the dependencies needed to run the app.
17+
18+
Once that is done you can use npm to start the app.
19+
Here the following commands are available:
20+
21+
```bash
22+
npm start
23+
```
24+
25+
Runs the app in the development mode.
26+
Open [http://localhost:3000](http://localhost:3000) to view it in your browser.
27+
28+
The page will reload when you make changes.
29+
You may also see any lint errors in the console.
30+
31+
```bash
32+
npm test
33+
```
34+
35+
Launches the test runner in the interactive watch mode.
36+
37+
```bash
38+
npm run build
39+
```
40+
41+
Builds the app for production to the `build` folder.
42+
It correctly bundles React in production mode and optimizes the build for the best performance.
43+
44+
## Start the app in a Docker container
45+
46+
To start the app in a Docker container, we need to build the Docker image and run the container.
47+
48+
The Docker image is built by the following command that need to be executed in the root directory of the project:
49+
50+
```bash
51+
docker build -t frontend-template .
52+
```
53+
54+
This will build the Docker image with the name `frontend-template`.
55+
56+
To run the Docker container, execute the following command:
57+
58+
```bash
59+
docker run -d -p 5051:8000 frontend-template
60+
```
61+
62+
This will run the Docker container in detached mode (`-d`) and map the port 8000 of the container to the port 5051 of the host machine.
63+
Once that is done you can access the app by navigating to `http://localhost:5051` in your browser.
64+
65+
## Backend integration
66+
67+
The app is designed to work with a backend API.
68+
The URL of the backend API is defined in the `.env` file in the root directory of the project.
69+
The default value is `http://localhost:5050`.
70+
To override this value, you can create a `.env` file in the root directory of the project and define the `REACT_APP_BACKEND_URL` variable with the URL of the backend API.
71+
72+
```env
73+
REACT_APP_BACKEND_URL=http://localhost:6000
74+
```
75+
76+
An even higher priority has the direct definition of an environment variable with the same name.
77+
This can be done by executing the following command:
78+
79+
```bash
80+
export REACT_APP_BACKEND_URL=http://localhost:6000
81+
```
82+
83+
The repository contains a simple backend API that can be used for testing purposes.
84+
The backend can be started by executing the following command in the root directory of the project:
85+
86+
```bash
87+
npm run backend
88+
```
89+
90+
This will start the backend API on port 5050 and forward the requests to the backend API to the `data.json` file in the `backend` directory.
91+
92+
If you want to define a custom backend for the app while using docker locally you can use the following command:
93+
94+
```bash
95+
docker build --build-arg BACKEND_URL=http://new.server:123 -t frontend-template .
96+
```
97+
98+
## Deployment
99+
100+
Today Open Elements uses [koyeb](https://www.koyeb.com) to deploy the frontend and backend services.
101+
The backend can easily be configured by defining an environment variable as described [here](https://www.koyeb.com/docs/build-and-deploy/environment-variables#accessing-environment-variables-during-dockerfile-builds).
102+
If the backend is running in [koyeb](https://www.koyeb.com) you can easily add the URL of the backend to the environment.

‎backend/data.json

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
{
2+
"items": [
3+
{ "id": 1, "name": "Item 1" },
4+
{ "id": 2, "name": "Item 2" },
5+
{ "id": 3, "name": "Item 3" }
6+
]
7+
}
8+

0 commit comments

Comments
 (0)