🧑🏻‍💻 | That buddy that will get everything ready for you [maintainer=@orzklv]
  • Rust 91.4%
  • Nix 7.9%
  • Just 0.7%
Find a file
Orzklv e351fcb2b6
Some checks failed
Test CI / test-flake (push) Has been cancelled
Test CI / test-project (push) Has been cancelled
Merge pull request #21 from xfeusw/refactor/where-reducing
2026-01-22 09:19:49 +05:00
.github chore: do ci/cd in self-hosted 2026-01-18 06:25:59 +05:00
src refactor: reduced where usages 2026-01-19 16:00:46 +05:00
.envrc chore: current builder ifnra 2025-06-28 18:16:42 +05:00
.gitignore chore: Ord for Tasks + replaces added 2026-01-09 11:03:38 +05:00
Cargo.lock chore: dumping version to 0.0.5 2026-01-18 09:45:02 +05:00
Cargo.toml chore: dumping version to 0.0.5 2026-01-18 09:45:02 +05:00
default.nix refactor: optimize flake 2026-01-11 19:29:54 +05:00
flake.lock chore: cleanup + init command 2026-01-09 12:51:08 +05:00
flake.nix refactor: optimize flake 2026-01-11 19:29:54 +05:00
justfile chore: just + debug for tasks 2026-01-12 12:11:21 +05:00
LICENSE-APACHE chore: add apache license to complete dualness 2026-01-09 12:58:24 +05:00
LICENSE-MIT chore: cleanup + init command 2026-01-09 12:51:08 +05:00
readme.md chore: update license notice 2026-01-11 23:31:48 +05:00
shell.nix chore: just + debug for tasks 2026-01-12 12:11:21 +05:00

Bleur's {Buddy}

Template manager & buddy for bleur-org/templates.

Top Used Language

This is template manager/assistant for creating/managing your own tempalte or bootstrapping a project using ready-to-go templates from remote. Also, this project itself was bootstrapped using Bleur's templates!

Development

The project has shell.nix which has development environment preconfigured already for you. Just open your terminal and at the root of this project:

# Open in bash by default
nix develop

# If you want other shell
nix develop -c $SHELL

# After entering Nix development environment,
# inside the env, you can open your editor, so
# your editor will read all $PATH and environmental
# variables, also your terminal inside your editor
# will adopt all variables, so, you can close terminal.

# Neovim
vim .

# VSCode
code .

# Zed Editor
zed .

The development environment has whatever you may need already, but feel free to add or remove whatever inside shell.nix.

Building

Well, there are two ways of building your project. You can either go with classic cargo build way, but before that, make sure to enter development environment to have cargo and all rust toolchain available in your PATH, you may do like that:

# Entering development environment
nix develop -c $SHELL

# Compile the project
cargo build --release

Or, you can build your project via nix which will do all the dirty work for you. Just, in your terminal:

# Build in nix environment
nix build

# Executable binary is available at:
./result/bin/bleur

FAQ

Why not use default.nix for devShell?

There's been cases when I wanted to reproduce totally different behaviors in development environment and production build. This occurs quite a lot lately for some reason and because of that, I tend to keep both shell.nix and default.nix to don't mix things up.

Thanks

License

This project is dual licensed under the MIT License and Apache-2.0 - see the LICENSE-MIT and LICENSE-APACHE files for details. Proudly written and developed by human, no usage of AI (LLM) at all, only brain and compiler.

Bleur's {Buddy}