#flake — Public Fediverse posts

Using a repo like codeberg and #git for managing a #flake for #nixos that applies for all multiple machines of a fleet each, having their own git branch, using the .#<machine_of_fleet> is really hard. Does anyone do this too? Why is it so hard? For example I have stopped using #checkout as a command because it makes no sense to me and leads to confusion, and use switch and restore. Also I have made a mental note not to refer to "main" in any operation other than the one master machine. Tips?

https://www.wacoca.com/media/640079/ 大阪・南堀江のレコード＆CDショップ
「FLAKE RECORDS」の20周年記念
イベントの開催が決定！ – NEWS | ぴあ関西版WEB #20周年 #DAWA #FLAKE #FLAKERECORDS #music #pia #ticket #チケット #ぴあ #ぴあ関西版WEB #ブレイク #フレイクレコード #レコード屋 #南堀江 #関西 #音楽

https://www.wacoca.com/media/640079/ 大阪・南堀江のレコード＆CDショップ
「FLAKE RECORDS」の20周年記念
イベントの開催が決定！ – NEWS | ぴあ関西版WEB #20周年 #DAWA #FLAKE #FLAKERECORDS #music #pia #ticket #チケット #ぴあ #ぴあ関西版WEB #ブレイク #フレイクレコード #レコード屋 #南堀江 #関西 #音楽

https://www.wacoca.com/media/640079/ 大阪・南堀江のレコード＆CDショップ
「FLAKE RECORDS」の20周年記念
イベントの開催が決定！ – NEWS | ぴあ関西版WEB #20周年 #DAWA #FLAKE #FLAKERECORDS #music #pia #ticket #チケット #ぴあ #ぴあ関西版WEB #ブレイク #フレイクレコード #レコード屋 #南堀江 #関西 #音楽

Ver la letra de la canción “Flake” de Jack Johnson
#JackJohnson #Flake
https://daletra.net/jack-johnson/letras/flake.html

Entdecken Sie den Text des Liedes “Flake” von Jack Johnson
#JackJohnson #Flake
https://daletra.top/jack-johnson/liedtexte/flake.html

@freya I am trying out #ZFS on my "homelab" server but was most surprised that it seems one has to do all the ZFS setup external to the #flake which only lives within the manually made ZFS pool environment. That seems to mean I need a sort of orchestration script like tool to match flake /persist data settings (am using #impermanence lite currently) to the ZFS setup hoo-ha. Works fine but is not declarative #nixos at all really. Any ideas there ?

@freya I am trying out #ZFS on my "homelab" server but was most surprised that it seems one has to do all the ZFS setup external to the #flake which only lives within the manually made ZFS pool environment. That seems to mean I need a sort of orchestration script like tool to match flake /persist data settings (am using #impermanence lite currently) to the ZFS setup hoo-ha. Works fine but is not declarative #nixos at all really. Any ideas there ?

@freya I am trying out #ZFS on my "homelab" server but was most surprised that it seems one has to do all the ZFS setup external to the #flake which only lives within the manually made ZFS pool environment. That seems to mean I need a sort of orchestration script like tool to match flake /persist data settings (am using #impermanence lite currently) to the ZFS setup hoo-ha. Works fine but is not declarative #nixos at all really. Any ideas there ?

@freya I am trying out #ZFS on my "homelab" server but was most surprised that it seems one has to do all the ZFS setup external to the #flake which only lives within the manually made ZFS pool environment. That seems to mean I need a sort of orchestration script like tool to match flake /persist data settings (am using #impermanence lite currently) to the ZFS setup hoo-ha. Works fine but is not declarative #nixos at all really. Any ideas there ?

@freya I am trying out #ZFS on my "homelab" server but was most surprised that it seems one has to do all the ZFS setup external to the #flake which only lives within the manually made ZFS pool environment. That seems to mean I need a sort of orchestration script like tool to match flake /persist data settings (am using #impermanence lite currently) to the ZFS setup hoo-ha. Works fine but is not declarative #nixos at all really. Any ideas there ?

