blog/Blog
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

chore: reformat TODO

Browse Source
This commit is contained in:
Price Hiller 2023-10-01 14:43:21 -05:00
parent 9218e6b567
commit a747d8d352
Signed by: Price
SSH Key Fingerprint: SHA256:Y4S9ZzYphRn1W1kbJerJFO6GGsfu9O70VaBSxJO7dF8
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
TODO.norg
View File

@ -1,22 +1,22 @@
* Code
- ( ) Clean up our Main function, it's kinda turning into a rats nest. It's great that I was able to hack it together
quickly, but it's kinda not great now. Needs improvement.
- ( ) Write some fucken tests my man, this shit is hanging in the wind unprotected right now. This is a relatively small
codebase as of the time of this TODO note, it's best to start writing them sooner rather than later.
- ( ) Look into minifying our `HTML` and `CSS` output, ideally we want the `gzipped` packet to be sub 14kb so the entire
page is transmitted during the first tcp roundtrip.
- ( ) Clean up our Main function, it's kinda turning into a rats nest. It's great that I was able to hack it together
quickly, but it's kinda not great now. Needs improvement.
- ( ) Write some fucken tests my man, this shit is hanging in the wind unprotected right now. This is a relatively small
codebase as of the time of this TODO note, it's best to start writing them sooner rather than later.
- ( ) Look into minifying our `HTML` and `CSS` output, ideally we want the `gzipped` packet to be sub 14kb so the entire
page is transmitted during the first tcp roundtrip.
* Styling
* CI/CD
- ( ) Get some gitlab-ci going here so we can do automated deployments.
- Probably the best way to do this is create an Ansible playbook that we then call from our CI engine. This will make
it easy to deploy from other devices besides the CI if needed and help with debugging, updates, etc. You know the
drill.
- ( ) Automate some linting, formatting, and auditing of the codebase
- `rustfmt` can be used for formatting
- `clippy` can be used for linting
- `cargo audit` can be used for auditing
- ( ) Get some gitlab-ci going here so we can do automated deployments.
-- Probably the best way to do this is create an Ansible playbook that we then call from our CI engine. This will make
it easy to deploy from other devices besides the CI if needed and help with debugging, updates, etc. You know the
drill.
- ( ) Automate some linting, formatting, and auditing of the codebase
-- `rustfmt` can be used for formatting
-- `clippy` can be used for linting
-- `cargo audit` can be used for auditing