Skip to content

My implementation of TP 201: Practical Networked Applications in Rust

Notifications You must be signed in to change notification settings

jamrok/rust-practical-networked-applications

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

9 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

🦀 Practical Networked Applications (PNA) in Rust

Code Checks Security Audit codecov

A training course about practical systems software construction in Rust.

  • This is my implementation of Projects 1 to 4 from the PingCAP Talent Plan PNA Course:
    • TP 201: Practical Networked Applications in Rust. A series of projects that incrementally develop a single Rust project from the ground up into a high-performance, networked, parallel and asynchronous key/value store. Along the way various real-world Rust development subject matter are explored and discussed.
  • It was also a good use-case to deep dive into GitHub Actions and see how it compares to GitLab CI.

📑 Project outline:

🔋 Code Coverage

🪝 Git Hooks

Git Hooks are in the .hooks directory.

Run .hooks/enable or .hooks/disable to enable or disable them respectively.

The main hook is .hooks/pre-commit:

  • It is a script that is triggered by the git commit command.
  • It runs various commands in the script (similar to what is run in CI) to verify the files before completing the git commit command.
    • ℹ️ Some commands in the script check the files in the working directory, not only the files staged for commit.
    • ℹ️ Ensure everything you want to commit is staged as they will be committed if the checks pass.
  • To skip triggering this hook, append -n or --no-verify to the git commit command you ran.

🖼️ Latest Benchmark Snapshots (click to see details)

About

My implementation of TP 201: Practical Networked Applications in Rust

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published