Solution in #nixos #flake for machine ThinkPad #x230 seems to be:
services.xserver.enable = true;
services.displayManager.gdm.enable = true;
services.desktopManager.gnome.enable = true;
services.desktopManager.gnome.flashback.enableMetacity = true;
# At the GDM login screen, click the gear # icon to choose between:
# - "GNOME" (Wayland)
# - "GNOME Flashback (Metacity)" #X11
and
nixos-rebuild boot + reboot is required (not switch) when jumping across major nixpkgs versions

Solution in #nixos #flake for machine ThinkPad #x230 seems to be:
services.xserver.enable = true;
services.displayManager.gdm.enable = true;
services.desktopManager.gnome.enable = true;
services.desktopManager.gnome.flashback.enableMetacity = true;
# At the GDM login screen, click the gear # icon to choose between:
# - "GNOME" (Wayland)
# - "GNOME Flashback (Metacity)" #X11
and
nixos-rebuild boot + reboot is required (not switch) when jumping across major nixpkgs versions

Solution in #nixos #flake for machine ThinkPad #x230 seems to be:
services.xserver.enable = true;
services.displayManager.gdm.enable = true;
services.desktopManager.gnome.enable = true;
services.desktopManager.gnome.flashback.enableMetacity = true;
# At the GDM login screen, click the gear # icon to choose between:
# - "GNOME" (Wayland)
# - "GNOME Flashback (Metacity)" #X11
and
nixos-rebuild boot + reboot is required (not switch) when jumping across major nixpkgs versions

Solution in #nixos #flake for machine ThinkPad #x230 seems to be:
services.xserver.enable = true;
services.displayManager.gdm.enable = true;
services.desktopManager.gnome.enable = true;
services.desktopManager.gnome.flashback.enableMetacity = true;
# At the GDM login screen, click the gear # icon to choose between:
# - "GNOME" (Wayland)
# - "GNOME Flashback (Metacity)" #X11
and
nixos-rebuild boot + reboot is required (not switch) when jumping across major nixpkgs versions

Solution in #nixos #flake for machine ThinkPad #x230 seems to be:
services.xserver.enable = true;
services.displayManager.gdm.enable = true;
services.desktopManager.gnome.enable = true;
services.desktopManager.gnome.flashback.enableMetacity = true;
# At the GDM login screen, click the gear # icon to choose between:
# - "GNOME" (Wayland)
# - "GNOME Flashback (Metacity)" #X11
and
nixos-rebuild boot + reboot is required (not switch) when jumping across major nixpkgs versions

Have I understood it right that an update of a #flake in #nixos , which has a .git , is performed without staging it first... i.e. the lock files are used independently of git and are an exception to the rule that changes have to be staged before testing a build and switch?

Have I understood it right that an update of a #flake in #nixos , which has a .git , is performed without staging it first... i.e. the lock files are used independently of git and are an exception to the rule that changes have to be staged before testing a build and switch?

Have I understood it right that an update of a #flake in #nixos , which has a .git , is performed without staging it first... i.e. the lock files are used independently of git and are an exception to the rule that changes have to be staged before testing a build and switch?

Have I understood it right that an update of a #flake in #nixos , which has a .git , is performed without staging it first... i.e. the lock files are used independently of git and are an exception to the rule that changes have to be staged before testing a build and switch?

Have I understood it right that an update of a #flake in #nixos , which has a .git , is performed without staging it first... i.e. the lock files are used independently of git and are an exception to the rule that changes have to be staged before testing a build and switch?

Could it be that if flake check crashes or freezes your machine then your flake and or your computer are officially silly? Is there a way of using an already extant remote build facility in the actual flake check also? #nixos #flake #flakecheck

Could it be that if flake check crashes or freezes your machine then your flake and or your computer are officially silly? Is there a way of using an already extant remote build facility in the actual flake check also? #nixos #flake #flakecheck

Could it be that if flake check crashes or freezes your machine then your flake and or your computer are officially silly? Is there a way of using an already extant remote build facility in the actual flake check also? #nixos #flake #flakecheck

Could it be that if flake check crashes or freezes your machine then your flake and or your computer are officially silly? Is there a way of using an already extant remote build facility in the actual flake check also? #nixos #flake #flakecheck

Could it be that if flake check crashes or freezes your machine then your flake and or your computer are officially silly? Is there a way of using an already extant remote build facility in the actual flake check also? #nixos #flake #flakecheck

