Compare commits

..

5 Commits

Author SHA1 Message Date
6a9ccd5766
dist: install fpkg to /usr/bin
All checks were successful
Tests / Go tests (push) Successful in 38s
Nix / NixOS tests (push) Successful in 3m42s
This is a high level user-facing tool.

Signed-off-by: Ophestra <cat@gensokyo.uk>
2024-12-29 01:04:53 +09:00
661e46e132
cmd/fpkg/start: correct drop to shell wording
All checks were successful
Tests / Go tests (push) Successful in 35s
Nix / NixOS tests (push) Successful in 3m35s
Activation no longer happens during application startup.

Signed-off-by: Ophestra <cat@gensokyo.uk>
2024-12-29 00:56:14 +09:00
5d8823b6eb
nix: generate application package build script
All checks were successful
Tests / Go tests (push) Successful in 35s
Nix / NixOS tests (push) Successful in 3m58s
This takes some metadata, sandbox options, a launch script and a list of home-manager modules. The result needs to be executed in an environment with nix daemon access, and it produces the final package file.

Signed-off-by: Ophestra <cat@gensokyo.uk>
2024-12-29 00:53:59 +09:00
aa09e3bf58
cmd/fpkg: app bundle helper
All checks were successful
Tests / Go tests (push) Successful in 35s
Nix / NixOS tests (push) Successful in 3m29s
This helper program creates fortify configuration for running an application bundle. The activate action wraps a home-manager activation package and ensures each generation gets activated once.

Signed-off-by: Ophestra <cat@gensokyo.uk>
2024-12-28 23:58:41 +09:00
6f7402ac29
internal: include path to fortify main program
Signed-off-by: Ophestra <cat@gensokyo.uk>
2024-12-26 12:48:48 +09:00
2 changed files with 2 additions and 2 deletions

View File

@ -36,7 +36,7 @@ package
*Default:*
` <derivation fortify-0.2.8> `
` <derivation fortify-0.2.7> `

View File

@ -14,7 +14,7 @@
buildGoModule rec {
pname = "fortify";
version = "0.2.8";
version = "0.2.7";
src = builtins.path {
name = "fortify-src";