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: README.md
+8-14Lines changed: 8 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ You shouldn't have to make any other changes to get this up and running, but her
11
11
12
12
- The default login credentials are admin and admin_password. These can be changed in backend/.env.
13
13
14
-
- There are 3 .env files provided. Note in particular the .env files in backend/ and postgres/; there, you can adjust the database credentials, debug mode, secret key, allowed hosts, etc. Things should run just fine without any changes, but just know these files are there.
14
+
- There are 3 .env files provided. Note in particular the .env files in backend/ and postgres/; there, you can adjust the database credentials, debug mode, secret key, allowed hosts, etc. The app should run just fine without any changes, but just know these files are there.
15
15
16
16
- The included sample helloyou django app can be easily removed by removing 'helloyou' from INSTALLED_APPS in django mainapp/settings.py, removing the associated helloyou path in mainapp/urls.py and deleting the entire helloyou folder. There are no database migrations, so you don't need to worry about that. On the frontend, delete/replace the contents of Home.tsx.
17
17
@@ -20,28 +20,21 @@ You shouldn't have to make any other changes to get this up and running, but her
20
20
21
21
**_NOTE: If you change your database name/credentials, but have already run the steps below, you may need to delete the associated postgres docker image in order to get things to work._**
22
22
23
-
For development mode without NGINX server, run the following command:
23
+
For development mode without NGINX server (recommended for development), run the following command:
24
24
25
25
```sh
26
26
docker-compose -f "docker-compose.dev.yml" up -d --build
27
27
```
28
28
The react frontend should be available at `http://localhost:3000/` and django backend at `http://localhost:8000/` (django admin at `http://localhost:8000/admin/`). This mode supports both react hot reloading and django auto-refresh with changes.
29
29
30
-
For development with the NGINX server run:
31
-
```sh
32
-
docker-compose -f "docker-compose.yml" up -d --build
33
-
```
34
-
The server should be available at `http://127.0.0.1/`. This mode will not hot reload since it's running a production build (npm build).
35
-
36
-
37
30
## Features
38
31
### Forgot Password:
39
-
- The password reset feature is fully functional. In order to get the password reset url, you will need to open the backend django console. Enter the following in an application like PowerShell:
32
+
- The password reset feature is fully functional. In order to get the password reset url, you will need to open the backend django logs. For example (in Powershell):
- Upon submitting a valid email, you should get a path like `http://localhost:3000/password_reset?token=abcdefgxyz123`; paste this in your browser to access the password reset form. The password reset form first validates the token;if the token is valid, it presents the password reset interface and allows the user to provide a new password. If the token is invalid, it will redirect the user to the login page.
37
+
- Upon submitting a valid email (default is ), you should get a path like `http://localhost:3000/password_reset?token=abcdefgxyz123`; paste this in your browser to access the password reset form. The password reset form first validates the token;if the token is valid, it presents the password reset interface and allows the user to provide a new password. If the token is invalid, it will redirect the user to the login page.
45
38
46
39
Check out the Django docs starting [here](https://docs.djangoproject.com/en/3.1/topics/email/#smtp-backend) in order to update the Email Backend from a console output to an actual SMTP backend.
47
40
@@ -53,7 +46,8 @@ The server should be available at `http://127.0.0.1/`. This mode will not hot re
53
46
54
47
### Alerts:
55
48
- An alert setter at the context level is also included. An example of TriggerAlert is shown in Home.tsx (variants displayed after successful/failed submit). See AlertContext.tsx for typings.
56
-
-
49
+
50
+
57
51
### Modal/Dialog:
58
52
- Similar to the alert setter, a context level modal/dialog is also provided. Use OpenDialog (basic example shown in Home.tsx) to open and set the modal title/contents/footer.
59
53
@@ -79,10 +73,10 @@ The server should be available at `http://127.0.0.1/`. This mode will not hot re
79
73
- [x] Add support for nested sub-routes off the main left-nav routes
80
74
- [x] Ensure match params (i.e. /user/profile/1/) work correctly.
81
75
- [x] Context level modal?
76
+
- [x] Auto redirect to login with Failed Request
82
77
- [ ] Reset session timeout with activity.
83
78
- [ ] Swagger API Explorer
84
79
- [ ] Backend Testing
85
80
- [ ] Frontend Testing (React Testing Library)
86
-
- [ ] Auto redirect to login with Failed Request
87
81
- [ ] Axios Interface for demo API
88
82
- [ ] Update and Pin versions (remove anything unused)
0 commit comments