vault backup: 2023-08-29 18:24:55
This commit is contained in:
@@ -4,14 +4,14 @@ week: 2023-W35
|
||||
year: 2023
|
||||
---
|
||||
#### To do 💪
|
||||
- [ ] Changer litière
|
||||
- [x] Changer litière ✅ 2023-08-29
|
||||
- [x] buy Galaxus stuff ✅ 2023-08-29
|
||||
|
||||
![[2023-W35#To do 💪]]
|
||||
|
||||
#### Habits ☕
|
||||
- [ ] Sport
|
||||
- [ ] Stretching
|
||||
- [x] Sport ✅ 2023-08-29
|
||||
- [x] Stretching ✅ 2023-08-29
|
||||
|
||||
| Calories | Weight |
|
||||
|--------|--------|
|
||||
@@ -19,11 +19,12 @@ year: 2023
|
||||
|
||||
#### Work 💻
|
||||
- [x] Fix the LiMa bug ✅ 2023-08-29
|
||||
- [ ] Deploy the Django app as Asgi with Uvicorn
|
||||
- [x] Deploy the Django app as Asgi with Uvicorn ✅ 2023-08-29
|
||||
|
||||
#### Notes ✏
|
||||
- I should check it out to be sure but I think ASGI applications are a superset of WSGI applications which means that by changing the main server deployment, we may be able to keep my setup while joining the forces on the same deployed server.
|
||||
- Started a [[Polyphasic]] sleep schedule, biphasic to be precise.
|
||||
- So the deployment in ASGI seems easier than what I thought. I'll still have to make it work on the server but I'm confident.
|
||||
|
||||
#### Outcomes 🦄
|
||||
1.
|
||||
26
Tracking/Daily/2023-08-30.md
Normal file
26
Tracking/Daily/2023-08-30.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
date: 2023-08-30
|
||||
week: 2023-W35
|
||||
year: 2023
|
||||
---
|
||||
#### To do 💪
|
||||
- [ ]
|
||||
|
||||
![[2023-W35#To do 💪]]
|
||||
|
||||
#### Habits ☕
|
||||
- [ ] Sport
|
||||
- [ ] Stretching
|
||||
|
||||
| Calories | Weight |
|
||||
|--------|--------|
|
||||
|2000 kcal|XX kg|
|
||||
|
||||
#### Work 💻
|
||||
- [ ] Try to deploy the ASGI app on the server.
|
||||
|
||||
#### Notes ✏
|
||||
-
|
||||
|
||||
#### Outcomes 🦄
|
||||
1.
|
||||
Reference in New Issue
Block a user