Confira a letra da música “Flake” de Jack Johnson
#JackJohnson #Flake
https://daletra.com.br/jack-johnson/letra/flake.html

Confira a letra da música “Flake” de Jack Johnson
#JackJohnson #Flake
https://daletra.com.br/jack-johnson/letra/flake.html

Scopri il testo della canzone “Flake” di Jack Johnson
#JackJohnson #Flake
https://daletra.online/jack-johnson/testi/flake.html

@stadtkind @edwtjo Thanks for the input. FYI this is my playbook for this #git #nixos #flake synch / reconciliation process when two flakes have deviated and you want to make them the same by using a repo, e.g. codeberg , as the single source of truth. The solution uses the branch main on the main computer which has the main flake that should be up to date always, & a branch on the other machine named after the machine. The other machine will always commit to its branch https://codeberg.org/adingbatponder/reticulum_nixos_flake/src/branch/main/docs/git-flake-reconciliation.md

@stadtkind @edwtjo Thanks for the input. FYI this is my playbook for this #git #nixos #flake synch / reconciliation process when two flakes have deviated and you want to make them the same by using a repo, e.g. codeberg , as the single source of truth. The solution uses the branch main on the main computer which has the main flake that should be up to date always, & a branch on the other machine named after the machine. The other machine will always commit to its branch https://codeberg.org/adingbatponder/reticulum_nixos_flake/src/branch/main/docs/git-flake-reconciliation.md

@stadtkind @edwtjo Thanks for the input. FYI this is my playbook for this #git #nixos #flake synch / reconciliation process when two flakes have deviated and you want to make them the same by using a repo, e.g. codeberg , as the single source of truth. The solution uses the branch main on the main computer which has the main flake that should be up to date always, & a branch on the other machine named after the machine. The other machine will always commit to its branch https://codeberg.org/adingbatponder/reticulum_nixos_flake/src/branch/main/docs/git-flake-reconciliation.md

@stadtkind @edwtjo Thanks for the input. FYI this is my playbook for this #git #nixos #flake synch / reconciliation process when two flakes have deviated and you want to make them the same by using a repo, e.g. codeberg , as the single source of truth. The solution uses the branch main on the main computer which has the main flake that should be up to date always, & a branch on the other machine named after the machine. The other machine will always commit to its branch https://codeberg.org/adingbatponder/reticulum_nixos_flake/src/branch/main/docs/git-flake-reconciliation.md

@stadtkind @edwtjo Thanks for the input. FYI this is my playbook for this #git #nixos #flake synch / reconciliation process when two flakes have deviated and you want to make them the same by using a repo, e.g. codeberg , as the single source of truth. The solution uses the branch main on the main computer which has the main flake that should be up to date always, & a branch on the other machine named after the machine. The other machine will always commit to its branch https://codeberg.org/adingbatponder/reticulum_nixos_flake/src/branch/main/docs/git-flake-reconciliation.md

@stadtkind @edwtjo Well I really got into a spin. When doing the above where you
1. pull a new flake down into a directory with a new name /flake-new
2. rename the old /flake directory /flake-old
3. rename /flake-new as /flake and check this out as branch
4. try nixos-rebuild switch --flake .#<machine_name>

caused the rebuild command not to switch. It just kept giving me the old generation...because I was doing 4. from previous main but should be done from the new branch #nixos #flake #git

@stadtkind @edwtjo Well I really got into a spin. When doing the above where you
1. pull a new flake down into a directory with a new name /flake-new
2. rename the old /flake directory /flake-old
3. rename /flake-new as /flake and check this out as branch
4. try nixos-rebuild switch --flake .#<machine_name>

caused the rebuild command not to switch. It just kept giving me the old generation...because I was doing 4. from previous main but should be done from the new branch #nixos #flake #git

@stadtkind @edwtjo Well I really got into a spin. When doing the above where you
1. pull a new flake down into a directory with a new name /flake-new
2. rename the old /flake directory /flake-old
3. rename /flake-new as /flake and check this out as branch
4. try nixos-rebuild switch --flake .#<machine_name>

