How to use .env files with your rust project

It is very important that secrets are stored in environment variables during the runtime. During the development, it makes sense to use .env file. In my last project, there were probably 40+ variables in the .env. Although that project was in RoR the idea of .env itself is not new. But for me, using .env with rust is new. For my current (self) assignment, I needed to store an API Key.

Why I switched to Zellij

I had tried switching to tmux for local shell sessions in past, but never truly understood why I might need it. I extensively used tmux for remote sessions. But why might I need it locally ? Then slowly I stopped using tmux and switched to wezterm which provided multiple tabs. Fast forward several years later. Recently I came across Zellij. I decided to give it a go. When I had tried tmux it took some time to get used to the keybinding.

How I generated 2000 parallel requests using nu-shell

At work, I need to load test new framework I had deployed. Usually, I work with QA team. They use JMeter (with Azure Load test) for such task. But today, the QA person was busy with other tasks, and I didn’t want to get blocked. Since I am learning rust, (nu-shell is built in rust) I remembered that it may be possible to run parallel requests in nu-shell. and it is!

Clippy

Clippy is a linter for Rust programming language. If you are annoyed by the compiler (shouting at telling you how your code is wrong), wait till you install and use clippy 😄 Jokes apart, why I want to use clippy is it tells us about idiomatic rust and can autofix issues (if we tell it to do so) Couple of fun facts I discovered : First search result for clippy is not what I was looking for 😄 till I searched for rust clippy clippy can not be installed via cargo install (As I tried initially) (As with rest of the rust ecosystem) there was a helpful error message with solution 😇 error: Clippy is no longer available via crates.

Nu Shell

Earlier I wrote about various utilities written in rust. Nu shell is one of the most important of them (It is an entire shell after all, not just single utility) Installing Turns out I had installed nu-shell earlier, but via macports and I had forgotten about macports (and nu shell) Mysterious upgrade failure (Or so I thought) When I installed nu-shell via brew I got the latest version, but nu kept invoking older version.

→ Oxidise Your Life ∞

This youtube video mentions the following tools:

• exa
• bat
• zellij
• mprocs
• ripgrep
• irust
• bacon
• cargo-info
• ncspot
• porsmo
• speedtest-rs
• rtx-cli

Of these I installed zellij, which is replacement for tmux (or screen)

I also installed mprocs, irust

I already have ripgrep

I had tried exa and bat in past, they are good but novelty item.

Installing bacon failed during the compile step :(

I’ve also installed nu-shell

I’ll write about nu-shell separately, after giving it enough time

100 Days of Rust : Day 9 (Testing)

I continued reading Command Line Applications in Rust Learnt that testing is easy. Any function that has #[test] above it, will be found (across any files) and used by cargo test Couple of interesting crates : exitcode It has quite well defined exit codes. They come from FreeBSD I wish other languages / frameworks had something similar proptest is a property testing framework Based on python’s Hypothesis I need to spend time actually trying this human-panic Generates report file on panic Shows nice (if a bit long) message to the user, asking them to (optionally) email the report file to the developer 🤯 Things to explore:

100 Days of Rust : Day 8

Today I started reading Command Line Applications in Rust Even though I have not finished reading “the book”, I am (by now) familiar with enough rust code that reading this book was kinda refreshing. Few important things I picked up : {:?} in println! is called debug representation (quite useful for .. debugging 😄) Custom data types can add support for {:?} for debugging and logging, one needs to add a #[derive(Debug) above their definition.

100 Days of Rust : Day 7

Technically this may be more like day 8 or 9, cause I did read some stuff from the rust book in last few days, and made note here Nothing improves your understanding better than doing – Me 😄 I was trying accessing the individual fields in tuple struct using dot notation via the index Since the rust book does not have an example of it, I used rust playground (Awesome resource BTW) and just printed stuff.

100 Days of Rust : Day 6 (Ownership)

When I started reading about Ownership, I was thinking I have done C. I understand memory But Rust book explains : If you are familiar with systems programming, you might think of memory at a low level like “memory is an array of bytes” or “memory is the pointers I get back from malloc”. .. The low-level model is too concrete to explain how Rust works. Rust does not allow you to interpret memory as an array of bytes, for instance.