Skip to content

Commit be97f7f

Browse files
committed
2nd upload
Added scripts and setup-dev-environment folder.
1 parent bcd9a39 commit be97f7f

File tree

163 files changed

+1826
-268
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

163 files changed

+1826
-268
lines changed

frontend/README.md

Lines changed: 0 additions & 209 deletions
This file was deleted.

mytodoreact/CONTRIBUTING.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
## MyToDoReact version 1.0.
2+
##
3+
## Copyright (c) 2021 Oracle, Inc.
4+
## Licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl/
5+
6+
# Contributing
7+
8+
We welcome your contributions! There are multiple ways to contribute.
9+
10+
## Issues
11+
For bugs or enhancement requests, please file a GitHub issue unless it's security related. When filing a bug remember that the better written the bug is, the more likely it is to be fixed. If you think you've found a security vulnerability, do not raise a GitHub issue and follow the instructions on our [Security Policy](./SECURITY.md).
12+
13+
## Contributing Code
14+
15+
We welcome your code contributions. To get started, you will need to sign the [Oracle Contributor Agreement](https://www.oracle.com/technetwork/community/oca-486395.html) (OCA).
16+
17+
For pull requests to be accepted, the bottom of your commit message must have
18+
the following line using the name and e-mail address you used for the OCA.
19+
20+
```
21+
Signed-off-by: Your Name <you@example.org>
22+
```
23+
24+
This can be automatically added to pull requests by committing with:
25+
26+
```
27+
git commit --signoff
28+
```
29+
30+
Only pull requests from committers that can be verified as having
31+
signed the OCA can be accepted.
32+
33+
### Pull request process
34+
35+
1. Fork this repository
36+
1. Create a branch in your fork to implement the changes. We recommend using
37+
the issue number as part of your branch name, e.g., `1234-fixes`
38+
1. Ensure that any Javadoc and/or documentation is updated with the changes.
39+
1. Add a test for the new behaviour (or that exercises the bug if a bug fix).
40+
1. Submit the pull request. *Do not leave the pull request text blank*. Explain exactly
41+
what your changes are meant to do and provide simple steps on how to validate
42+
your changes. Ensure that you reference the issue you created as well. The PR
43+
name will be the name of the squashed commit to main.
44+
1. We will assign the pull request to be reviewed before it is merged.
45+
46+
## Code of Conduct
47+
Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). More specific guidelines are in the [Contributor Covenant Code of Conduct](./CODE_OF_CONDUCT.md)

mytodoreact/LICENSE.txt

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
Copyright (c) 2019, 2020 Oracle and/or its affiliates.
2+
3+
The Universal Permissive License (UPL), Version 1.0
4+
5+
Subject to the condition set forth below, permission is hereby granted to any
6+
person obtaining a copy of this software, associated documentation and/or data
7+
(collectively the "Software"), free of charge and under any and all copyright
8+
rights in the Software, and any and all patent rights owned or freely
9+
licensable by each licensor hereunder covering either (i) the unmodified
10+
Software as contributed to or provided by such licensor, or (ii) the Larger
11+
Works (as defined below), to deal in both
12+
13+
(a) the Software, and
14+
(b) any piece of software and/or hardware listed in the lrgrwrks.txt file if
15+
one is included with the Software (each a "Larger Work" to which the Software
16+
is contributed by such licensors),
17+
18+
without restriction, including without limitation the rights to copy, create
19+
derivative works of, display, perform, and distribute the Software and make,
20+
use, sell, offer for sale, import, export, have made, and have sold the
21+
Software and the Larger Work(s), and to sublicense the foregoing rights on
22+
either these or other terms.
23+
24+
This license is subject to the following condition:
25+
The above copyright notice and either this complete permission notice or at
26+
a minimum a reference to the UPL must be included in all copies or
27+
substantial portions of the Software.
28+
29+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
30+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
31+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
32+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
33+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
34+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
35+
SOFTWARE.

mytodoreact/README.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# MyToDoReact version 1.0.
2+
Copyright (c) 2021 Oracle, Inc.
3+
4+
Licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl/
5+
6+
# My ToDo List React application for Java developers
7+
## Introduction and Overview
8+
9+
In this workshop, you will deploy a simple Cloud native application using the most commonly used frameworks and the Oracle Cloud Infrastructure services.
10+
11+
![](./images/Application.png " ")
12+
13+
You will will learn how to use the Autonomous Database, the Container Registry, the Kubernetes Cluster (OKE) , Helidon, and the API Gateway managed services of the Oracle Cloud Infrastructure through the deployment of a simple MyToDo List React JS application.
14+
![](./images/architecture.png " ")
15+
16+
## Let's Get Started!
17+
18+
This lab has 3 parts however, you need first to setup a Cloud account
19+
## **STEP 1**: Sign up for a Free Trial Cloud Account
20+
Click on [Sign Up For a Free Trial](?lab=sign-up-for-free-trial) to get your Oracle Free Trial. If you already have an Oracle Free Trial or Paid account, you can proceed to [Part 1: Setup Dev Environment](?setup-dev-environment/README.md).
21+
22+
## Want to Learn More?
23+
24+
* [https://developer.oracle.com/](https://developer.oracle.com/)
25+
26+
## Acknowledgements
27+
* **Workshop by** - Kuassi Mensah, Dir. Product Management, Java Database Access
28+
* **Application by** - Jean de Lavarene, Sr. Director of Development, JDBC/UCP
29+
* **Original scripts by** - Paul Parkinson, Developer Evangelist, Microservices
30+
31+
## Need Help?
32+
Please submit feedback or ask for help using this [LiveLabs Support Forum](https://community.oracle.com/tech/developers/categories/building-microservices-with-oracle-converged-database). Please login using your Oracle Sign On and click the **Ask A Question** button to the left. You can include screenshots and attach files. Communicate directly with the authors and support contacts. Include the *lab* and *step* in your request.

mytodoreact/SECURITY.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
2+
## MyToDoReact version 1.0.
3+
##
4+
## Copyright (c) 2021 Oracle, Inc.
5+
## Licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl/
6+
# Reporting Security Vulnerabilities
7+
8+
Oracle values the independent security research community and believes that responsible disclosure of security vulnerabilities helps us ensure the security and privacy of all our users.
9+
10+
Please do NOT raise a GitHub Issue to report a security vulnerability. If you believe you have found a security vulnerability, please submit a report to [secalert\_us@oracle.com](mailto:secalert_us@oracle.com) preferably with a proof of concept. We provide additional information on [how to report security vulnerabilities to Oracle](https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html) which includes public encryption keys for secure email.
11+
12+
We ask that you do not use other channels or contact project contributors directly.
13+
14+
Non-vulnerability related security issues such as new great new ideas for security features are welcome on GitHub Issues.
15+
16+
### Security Updates, Alerts and Bulletins
17+
18+
Security updates will be released on a regular cadence. Many of our projects will typically release security fixes in conjunction with the [Oracle Critical Patch Update](https://www.oracle.com/security-alerts/) program. Security updates are released on the Tuesday closest to the 17th day of January, April, July and October. A pre-release announcement will be published on the Thursday preceding each release. Additional information, including past advisories, is available on our [Security Alerts](https://www.oracle.com/security-alerts/) page.
19+
20+
### Security-Related Information
21+
22+
We will provide security related information such as a threat model, considerations for secure use, or any known security issues in our documentation. Please note that labs and sample code are intended to demonstrate a concept and may not be sufficiently hardened for production use.

0 commit comments

Comments
 (0)