caused the rebuild command not to switch. It just kept giving me the old generation...because I was doing 4. from previous main but should be done from the new branch #nixos #flake #git

@stadtkind @edwtjo Well I really got into a spin. When doing the above where you
1. pull a new flake down into a directory with a new name /flake-new
2. rename the old /flake directory /flake-old
3. rename /flake-new as /flake and check this out as branch
4. try nixos-rebuild switch --flake .#<machine_name>

caused the rebuild command not to switch. It just kept giving me the old generation...because I was doing 4. from previous main but should be done from the new branch #nixos #flake #git

@stadtkind @edwtjo Well I really got into a spin. When doing the above where you
1. pull a new flake down into a directory with a new name /flake-new
2. rename the old /flake directory /flake-old
3. rename /flake-new as /flake and check this out as branch
4. try nixos-rebuild switch --flake .#<machine_name>

caused the rebuild command not to switch. It just kept giving me the old generation...because I was doing 4. from previous main but should be done from the new branch #nixos #flake #git

Text des Liedes “Flake” von Jack Johnson
#JackJohnson #Flake
https://daletra.top/jack-johnson/liedtexte/flake.html

Do you have a single #nixos #flake for multiple devices using different #nixosconfigurations in which for each device you have a specified /persist data location as part of an #impermanence setup? I am looking for examples, tips and foot-gun alerts.... cheers.

Do you have a single #nixos #flake for multiple devices using different #nixosconfigurations in which for each device you have a specified /persist data location as part of an #impermanence setup? I am looking for examples, tips and foot-gun alerts.... cheers.

Do you have a single #nixos #flake for multiple devices using different #nixosconfigurations in which for each device you have a specified /persist data location as part of an #impermanence setup? I am looking for examples, tips and foot-gun alerts.... cheers.

Do you have a single #nixos #flake for multiple devices using different #nixosconfigurations in which for each device you have a specified /persist data location as part of an #impermanence setup? I am looking for examples, tips and foot-gun alerts.... cheers.

Do you have a single #nixos #flake for multiple devices using different #nixosconfigurations in which for each device you have a specified /persist data location as part of an #impermanence setup? I am looking for examples, tips and foot-gun alerts.... cheers.

Confira a letra da música “Flake” de Jack Johnson
#JackJohnson #Flake
https://daletra.com.br/jack-johnson/letra/flake.html

Sehen Sie den Text des Liedes “Flake” von Jack Johnson
#JackJohnson #Flake
https://daletra.top/jack-johnson/liedtexte/flake.html

@stiefkind Als langjähriger Tonmeister bei der lit.RUHR muss ich sagen, dass du Recht hast, wenn du Recht hast. Aber jedesmal wenn du nicht Recht hattest war es so unfassbar klasse, dass ich nur ermutigen kann, das Risiko immer mal wieder einzugehen.

#arnogeiger #carolinewahl (okgeschmackssache!) #wolfhaas #frankgoosen #paulmaar #luisaneubauer #marionbrasch #jaroslavrudiš #johnlecarré #maxgoldt #flake ...

#litruhr #zollverein

@stiefkind Als langjähriger Tonmeister bei der lit.RUHR muss ich sagen, dass du Recht hast, wenn du Recht hast. Aber jedesmal wenn du nicht Recht hattest war es so unfassbar klasse, dass ich nur ermutigen kann, das Risiko immer mal wieder einzugehen.

#arnogeiger #carolinewahl (okgeschmackssache!) #wolfhaas #frankgoosen #paulmaar #luisaneubauer #marionbrasch #jaroslavrudiš #johnlecarré #maxgoldt #flake ...

#litruhr #zollverein

@stiefkind Als langjähriger Tonmeister bei der lit.RUHR muss ich sagen, dass du Recht hast, wenn du Recht hast. Aber jedesmal wenn du nicht Recht hattest war es so unfassbar klasse, dass ich nur ermutigen kann, das Risiko immer mal wieder einzugehen.

#arnogeiger #carolinewahl (okgeschmackssache!) #wolfhaas #frankgoosen #paulmaar #luisaneubauer #marionbrasch #jaroslavrudiš #johnlecarré #maxgoldt #flake ...

#litruhr #zollverein