• 2 Posts
  • 12 Comments
Joined 2 years ago
cake
Cake day: August 5th, 2023

help-circle





  • I do this for sites where I don’t care at all about security. One minor tip, that will protect against automated attacks if the password is cracked, is to add part of the website name into the password (e.g “mystrongp4ss!lemworld”) .

    A human could easily crack it, but automated systems that replay the password on different sites would probably not bother to calculate the pattern.



  • At $work we write closed source Rust but we do not use Kellnr.

    Instead we use a mono-repo, using a workspace, that contains most of our applications and libraries.

    Our setup is mostly OK but needs some workarounds for problems we have hit:

    • Slow cargo clean && cargo build, to speed this up we use sccache.
    • Very slow Docker builds. To speed these up we use cargo chef.
    • Slow CI/CD. To speed this up we use AWS instances as Github runners that we shutdown, but do not destroy, after use. This allows us to cache build dependencies for faster builds.

    I am generally happy with our setup, but I am a fan of mono-repos. If it ever becomes to difficult to keep compiles times reasonable, I think that we would definitely look at Kellnr.