Skip to content

Commit a4e0d60

Browse files
committed
reafctor: drops requirement of specific framework for logging
the requirement is being revised to have python navtive application level logging,the actual log aggretation is an infrasatructure level requirement not an application specific requirement REFS #7
1 parent c5c0233 commit a4e0d60

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ This lab aims to outline a recipe for building a standardised Python server that
88
- [ ] Healthcheck endpoint that will validate that the API can get to the database
99
- [x] Worker processes that will process tasks in the background (using [TasIQ](https://github.com/taskiq-python/taskiq))
1010
- [x] Provide `Dockerfile` for development and production
11-
- [ ] Log aggregation and monitoring ([parseable](https://github.com/parseablehq/parseable))
11+
- [ ] Application level logging
1212
- [x] ~~CSRF protection~~ see [#52](https://github.com/anomaly/lab-python-server/issues/52), also see [official guide](https://fastapi.tiangolo.com/tutorial/cors/)
1313
- [x] Basic endpoints for authentication (JWT and OTP based) - along with recommendations for encryption algorithms
1414

0 commit comments

Comments
 (0)