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: templates/ords-remix-jwt-sample/README.md
+2-5Lines changed: 2 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,5 @@
1
1
# ORDS Concert App
2
2
3
-
<!---
4
-
TODO: Replace with a screenshot of the Concert App up and running, once we have the images.
5
-
-->
6
3

7
4
8
5
## What's in the project
@@ -49,11 +46,11 @@ You can create a `.env` file or rename the `.env.example` file to `.env` and use
49
46
# We refer to some variables as Autonomous Database specific but you can use whichever ORDS URL you want/have as well as the user, as long as this user is capable of creating and REST Enabling other schemas.
50
47
ADB_ORDS_URL=https://example.com:8080/ords/
51
48
ADB_ADMIN_USER=username
52
-
ADB_ADMIN_PASSWORD=password
49
+
ADB_ADMIN_PASSWORD=
53
50
54
51
# The name of the schema that will be created to host all of the ORDS Concert App database objects.
55
52
SCHEMA_NAME=ORDS_CONCERT_APP
56
-
SCHEMA_PASSWORD=<STRONG_PASSWORD>
53
+
SCHEMA_PASSWORD=
57
54
58
55
# Your Auth0 tenant JWT credentials, used by ORDS to validate request to protected endpoints.
0 commit comments