pegasust
/
dotfiles
1
0
Fork 0
Code Issues 6 Pull Requests Projects Releases Wiki Activity

Roadmap for maximum productivity #11

New Issue
Open
opened 2023-03-02 02:43:15 +00:00 by pegasust · 4 comments
pegasust commented 2023-03-02 02:43:15 +00:00
Owner

What we currently have

  • Internally have nix-infra/nix-boost to provide numerous packages (like nix-community/nur but more informal). nix-boost also provides some "library" functions, though we should not be writing too much Nix code to start with. Keep it simple.
  • nix-infra/nix-templates which make bootstrapping easier to investigate. The only downside is composability within a single file is hard.

Proposals:

  • nix-boost: Use & maintain a private channel in gitea
  • Deploy Hydra
  • Deploy Binary Cache
  • Integrate Cachix or self-developed solution that watches /nix/store and publish asynchronously
  • Deploy dev and main environments for projects that need server infrastructure.
    • Dedicated servers should be ideal here
  • Service: Skip nixops and deploy-rs, focus on Nix + Kubernetes (?)
  • Observability: TIG stack + ELK stack to alert systems
  • Simplicity: dotfiles should contain only configuration modules, personal credentials.
  • DevEnv: Neovim should not be using Mason. Use nvim-lsp-config or configure your own. Build the environment from ground up with nix
  • PassMan: Develop a personal credentials that uses sops + credentials.yml
What we currently have - Internally have `nix-infra/nix-boost` to provide numerous packages (like `nix-community/nur` but more informal). `nix-boost` also provides some "library" functions, though we should not be writing too much Nix code to start with. Keep it simple. - `nix-infra/nix-templates` which make bootstrapping easier to investigate. The only downside is composability within a single file is hard. Proposals: - [x] `nix-boost`: Use & maintain a private channel in gitea - [ ] Deploy Hydra - [ ] Deploy Binary Cache - [ ] Integrate Cachix or self-developed solution that watches `/nix/store` and publish asynchronously - [ ] Deploy `dev` and `main` environments for projects that need server infrastructure. - [ ] Dedicated servers should be ideal here - [ ] Service: Skip `nixops` and `deploy-rs`, focus on Nix + Kubernetes (?) - [ ] Observability: TIG stack + ELK stack to alert systems - [ ] Simplicity: `dotfiles` should contain only configuration modules, personal credentials. - [ ] DevEnv: Neovim should not be using `Mason`. Use `nvim-lsp-config` or configure your own. Build the environment from ground up with `nix` - [ ] PassMan: Develop a personal credentials that uses `sops` + `credentials.yml`
pegasust commented 2023-05-16 14:56:16 +00:00
Poster
Owner

Regarding service deployment, we could probably test (and use) nixosModule with std as function or develop our own blockType

ACTION:

  • replace skipping nixops and deploy-rs to focus on Nix + Kubernetes
    • opt: deploy-rs blocktype
    • test deployment of bgp-config with deploy-rs in nix-infra
    • validate that secret ops work with deploy-rs in nix-infra
    • opt: nix-container blocktype
      • local action: deploy
      • local action: up
      • local action: down
      • local action: shell
      • This would help a lot if we could parametrize this
    • opt: nixosModule service framework
Regarding service deployment, we could probably test (and use) nixosModule with `std` as function or develop our own blockType ACTION: - [ ] replace skipping `nixops` and `deploy-rs` to focus on Nix + Kubernetes - [ ] opt: deploy-rs blocktype - [ ] test deployment of bgp-config with deploy-rs in nix-infra - [ ] validate that secret ops work with deploy-rs in nix-infra - [x] opt: nix-container blocktype - [x] local action: deploy - [ ] local action: up - [ ] local action: down - [ ] local action: shell - This would help a lot if we could parametrize this - [ ] opt: nixosModule service framework
pegasust commented 2023-06-18 09:28:25 +00:00
Poster
Owner

Kind of stale right now. The most important aspects are to try out tools in a different paradigm such as (tiling) window manager, nix-darwin,...

Kind of stale right now. The most important aspects are to try out tools in a different paradigm such as (tiling) window manager, `nix-darwin`,...
pegasust commented 2023-06-18 09:35:35 +00:00
Poster
Owner

We also found that std:blockType should be lightly be implemented due to the horizon the project is changing at the moment.

Just use the given blockTypes for now.

Also, we do have containers blocktype, just not as robust with these actions

We also found that `std:blockType` should be lightly be implemented due to the horizon the project is changing at the moment. Just use the given blockTypes for now. Also, we do have [`containers` blocktype](https://github.com/divnix/std/blob/8671b6892e45d795d7409940750832d68c929dcf/lib/blockTypes/containers.nix), just not as robust with these actions
pegasust commented 2023-06-18 09:54:36 +00:00
Poster
Owner
  • Put nixgl out into its separate stuff or contrib to upstream
- [ ] Put nixgl out into its separate stuff or contrib to upstream
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
bleed
telescope-reuse-window
lean
try-kitty
bare
master
std
top-level-wip
top-level-wip-bao
top-level-nix
lazy-refac
nix-refac
nix-rearch
nix-components
yaml
consolidate-nix
fix-pylsp
mason-deno-fix
archive/test-hm
archive/plugins-need-update
archive/boost
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: pegasust/dotfiles#11
There is no content yet.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?