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
* add rum config and compose file
* Update README.md to document compose
* Updated some stuff, added env vars back
* Update README.md
* Update README.md
* make git hash be version in rum
* Update README.md
* Fixing linting
* more fixing lint
Reach out to an RTP to get OIDC credentials that will allow you to develop locally behind OIDC auth.
64
+
#### OIDC
65
+
66
+
Reach out to an RTP to get OIDC credentials that will allow you to develop locally behind OIDC auth. You will need `PROFILES_OIDC_CLIENT_ID` and `PROFILES_OIDC_CLIENT_SECRET`
67
+
68
+
#### LDAP
65
69
66
70
```LDAP_BIND_DN``` is your CSH DN. It is in the following format:
67
71
68
72
```uid={CSH User Name},cn=users,cn=accounts,dc=csh,dc=rit,dc=edu```
69
73
74
+
```LDAP_BIND_PASS``` is your CSH password.
75
+
76
+
#### DATADOG
70
77
71
-
```LDAP_BIND_PASS``` is your CSH password.
78
+
```DATADOG_ENV``` is the env where you are developing, should stay local for local development
79
+
80
+
```DATADOG_APP_VERSION``` is the version of your app, when unset defaults to git commit hash
72
81
73
82
If you did everything right, you should be able to run ```python app.py``` and develop locally.
74
83
84
+
Running with Docker
85
+
--------------------
86
+
87
+
Alternatively, you can run profiles using docker or podman compose. You can configure the environment in same way as above, using a `config.py` file, or you can copy the `.env.example` file to `.env` and configure it there.
88
+
89
+
The docker-compose file is also set up for automatic redeploying with watch if you run with `podman compose up --watch --build`
0 commit comments