Official NixOS Wiki - User contributions [en]

NixOS Wiki/ru

2025-01-18T18:18:32Z

Unabomberlive:

<languages/>
__NOTOC__
<div class="row home-panes">
<div class="col-md-7">
{{home:box|get-started|icon=clarifications|Приступаем|
Это официальная Wiki NixOS.
Она включает в себя темы, не освещённые в [https://nixos.org/nixos/manual Мануале по NixOS]: руководства пользователя NixOS, примеры конфигурации и советы по устранению неполадок.

NixOS — это операционная система на базе Linux ядра, основанная на менеджере пакетов Nix и репозитории пакетов Nixpkgs.

Новичкам в NixOS рекомендуется прочитать обзорную статью [[Nix Ecosystem|Экосистема Nix]], чтобы получить полное представление. Для более конкретного ознакомления см. :
* [[NixOS]]
* [[Nix package manager|Пакетный менеджер Nix]]
* [[Nixpkgs|Репозиторий пакетов Nixpkgs]]
* [[Overview of the Nix Language |Общее представление о Nix языке]]
Если вы хотите попробовать Nix в автономном режиме на другом дистрибутиве Linux или на Mac, ознакомьтесь с [[nix.dev]].

В экосистеме Nix существует множество дополнительных инструментов, таких как:

* [[Home Manager|Home-manager]] для управления профилем пользователя и содержимым домашнего каталога
* [[Flakes|Nix Flakes]] для управления зависимости проектов Nix

Они добавляют сложности и поначалу могут сбить с толку, и вы даже можете решить, что они вам не нужны.
Начните с простой Nix/NixOS, а Home Manager и/или Flakes интегрируйте в свою систему только после того, как вы уверенно освоите Nix/NixOS и поймете их значение.}}

{{home:box|hosting|icon=cloud|Установка NixOS|

* На Персональном Компьютере, с [[NixOS_as_a_desktop/ru|NixOS на ПК]]
* На ARM, с [[NixOS on ARM]]
* В облаке, с помощью [[NixOS friendly hosters]]
}}

{{home:box|doctopics|icon=manual|Разделы документации|
Первым пунктом должны быть [[Resources]], который служит шлюзом к наиболее важной документации. Некоторые основные моменты приведены ниже.

Основные справочные материалы:
* [https://nixos.org/nixos/manual/ Руководство по NixOS]
* [https://nixos.org/nix/manual/ Руководство по Nix]
* [https://nixos.org/nixpkgs/manual/ Руководство по Nixpkgs]
* [https://nixos.org/hydra/manual/ Руководство Hydra]

Основные категории страниц:
* [[:{{ns:14}}:Software|Программное обеспечение]]
* [[:{{ns:14}}:Hardware|Аппаратное обеспечение]]
* [[:{{ns:14}}:Desktop|Desktop]] - настройка для ПК
* [[:{{ns:14}}:Server|Server]] - настройка для Сервера
* [[:{{ns:14}}:Community|Community]] - люди, общение, работа над NixOS

См. также:
* [[FAQ|Часто задаваемые вопросы]]
* [[Nix vs. Linux Standard Base|Nix против стандартной базы Linux]]
* [[Terms and Definitions in Nix Project|Термины и определения в Nix Project]]
* [[Cheatsheet|Cheatsheet]]
* [[Ubuntu vs. NixOS|Сравнение между Ubuntu и NixOS]]
}}

{{home:box|wikipages|Служебные страницы|3=<ul>
<li><span class="plainlinks">[{{fullurl:Special:SpecialPages}} Overview of special pages]</span></li>
<li><span class="plainlinks">[{{fullurl:Special:AllPages|hideredirects=1}} Все страницы на {{SERVERNAME}}]</span></li>
<li>[[Special:Categories|Все категории на {{SERVERNAME}}]]</li>
<li>[{{fullurl:Special:RecentChanges|hidebots=1&reviewStatus=unpatrolled}} Непроверенные изменения на {{SERVERNAME}}]</li>
</ul>}}
</div>
<div class="col-md-5">
{{home:box|get-in-touch|icon=dialog-hi|Связь|
<b>С сообществом</b>
* [https://nixos.org/ Официальный сайт NixOS]
* [https://nixos.org/community/#governance-teams Команда разработчиков]
* [[Nix Community|Обзор сообщества]]
* [[Get In Touch|Чаты и форумы]]
* [[Support|Получить поддержку]]
* [[Get In Touch#Events|События]]

<b> О Wiki</b>
* Чат Matrix для редакторов Wiki
* [[Contributing|Поучаствовать в развитии NixOs и Wiki]]
* [[Manual of Style]]
}}
{{home:box|news|Новости|{{NixOS_Wiki:News}}
[[NixOS_Wiki:News{{!}}... все новостные статьи →]]
}}
</div>
</div>

Translations:NixOS Wiki/11/ru

2025-01-18T18:18:31Z

Unabomberlive:

<b> О Wiki</b>
* Чат Matrix для редакторов Wiki
* [[Contributing|Поучаствовать в развитии NixOs и Wiki]]
* [[Manual of Style]]
}}
{{home:box|news|Новости|{{NixOS_Wiki:News}}
[[NixOS_Wiki:News{{!}}... все новостные статьи →]]
}}
</div>
</div>

NixOS Wiki/ru

2025-01-16T15:32:05Z

Unabomberlive:

<languages/>
__NOTOC__
<div class="row home-panes">
<div class="col-md-7">
{{home:box|get-started|icon=clarifications|Приступаем|
Это официальная Wiki NixOS.
Она включает в себя темы, не освещённые в [https://nixos.org/nixos/manual Мануале по NixOS]: руководства пользователя NixOS, примеры конфигурации и советы по устранению неполадок.

NixOS — это операционная система на базе Linux ядра, основанная на менеджере пакетов Nix и репозитории пакетов Nixpkgs.

Новичкам в NixOS рекомендуется прочитать обзорную статью [[Nix Ecosystem|Экосистема Nix]], чтобы получить полное представление. Для более конкретного ознакомления см. :
* [[NixOS]]
* [[Nix package manager|Пакетный менеджер Nix]]
* [[Nixpkgs|Репозиторий пакетов Nixpkgs]]
* [[Overview of the Nix Language |Общее представление о Nix языке]]
Если вы хотите попробовать Nix в автономном режиме на другом дистрибутиве Linux или на Mac, ознакомьтесь с [[nix.dev]].

В экосистеме Nix существует множество дополнительных инструментов, таких как:

* [[Home Manager|Home-manager]] для управления профилем пользователя и содержимым домашнего каталога
* [[Flakes|Nix Flakes]] для управления зависимости проектов Nix

Они добавляют сложности и поначалу могут сбить с толку, и вы даже можете решить, что они вам не нужны.
Начните с простой Nix/NixOS, а Home Manager и/или Flakes интегрируйте в свою систему только после того, как вы уверенно освоите Nix/NixOS и поймете их значение.}}

{{home:box|hosting|icon=cloud|Установка NixOS|

* На Персональном Компьютере, с [[NixOS_as_a_desktop/ru|NixOS на ПК]]
* На ARM, с [[NixOS on ARM]]
* В облаке, с помощью [[NixOS friendly hosters]]
}}

{{home:box|doctopics|icon=manual|Разделы документации|
Первым пунктом должны быть [[Resources]], который служит шлюзом к наиболее важной документации. Некоторые основные моменты приведены ниже.

Основные справочные материалы:
* [https://nixos.org/nixos/manual/ Руководство по NixOS]
* [https://nixos.org/nix/manual/ Руководство по Nix]
* [https://nixos.org/nixpkgs/manual/ Руководство по Nixpkgs]
* [https://nixos.org/hydra/manual/ Руководство Hydra]

Основные категории страниц:
* [[:{{ns:14}}:Software|Программное обеспечение]]
* [[:{{ns:14}}:Hardware|Аппаратное обеспечение]]
* [[:{{ns:14}}:Desktop|Desktop]] - настройка для ПК
* [[:{{ns:14}}:Server|Server]] - настройка для Сервера
* [[:{{ns:14}}:Community|Community]] - люди, общение, работа над NixOS

См. также:
* [[FAQ|Часто задаваемые вопросы]]
* [[Nix vs. Linux Standard Base|Nix против стандартной базы Linux]]
* [[Terms and Definitions in Nix Project|Термины и определения в Nix Project]]
* [[Cheatsheet|Cheatsheet]]
* [[Ubuntu vs. NixOS|Сравнение между Ubuntu и NixOS]]
}}

{{home:box|wikipages|Служебные страницы|3=<ul>
<li><span class="plainlinks">[{{fullurl:Special:SpecialPages}} Overview of special pages]</span></li>
<li><span class="plainlinks">[{{fullurl:Special:AllPages|hideredirects=1}} Все страницы на {{SERVERNAME}}]</span></li>
<li>[[Special:Categories|Все категории на {{SERVERNAME}}]]</li>
<li>[{{fullurl:Special:RecentChanges|hidebots=1&reviewStatus=unpatrolled}} Непроверенные изменения на {{SERVERNAME}}]</li>
</ul>}}
</div>
<div class="col-md-5">
{{home:box|get-in-touch|icon=dialog-hi|Связь|
<b>С сообществом</b>
* [https://nixos.org/ Официальный сайт NixOS]
* [https://nixos.org/community/#governance-teams Команда разработчиков]
* [[Nix Community|Обзор сообщества]]
* [[Get In Touch|Чаты и форумы]]
* [[Support|Получить поддержку]]
* [[Get In Touch#Events|События]]

<b> О Wiki</b>
* Чат Matrix для редакторов Wiki
* [[Contributing|Поучаствовать в развитии NixOs и Wiki]]
}}
{{home:box|news|Новости|{{NixOS_Wiki:News}}
[[NixOS_Wiki:News{{!}}... все новостные статьи →]]
}}
</div>
</div>

Translations:NixOS Wiki/9/ru

2025-01-16T15:32:03Z

Unabomberlive:

См. также:
* [[FAQ|Часто задаваемые вопросы]]
* [[Nix vs. Linux Standard Base|Nix против стандартной базы Linux]]
* [[Terms and Definitions in Nix Project|Термины и определения в Nix Project]]
* [[Cheatsheet|Cheatsheet]]
* [[Ubuntu vs. NixOS|Сравнение между Ubuntu и NixOS]]
}}

NixOS Wiki/ru

2025-01-16T15:31:13Z

Unabomberlive:

<languages/>
__NOTOC__
<div class="row home-panes">
<div class="col-md-7">
{{home:box|get-started|icon=clarifications|Приступаем|
Это официальная Wiki NixOS.
Она включает в себя темы, не освещённые в [https://nixos.org/nixos/manual Мануале по NixOS]: руководства пользователя NixOS, примеры конфигурации и советы по устранению неполадок.

NixOS — это операционная система на базе Linux ядра, основанная на менеджере пакетов Nix и репозитории пакетов Nixpkgs.

Новичкам в NixOS рекомендуется прочитать обзорную статью [[Nix Ecosystem|Экосистема Nix]], чтобы получить полное представление. Для более конкретного ознакомления см. :
* [[NixOS]]
* [[Nix package manager|Пакетный менеджер Nix]]
* [[Nixpkgs|Репозиторий пакетов Nixpkgs]]
* [[Overview of the Nix Language |Общее представление о Nix языке]]
Если вы хотите попробовать Nix в автономном режиме на другом дистрибутиве Linux или на Mac, ознакомьтесь с [[nix.dev]].

В экосистеме Nix существует множество дополнительных инструментов, таких как:

* [[Home Manager|Home-manager]] для управления профилем пользователя и содержимым домашнего каталога
* [[Flakes|Nix Flakes]] для управления зависимости проектов Nix

Они добавляют сложности и поначалу могут сбить с толку, и вы даже можете решить, что они вам не нужны.
Начните с простой Nix/NixOS, а Home Manager и/или Flakes интегрируйте в свою систему только после того, как вы уверенно освоите Nix/NixOS и поймете их значение.}}

{{home:box|hosting|icon=cloud|Установка NixOS|

* На Персональном Компьютере, с [[NixOS_as_a_desktop/ru|NixOS на ПК]]
* На ARM, с [[NixOS on ARM]]
* В облаке, с помощью [[NixOS friendly hosters]]
}}

{{home:box|doctopics|icon=manual|Разделы документации|
Первым пунктом должны быть [[Resources]], который служит шлюзом к наиболее важной документации. Некоторые основные моменты приведены ниже.

Основные справочные материалы:
* [https://nixos.org/nixos/manual/ Руководство по NixOS]
* [https://nixos.org/nix/manual/ Руководство по Nix]
* [https://nixos.org/nixpkgs/manual/ Руководство по Nixpkgs]
* [https://nixos.org/hydra/manual/ Руководство Hydra]

Основные категории страниц:
* [[:{{ns:14}}:Software|Программное обеспечение]]
* [[:{{ns:14}}:Hardware|Аппаратное обеспечение]]
* [[:{{ns:14}}:Desktop|Desktop]] - настройка для ПК
* [[:{{ns:14}}:Server|Server]] - настройка для Сервера
* [[:{{ns:14}}:Community|Community]] - люди, общение, работа над NixOS

См. также:
* [[FAQ|Часто задаваемые вопросы]]
* [[Nix vs. Linux Standard Base|Nix против стандартной базы Linux]]
* [[Terms and Definitions in Nix Project|Термины и определения в Nix Project]]
* [[Cheatsheet|Cheatsheet]]
* [[Ubuntu vs NixOS|Сравнение между Ubuntu и NixOS]]
}}

{{home:box|wikipages|Служебные страницы|3=<ul>
<li><span class="plainlinks">[{{fullurl:Special:SpecialPages}} Overview of special pages]</span></li>
<li><span class="plainlinks">[{{fullurl:Special:AllPages|hideredirects=1}} Все страницы на {{SERVERNAME}}]</span></li>
<li>[[Special:Categories|Все категории на {{SERVERNAME}}]]</li>
<li>[{{fullurl:Special:RecentChanges|hidebots=1&reviewStatus=unpatrolled}} Непроверенные изменения на {{SERVERNAME}}]</li>
</ul>}}
</div>
<div class="col-md-5">
{{home:box|get-in-touch|icon=dialog-hi|Связь|
<b>С сообществом</b>
* [https://nixos.org/ Официальный сайт NixOS]
* [https://nixos.org/community/#governance-teams Команда разработчиков]
* [[Nix Community|Обзор сообщества]]
* [[Get In Touch|Чаты и форумы]]
* [[Support|Получить поддержку]]
* [[Get In Touch#Events|События]]

<b> О Wiki</b>
* Чат Matrix для редакторов Wiki
* [[Contributing|Поучаствовать в развитии NixOs и Wiki]]
}}
{{home:box|news|Новости|{{NixOS_Wiki:News}}
[[NixOS_Wiki:News{{!}}... все новостные статьи →]]
}}
</div>
</div>

Translations:NixOS Wiki/9/ru

2025-01-16T15:31:13Z

Unabomberlive:

См. также:
* [[FAQ|Часто задаваемые вопросы]]
* [[Nix vs. Linux Standard Base|Nix против стандартной базы Linux]]
* [[Terms and Definitions in Nix Project|Термины и определения в Nix Project]]
* [[Cheatsheet|Cheatsheet]]
* [[Ubuntu vs NixOS|Сравнение между Ubuntu и NixOS]]
}}

Chromium

2025-01-10T20:48:18Z

Unabomberlive: /* Accelerated video playback */

== Installation ==
=== NixOS ===
Add {{nixos:package|chromium}} to {{NixOS Manual|name=systemPackages|anchor=#sec-package-management}}.

== Accelerated video playback ==

Make sure [[Accelerated Video Playback]] is setup on the system properly. Check {{ic|chrome://gpu}} to see if Chromium has enabled hardware acceleration.

If accelerated video playback is not working, check relevant flags at {{ic|chrome://flags}}, or enable them using the cli:
{{file|/etc/nixos/configuration.nix|nix|<nowiki>
{
environment.systemPackages = with pkgs; [
(chromium.override {
commandLineArgs = [
"--enable-features=AcceleratedVideoEncoder"
"--ignore-gpu-blocklist"
"--enable-zero-copy"
];
})
];
}
</nowiki>}}

In some cases, {{ic|chrome://gpu}} will show Video Decode as enabled, but Video Acceleration Information as blank, with {{ic|chrome://media-internals}} using FFmpeg Video Decoder (software decoding). If this happens, try to enable the following features:
{{file|/etc/nixos/configuration.nix|nix|<nowiki>
{
environment.systemPackages = with pkgs; [
(chromium.override {
commandLineArgs = [
"--enable-features=AcceleratedVideoEncoder,VaapiOnNvidiaGPUs,VaapiIgnoreDriverChecks,Vulkan,DefaultANGLEVulkan,VulkanFromANGLE"
"--enable-features=VaapiIgnoreDriverChecks,VaapiVideoDecoder,PlatformHEVCDecoderSupport"
"--enable-features=UseMultiPlaneFormatForHardwareVideo"
"--ignore-gpu-blocklist"
"--enable-zero-copy"
];
})
];
}
</nowiki>}}

== Enabling native Wayland support ==

You can turn on native Wayland support in all chrome and most electron apps by setting an environment variable: <code>environment.sessionVariables.NIXOS_OZONE_WL = "1"</code>.

== Enabling DRM (Widevine support) ==
By default, {{nixos:package|chromium}} does not support playing DRM protected media. However, there is a build time flag to include the unfree Widevine blob from nixpkgs:
{{file|/etc/nixos/configuration.nix|nix|<nowiki>
{
environment.systemPackages = with pkgs; [
(chromium.override { enableWideVine = true; })
];
}
</nowiki>}}

[[Category:Applications]]
[[Category:Web Browser]]

Chromium

2025-01-10T20:47:08Z

Unabomberlive: /* Accelerated video playback */ New chromium acceleration flags

== Installation ==
=== NixOS ===
Add {{nixos:package|chromium}} to {{NixOS Manual|name=systemPackages|anchor=#sec-package-management}}.

== Accelerated video playback ==

Make sure [[Accelerated Video Playback]] is setup on the system properly. Check {{ic|chrome://gpu}} to see if Chromium has enabled hardware acceleration.

If accelerated video playback is not working, check relevant flags at {{ic|chrome://flags}}, or enable them using the cli:
{{file|/etc/nixos/configuration.nix|nix|<nowiki>
{
environment.systemPackages = with pkgs; [
(chromium.override {
commandLineArgs = [
"--enable-features=AcceleratedVideoEncoder"
"--ignore-gpu-blocklist"
"--enable-zero-copy"
];
})
];
}
</nowiki>}}

In some cases, {{ic|chrome://gpu}} will show Video Decode as enabled, but Video Acceleration Information as blank, with {{ic|chrome://media-internals}} using FFmpeg Video Decoder (software decoding). If this happens, try to enable the following features:
{{file|/etc/nixos/configuration.nix|nix|<nowiki>
{
environment.systemPackages = with pkgs; [
(chromium.override {
commandLineArgs = [
"--enable-features=AcceleratedVideoEncoder,VaapiOnNvidiaGPUs,VaapiIgnoreDriverChecks,Vulkan,DefaultANGLEVulkan,VulkanFromANGLE"
"--enable-features=VaapiIgnoreDriverChecks,VaapiVideoDecoder,PlatformHEVCDecoderSupport"
"--enable-features=DefaultANGLEVulkan,UseMultiPlaneFormatForHardwareVideo"
"--ignore-gpu-blocklist"
"--enable-zero-copy"
];
})
];
}
</nowiki>}}

== Enabling native Wayland support ==

You can turn on native Wayland support in all chrome and most electron apps by setting an environment variable: <code>environment.sessionVariables.NIXOS_OZONE_WL = "1"</code>.

== Enabling DRM (Widevine support) ==
By default, {{nixos:package|chromium}} does not support playing DRM protected media. However, there is a build time flag to include the unfree Widevine blob from nixpkgs:
{{file|/etc/nixos/configuration.nix|nix|<nowiki>
{
environment.systemPackages = with pkgs; [
(chromium.override { enableWideVine = true; })
];
}
</nowiki>}}

[[Category:Applications]]
[[Category:Web Browser]]

Flakes/ru

2025-01-10T20:40:21Z

Unabomberlive: Created page with "=== Входная схема ==="

<languages />
'''Nix flakes''' это [https://nixos.org/manual/nix/stable/contributing/experimental-Features.html экспериментальная особенность] которая была представлена с Nix 2.4 ([https://nixos.org/manual/nix/unstable/release-notes/rl-2.4.html см. Примечания к выпуску]).

<span id="Introduction"></span>
==== Введение ====

Nix flakes обеспечивают единую структуру для Nix-проектов, фиксируют версии зависимостей в лок-файле и делают более удобным написание воспроизводимых Nix-выражений.

* [https://nixos.org/manual/nix/unstable/command-ref/new-cli/nix3-flake.html#description flake] это файловая структура, корневая директория которой содержит спецификацию Nix в файле <code>flake.nix</code>.

* Содержимое файла <code>flake.nix</code> следует единой схеме наименования для объявления пакетов и их зависимостей на языке Nix.

Флейки вводят [https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake.html#flake-references синтаксис, похожий на URL] для указания удалённых источников.

* Чтобы упростить длинный синтаксис URL с помощью более коротких названий, [https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-registry.html флейки используют реестр] символических идентификаторов.

* Флейки также позволяют фиксировать ссылки и версии, которые затем могут быть запрошены и обновлены программно.

[https://nixos.org/manual/nix/stable/command-ref/new-cli/nix.html Экспериментальный интерфейс командной строки] принимает ссылки на флейки для выражений, которые создают, запускают и развёртывают пакеты.

<span id="Enable_flakes_temporarily"></span>
==== Временно включить поддержку Flakes ====

При использовании любой команды <code>nix</code> добавьте следующие параметры командной строки:
<syntaxhighlight lang="shell">
--experimental-features 'nix-command flakes'
</syntaxhighlight>

<span id="Enable_flakes_permanently_in_NixOS"></span>
====Включить flakes на постоянной основе в NixOS====

<div lang="en" dir="ltr" class="mw-content-ltr">
Add the following to the [[Overview_of_the_NixOS_Linux_distribution#Declarative_Configuration system configuration |NixOS configuration]]:
</div>

<syntaxHighlight lang=nix>
nix.settings.experimental-features = [ "nix-command" "flakes" ];
</syntaxHighlight>

<span id="Other_Distros,_with_Home-Manager"></span>
===== В других Дистрибутивах, с Home-Manager =====

Добавьте следующее в свою конфигурацию Home-Manager:

<syntaxhighlight lang="nix">
nix.settings.experimental-features = [ "nix-command" "flakes" ];
</syntaxhighlight>

<span id="Other_Distros,_without_Home-Manager"></span>
=====Другие Дистрибутивы, без Home-Manager=====

<div lang="en" dir="ltr" class="mw-content-ltr">
{{Note | The [https://github.com/DeterminateSystems/nix-installer Determinate Nix Installer] enables flakes by default.}}
</div>

Добавьте следующее в <code>~/.config/nix/nix.conf</code> или <code>/etc/nix/nix.conf</code>:

<syntaxHighlight lang=text>
experimental-features = nix-command flakes
</syntaxHighlight>

<span id="Basic_Usage_of_Flake"></span>
=== Основное Использование Flake ===

Прежде чем выполнять какие-либо команды nix на этом этапе, обратите внимание на два предупреждения ниже: одно для шифрования, другое для git.

<div lang="en" dir="ltr" class="mw-content-ltr">
====Encryption WARNING====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{Warning | Since contents of flake files are copied to the world-readable Nix store folder, do not put any unencrypted secrets in flake files. You should instead use a [[Comparison of secret managing schemes|secret managing scheme]].}}
</div>

<span id="Git_WARNING"></span>
==== Предупреждение Git ====

<div lang="en" dir="ltr" class="mw-content-ltr">
For flakes in git repos, only files in the working tree will be copied to the store.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Therefore, if you use <code>git</code> for your flake, ensure to <code>git add</code> any project files after you first create them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
See also https://www.tweag.io/blog/2020-05-25-flakes/
</div>

<span id="Generate_flake.nix_file"></span>
====Создание файла flake.nix====

Чтобы начать базовое использование Flakes, выполните команду flake в каталоге проекта:

<syntaxHighlight lang=text>
nix flake init
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Flake schema ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The flake.nix file is a Nix file but that has special restrictions (more on that later).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
It has 4 top-level attributes:
</div>

* <code>description</code> это строка описывающая flake.

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code>inputs</code> is an attribute set of all the dependencies of the flake. The schema is described below.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code>outputs</code> is a function of one argument that takes an attribute set of all the realized inputs, and outputs another attribute set whose schema is described below.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code>nixConfig</code> is an attribute set of values which reflect the [https://nixos.org/manual/nix/stable/command-ref/conf-file.html values given to nix.conf]. This can extend the normal behavior of a user's nix experience by adding flake-specific configuration, such as a binary cache.
</div>

<span id="Input_schema"></span>
=== Входная схема ===

<div lang="en" dir="ltr" class="mw-content-ltr">
[https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake.html#flake-inputs The nix flake inputs manual].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
[https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake.html#flake-references The nix flake references manual].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The inputs attribute defines the dependencies of the flake. For example, nixpkgs has to be defined as a dependency for a system flake in order for the system to build properly.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Nixpkgs can be defined using the following code:
</div>

<code>inputs.nixpkgs.url = "github:NixOS/nixpkgs/<branch name>";</code>

<div lang="en" dir="ltr" class="mw-content-ltr">
For any repository with its own flake.nix file, the website must also be defined. Nix knows where the nixpkgs repository is, so stating that it's on GitHub is unnecessary.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example, adding [[Hyprland]] as an input would look something like this:
</div>

<code>inputs.hyprland.url = "github:hyprwm/Hyprland";</code>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you want to make Hyprland follow the nixpkgs input to avoid having multiple versions of nixpkgs, this can be done using the following code:
</div>

<code>inputs.hyprland.inputs.nixpkgs.follows = "nixpkgs";</code>

<div lang="en" dir="ltr" class="mw-content-ltr">
Using curly brackets({}), we can shorten all of this and put it in a table. The code will look something like this:
</div>

<syntaxhighlight lang="nix">
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/<branch name>";
hyprland = {
url = "github:hyprwm/Hyprland";
inputs.nixpkgs.follows = "nixpkgs";
};
};
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Output schema ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This is described in the nix package manager [https://github.com/NixOS/nix/blob/master/src/nix/flake-check.md src/nix/flake-check.md].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the inputs are resolved, they're passed to the function `outputs` along with with `self`, which is the directory of this flake in the store. `outputs` returns the outputs of the flake, according to the following schema.
</div>

В которой:

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code><system></code> is something like "x86_64-linux", "aarch64-linux", "i686-linux", "x86_64-darwin"
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code><name></code> is an attribute name like "hello".
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code><flake></code> is a flake name like "nixpkgs".
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code><store-path></code> is a <code>/nix/store..</code> path
</div>

<syntaxHighlight lang=nix>
{ self, ... }@inputs:
{
# Executed by `nix flake check`
checks."<system>"."<name>" = derivation;
# Executed by `nix build .#<name>`
packages."<system>"."<name>" = derivation;
# Executed by `nix build .`
packages."<system>".default = derivation;
# Executed by `nix run .#<name>`
apps."<system>"."<name>" = {
type = "app";
program = "<store-path>";
};
# Executed by `nix run . -- <args?>`
apps."<system>".default = { type = "app"; program = "..."; };

# Formatter (alejandra, nixfmt or nixpkgs-fmt)
formatter."<system>" = derivation;
# Used for nixpkgs packages, also accessible via `nix build .#<name>`
legacyPackages."<system>"."<name>" = derivation;
# Overlay, consumed by other flakes
overlays."<name>" = final: prev: { };
# Default overlay
overlays.default = final: prev: { };
# Nixos module, consumed by other flakes
nixosModules."<name>" = { config, ... }: { options = {}; config = {}; };
# Default module
nixosModules.default = { config, ... }: { options = {}; config = {}; };
# Used with `nixos-rebuild switch --flake .#<hostname>`
# nixosConfigurations."<hostname>".config.system.build.toplevel must be a derivation
nixosConfigurations."<hostname>" = {};
# Used by `nix develop .#<name>`
devShells."<system>"."<name>" = derivation;
# Used by `nix develop`
devShells."<system>".default = derivation;
# Hydra build jobs
hydraJobs."<attr>"."<system>" = derivation;
# Used by `nix flake init -t <flake>#<name>`
templates."<name>" = {
path = "<store-path>";
description = "template description goes here?";
};
# Used by `nix flake init -t <flake>`
templates.default = { path = "<store-path>"; description = ""; };
}
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
You can also define additional arbitrary attributes, but these are the outputs that Nix knows about.
</div>

<span id="nix_run"></span>
==== `nix run` ====

<div lang="en" dir="ltr" class="mw-content-ltr">
When output <code>apps.<system>.myapp</code> is not defined, <code>nix run myapp</code> runs <code><packages or legacyPackages.<system>.myapp>/bin/<myapp.meta.mainProgram or myapp.pname or myapp.name (the non-version part)></code>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Using flakes with stable Nix ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
There exists the [https://github.com/edolstra/flake-compat flake-compat] library that you can use to shim <code>default.nix</code> and <code>shell.nix</code> files. It will download the inputs of the flake, pass them to the flake’s <code>outputs</code> function and return an attribute set containing <code>defaultNix</code> and <code>shellNix</code> attributes. The attributes will contain the output attribute set with an extra <code>default</code> attribute pointing to current platform’s <code>defaultPackage</code> (resp. <code>devShell</code> for <code>shellNix</code>).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Place the following into <code>default.nix</code> (for <code>shell.nix</code>, replace <code>defaultNix</code> with <code>shellNix</code>) to use the shim:
</div>

<syntaxHighlight lang=nix>
(import (
fetchTarball {
url = "https://github.com/edolstra/flake-compat/archive/12c64ca55c1014cdc1b16ed5a804aa8576601ff2.tar.gz";
sha256 = "0jm6nzb83wa6ai17ly9fzpqc40wg1viib8klq8lby54agpl213w5"; }
) {
src = ./.;
}).defaultNix
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
You can also use the lockfile to make updating the hashes easier using <code>nix flake lock --update-input flake-compat</code>. Add the following to your <code>flake.nix</code>:
</div>

<syntaxHighlight lang=nix>
inputs.flake-compat = {
url = "github:edolstra/flake-compat";
flake = false;
};
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
and add <code>flake-compat</code> to the arguments of <code>outputs</code> attribute. Then you will be able to use <code>default.nix</code> like the following:
</div>

<syntaxhighlight lang="nix">
(import (
let
lock = builtins.fromJSON (builtins.readFile ./flake.lock);
nodeName = lock.nodes.root.inputs.flake-compat;
in
fetchTarball {
url =
lock.nodes.${nodeName}.locked.url
or "https://github.com/edolstra/flake-compat/archive/${lock.nodes.${nodeName}.locked.rev}.tar.gz";
sha256 = lock.nodes.${nodeName}.locked.narHash;
}
) { src = ./.; }).defaultNix
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Accessing flakes from Nix expressions ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you want to access a flake from within a regular Nix expression on a system that has flakes enabled, you can use something like <code>(builtins.getFlake "/path/to/directory").packages.x86_64-linux.default</code>, where 'directory' is the directory that contains your <code>flake.nix</code>.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Making your evaluations pure ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Nix flakes run in pure evaluation mode, which is underdocumented. Some tips for now:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* fetchurl and fetchtar [https://github.com/NixOS/nix/blob/36c4d6f59247826dde32ad2e6b5a9471a9a1c911/src/libexpr/primops/fetchTree.cc#L201 require] a sha256 argument to be considered pure.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* builtins.currentSystem is non-hermetic and impure. This can usually be avoided by passing the system (i.e., x86_64-linux) explicitly to derivations requiring it.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Imports from channels like <code><nixpkgs></code> can be made pure by instead importing from the <code>output</code> function in <code>flake.nix</code>, where the arguments provide the store path to the flake's inputs:
</div>

<syntaxhighlight lang="nix">
outputs = { self, nixpkgs, ... }:
{
nixosConfigurations.machine = nixpkgs.lib.nixosSystem {
modules = [
"${nixpkgs}/nixos/modules/<some-module>.nix"
./machine.nix
];
};
};
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
== The nix flakes command ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The {{ic|nix flake}} subcommand is described in [https://nixos.org/manual/nix/unstable/command-ref/new-cli/nix3-flake.html command reference page of the unstable manual].
</div>

<span id="Install_packages_with_`nix_profile`"></span>
== Установка пакетов с помощью `nix-profile` ==

[https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-profile-install.html <code>nix profile install</code> в документации]

<div lang="en" dir="ltr" class="mw-content-ltr">
== Using nix flakes with NixOS ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{Ic|nixos-rebuild switch}} will read its configuration from <code>/etc/nixos/flake.nix</code> if it is present.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
A basic nixos flake.nix could look like this:
</div>

<syntaxhighlight lang="nix">
{
inputs.nixpkgs.url = github:NixOS/nixpkgs/nixos-unstable;
outputs = { self, nixpkgs }: {
# replace 'joes-desktop' with your hostname here.
nixosConfigurations.joes-desktop = nixpkgs.lib.nixosSystem {
modules = [ ./configuration.nix ];
};
};
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you want to pass on the flake inputs to external configuration files, you can use the <code>specialArgs</code> attribute:
</div>

<syntaxhighlight lang="nix">
{
inputs.nixpkgs.url = github:NixOS/nixpkgs/nixos-unstable;
inputs.home-manager.url = github:nix-community/home-manager;

outputs = { self, nixpkgs, ... }@inputs: {
nixosConfigurations.fnord = nixpkgs.lib.nixosSystem {
specialArgs = { inherit inputs; };
modules = [ ./configuration.nix ];
};
};
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
Then, you can access the flake inputs from the file <code>configuration.nix</code> like this:
</div>

<syntaxhighlight lang="nix">
{ config, lib, inputs, ... }: {
# do something with home-manager here, for instance:
imports = [ inputs.home-manager.nixosModules.default ];
...
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{Ic|nixos-rebuild}} also allows to specify different flake using the <code>--flake</code> flag (# is optional):
</div>

<syntaxhighlight lang="console">
$ sudo nixos-rebuild switch --flake .
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
By default nixos-rebuild will use the currents system hostname to lookup the right nixos configuration in <code>nixosConfigurations</code>. You can also override this by using appending it to the flake parameter:
</div>

<syntaxhighlight lang="console">
$ sudo nixos-rebuild switch --flake /etc/nixos#joes-desktop
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
To switch a remote host you can use:
</div>

<syntaxhighlight lang="bash">
$ nixos-rebuild --flake .#mymachine \
--target-host mymachine-hostname \
--build-host mymachine-hostname --fast \
switch
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{warning|Remote building seems to have an issue that's [https://github.com/NixOS/nixpkgs/issues/134952#issuecomment-1367056358 resolved by setting the <code>--fast</code> flag].}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Pinning the registry on NixOS ==
</div>

<syntaxhighlight lang="nix">
{ inputs, ... }:
{
nix.registry = {
nixpkgs.flake = inputs.nixpkgs;
};
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
To make sure the registry entry is "locked", use the following:
</div>

<syntaxHighlight lang=nix>
nix.registry = {
nixpkgs.to = {
type = "path";
path = pkgs.path;
narHash = builtins.readFile
(pkgs.runCommandLocal "get-nixpkgs-hash"
{ nativeBuildInputs = [ pkgs.nix ]; }
"nix-hash --type sha256 --sri ${pkgs.path} > $out");
};
};
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
This has the unfortunate side-effect of requiring import-from-derivation and slowing down build times, however it may greatly speed up almost every eval. Full-time flakes users may be able to just use <code>narHash = pkgs.narHash</code>.
</div>

<span id="Super_fast_nix-shell"></span>
== Супер быстрая nix-shell ==

<div lang="en" dir="ltr" class="mw-content-ltr">
A feature of the nix Flake edition is that Nix evaluations are cached.
</div>

Допустим, в вашем проекте есть файл <code>shell.nix</code>, который выглядит следующим образом:

<syntaxhighlight lang="nix">
{
pkgs ? import <nixpkgs> { },
}:
pkgs.mkShell {
packages = [ pkgs.nixfmt ];

shellHook = ''
# ...
'';
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
Running nix-shell can be a bit slow and take 1-3 seconds.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Now create a <code>flake.nix</code> file in the same repository:
</div>

<syntaxhighlight lang="nix">
{
inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";

outputs =
{ nixpkgs, ... }:
{
/*
This example assumes your system is x86_64-linux
change as neccesary
*/
devShells.x86_64-linux =
let
pkgs = nixpkgs.legacyPackages.x86_64-linux;
in
{
default = pkgs.mkShell {
packages = [ pkgs.hello ];
};
};
};
}
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
( If you're in a git repository run `git add flake.nix` so that Nix recognizes it. )
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
And finally, run <code>nix develop</code>. This is what replaces the old nix-shell invocation.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Exit and run again, this command should now be super fast.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{warning|TODO: there is an alternative version where the defaultPackage is a pkgs.buildEnv that contains all the dependencies. And then nix shell is used to open the environment.}}
</div>

<span id="Automatically_switch_nix_shells_with_nix-direnv"></span>
=== Автоматическое переключение оболочек nix с nix-direnv ===

<div lang="en" dir="ltr" class="mw-content-ltr">
You can easily switch nix shells when you cd into different projects with [https://github.com/nix-community/nix-direnv nix-direnv].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Pushing Flakes to Cachix ==
</div>

https://docs.cachix.org/pushing#flakes

<div lang="en" dir="ltr" class="mw-content-ltr">
To push ''all'' flake outputs automatically, checkout [https://github.com/srid/devour-flake#usage devour-flake].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Build specific attributes in a flake repository ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When in the repository top-level, run <code>nix build .#<attr></code>. It will look in the <code>legacyPackages</code> and <code>packages</code> output attributes for the corresponding derivation.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Eg, in nixpkgs:
</div>

<syntaxHighlight lang=console>
$ nix build .#hello
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Building flakes from a Git repo url with submodules ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As per nix 2.9.1, git submodules in package <code>src</code>'s won't get copied to the nix store, this may cause the build to fail. To workaround this, use:
</div>

<syntaxhighlight lang="console">
nix build '.?submodules=1#hello'
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
See: https://github.com/NixOS/nix/pull/5434
</div>

<span id="Importing_packages_from_multiple_nixpkgs_branches"></span>
== Импорт пакетов из нескольких веток nixpkgs ==

<div lang="en" dir="ltr" class="mw-content-ltr">
A NixOS config flake could be as follows:
</div>

<syntaxhighlight lang="nix">
{
description = "NixOS configuration with two or more channels";

inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-23.11";
nixpkgs-unstable.url = "github:NixOS/nixpkgs/nixos-unstable";
};

outputs =
{ nixpkgs, nixpkgs-unstable, ... }:
{
nixosConfigurations."<hostname>" = nixpkgs.lib.nixosSystem {
modules = [
{
nixpkgs.overlays = [
(final: prev: {
unstable = nixpkgs-unstable.legacyPackages.${prev.system};
# use this variant if unfree packages are needed:
# unstable = import nixpkgs-unstable {
# inherit system;
# config.allowUnfree = true;
# };
})
];
}
./configuration.nix
];
};
};
}
</syntaxhighlight>

<syntaxhighlight lang="nix">
# NixOS configuration.nix, can now use "pkgs.package" or "pkgs.unstable.package"
{ pkgs, ... }:
{
environment.systemPackages = [
pkgs.firefox
pkgs.unstable.chromium
];
# ...
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the variable <code>nixpkgs</code> points to the flake, you can also define <code>pkgs</code> with overlays with:
</div>

<syntaxhighlight lang="nix">
pkgs = import nixpkgs { system = "x86_64-linux"; overlays = [ /*the overlay in question*/ ]; };
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Getting ''Instant'' System Flakes Repl ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
How to get a nix repl out of your system flake:
</div>

<syntaxhighlight lang="text">
$ nix repl

nix-repl> :lf /path/to/flake
Added 18 variables.

nix-repl> nixosConfigurations.myHost.config.networking.hostName
"myHost"

</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
However, this won't be instant upon evaluation if any file changes have been done since your last configuration rebuild. Instead, if one puts:
</div>

<syntaxHighlight lang=nix>
nix.nixPath = let path = toString ./.; in [ "repl=${path}/repl.nix" "nixpkgs=${inputs.nixpkgs}" ];
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
In their system <code>flake.nix</code> configuration file, and includes the following file in their root directory flake as <code>repl.nix</code>:
</div>

<syntaxHighlight lang=nix>
let
flake = builtins.getFlake (toString ./.);
nixpkgs = import <nixpkgs> { };
in
{ inherit flake; }
// flake
// builtins
// nixpkgs
// nixpkgs.lib
// flake.nixosConfigurations
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
(Don't forget to <code>git add repl.nix && nixos-rebuild switch --flake "/etc/nixos"</code>)
Then one can run (or bind a shell alias):
</div>

<syntaxHighlight lang=bash>
source /etc/set-environment && nix repl $(echo $NIX_PATH | perl -pe 's|.*(/nix/store/.*-source/repl.nix).*|\1|')</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
This will launch a repl with access to <code>nixpkgs</code>, <code>lib</code>, and the <code>flake</code> options in a split of a second.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
An alternative approach to the above shell alias is omitting <code>repl</code> from <code>nix.nixPath</code> and creating a shell script:
</div>

<syntaxHighlight lang=nix>
nix.nixPath = [ "nixpkgs=${inputs.nixpkgs}" ];
environment.systemPackages = let
repl_path = toString ./.;
my-nix-fast-repl = pkgs.writeShellScriptBin "my-nix-fast-repl" ''
source /etc/set-environment
nix repl "${repl_path}/repl.nix" "$@"
'';
in [
my-nix-fast-repl
];
</syntaxHighlight>

<span id="Enable_unfree_software"></span>
== Включить несвободное ПО ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Refer to [[Unfree software|Unfree Software]].
</div>

<span id="Development_tricks"></span>
== Трюки для разработки ==

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Build a package added in a PR ===
</div>

<syntaxHighlight>
nix build github:nixos/nixpkgs?ref=pull/<PR_NUMBER>/head#<PACKAGE>
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
this allows building a package that has not yet been added to nixpkgs.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
note that this will download a full source tarball of nixpkgs. if you already have a local clone, using that may be faster due to delta compression:
</div>

<syntaxHighlight>
git fetch upstream pull/<PR_NUMBER>/head && git checkout FETCH_HEAD && nix build .#PACKAGE
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
this allows building a package that has not yet been added to nixpkgs.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== How to add a file locally in git but not include it in commits ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When a git folder exists, flake will only copy files added in git to maximize reproducibility (this way if you forgot to add a local file in your repo, you will directly get an error when you try to compile it). However, for development purpose you may want to create an alternative flake file, for instance containing configuration for your preferred editors as described [https://discourse.nixos.org/t/local-personal-development-tools-with-flakes/22714/8 here]… of course without committing this file since it contains only your own preferred tools. You can do so by doing something like that (say for a file called <code>extra/flake.nix</code>):
</div>

<syntaxHighlight>
git add --intent-to-add extra/flake.nix
git update-index --skip-worktree --assume-unchanged extra/flake.nix
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Rapid iteration of a direct dependency ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
One common pain point with using Nix as a development environment is the need to completely rebuild dependencies and re-enter the dev shell every time they are updated. The <code>nix develop --redirect <flake> <directory></code> command allows you to provide a mutable dependency to your shell as if it were built by Nix.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Consider a situation where your executable, <code>consumexe</code>, depends on a library, <code>libdep</code>. You're trying to work on both at the same time, where changes to <code>libdep</code> are reflected in real time for <code>consumexe</code>. This workflow can be achieved like so:
</div>

<syntaxHighlight lang=bash>
cd ~/libdep-src-checkout/
nix develop # Or `nix-shell` if applicable.
export prefix="./install" # configure nix to install it here
buildPhase # build it like nix does
installPhase # install it like nix does
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
Now that you've built the dependency, <code>consumexe</code> can take it as an input. '''In another terminal''':
</div>

<syntaxHighlight lang=bash>
cd ~/consumexe-src-checkout/
nix develop --redirect libdep ~/libdep-src-checkout/install
echo $buildInputs | tr " " "\n" | grep libdep
# Output should show ~/libdep-src-checkout/ so you know it worked
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Nix warns you that your redirected flake isn't actually used as an input to the evaluated flake, try using the <code>--inputs-from .</code> flag. If all worked well you should be able to <code>buildPhase && installPhase</code> when the dependency changes and rebuild your consumer with the new version ''without'' exiting the development shell.
</div>

<span id="See_also"></span>
== См. также ==

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://nix.dev/concepts/flakes Flakes] - nix.dev
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://github.com/NixOS/rfcs/pull/49 RFC 49] (2019) - Original flakes specification
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://jade.fyi/blog/flakes-arent-real/ Flakes aren't real and can't hurt you] (Jade Lovelace, 2024)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://github.com/ryan4yin/nixos-and-flakes-book NixOS & Flakes Book](Ryan4yin, 2023) - 🛠️ ❤️ An unofficial NixOS & Flakes book for beginners.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://xeiaso.net/blog/nix-flakes-1-2022-02-21 Nix Flakes: an Introduction] (Xe Iaso, 2022)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://serokell.io/blog/practical-nix-flakes Practical Nix Flakes] (Alexander Bantyev, 2021) - Intro article on working with Nix and Flakes
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://www.tweag.io/blog/2020-05-25-flakes/ Nix Flakes, Part 1: An introduction and tutorial] (Eelco Dolstra, 2020)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://www.tweag.io/blog/2020-06-25-eval-cache/ Nix Flakes, Part 2: Evaluation caching] (Eelco Dolstra, 2020)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://www.tweag.io/blog/2020-07-31-nixos-flakes/ Nix Flakes, Part 3: Managing NixOS systems] (Eelco Dolstra, 2020)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://nixos.org/manual/nix/unstable/command-ref/new-cli/nix3-flake.html Nix flake command reference manual] - Many additional details about flakes, and their parts.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://www.youtube.com/watch?v=QXUlhnhuRX4&list=PLgknCdxP89RcGPTjngfNR9WmBgvD_xW0l Nix flakes 101: Introduction to nix flakes] (Jörg Thalheim, 2020)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://github.com/NixOS/nix/blob/master/src/nix/flake.md spec describing flake inputs in more detail]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://github.com/numtide/flake-utils flake-utils: Library to avoid some boiler-code when writing flakes]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://zimbatm.com/NixFlakes/#direnv-integration zimbat's direnv article]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://github.com/nix-community/todomvc-nix building Rust and Haskell flakes]
</div>

[[Category:Software]]
[[Category:Nix]]
[[Category:Flakes]]

Translations:Flakes/31/ru

2025-01-10T20:40:20Z

Unabomberlive: Created page with "=== Входная схема ==="

=== Входная схема ===

Flakes/ru

2025-01-10T20:39:41Z

Unabomberlive: Created page with "В которой:"

<languages />
'''Nix flakes''' это [https://nixos.org/manual/nix/stable/contributing/experimental-Features.html экспериментальная особенность] которая была представлена с Nix 2.4 ([https://nixos.org/manual/nix/unstable/release-notes/rl-2.4.html см. Примечания к выпуску]).

<span id="Introduction"></span>
==== Введение ====

Nix flakes обеспечивают единую структуру для Nix-проектов, фиксируют версии зависимостей в лок-файле и делают более удобным написание воспроизводимых Nix-выражений.

* [https://nixos.org/manual/nix/unstable/command-ref/new-cli/nix3-flake.html#description flake] это файловая структура, корневая директория которой содержит спецификацию Nix в файле <code>flake.nix</code>.

* Содержимое файла <code>flake.nix</code> следует единой схеме наименования для объявления пакетов и их зависимостей на языке Nix.

Флейки вводят [https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake.html#flake-references синтаксис, похожий на URL] для указания удалённых источников.

* Чтобы упростить длинный синтаксис URL с помощью более коротких названий, [https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-registry.html флейки используют реестр] символических идентификаторов.

* Флейки также позволяют фиксировать ссылки и версии, которые затем могут быть запрошены и обновлены программно.

[https://nixos.org/manual/nix/stable/command-ref/new-cli/nix.html Экспериментальный интерфейс командной строки] принимает ссылки на флейки для выражений, которые создают, запускают и развёртывают пакеты.

<span id="Enable_flakes_temporarily"></span>
==== Временно включить поддержку Flakes ====

При использовании любой команды <code>nix</code> добавьте следующие параметры командной строки:
<syntaxhighlight lang="shell">
--experimental-features 'nix-command flakes'
</syntaxhighlight>

<span id="Enable_flakes_permanently_in_NixOS"></span>
====Включить flakes на постоянной основе в NixOS====

<div lang="en" dir="ltr" class="mw-content-ltr">
Add the following to the [[Overview_of_the_NixOS_Linux_distribution#Declarative_Configuration system configuration |NixOS configuration]]:
</div>

<syntaxHighlight lang=nix>
nix.settings.experimental-features = [ "nix-command" "flakes" ];
</syntaxHighlight>

<span id="Other_Distros,_with_Home-Manager"></span>
===== В других Дистрибутивах, с Home-Manager =====

Добавьте следующее в свою конфигурацию Home-Manager:

<syntaxhighlight lang="nix">
nix.settings.experimental-features = [ "nix-command" "flakes" ];
</syntaxhighlight>

<span id="Other_Distros,_without_Home-Manager"></span>
=====Другие Дистрибутивы, без Home-Manager=====

<div lang="en" dir="ltr" class="mw-content-ltr">
{{Note | The [https://github.com/DeterminateSystems/nix-installer Determinate Nix Installer] enables flakes by default.}}
</div>

Добавьте следующее в <code>~/.config/nix/nix.conf</code> или <code>/etc/nix/nix.conf</code>:

<syntaxHighlight lang=text>
experimental-features = nix-command flakes
</syntaxHighlight>

<span id="Basic_Usage_of_Flake"></span>
=== Основное Использование Flake ===

Прежде чем выполнять какие-либо команды nix на этом этапе, обратите внимание на два предупреждения ниже: одно для шифрования, другое для git.

<div lang="en" dir="ltr" class="mw-content-ltr">
====Encryption WARNING====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{Warning | Since contents of flake files are copied to the world-readable Nix store folder, do not put any unencrypted secrets in flake files. You should instead use a [[Comparison of secret managing schemes|secret managing scheme]].}}
</div>

<span id="Git_WARNING"></span>
==== Предупреждение Git ====

<div lang="en" dir="ltr" class="mw-content-ltr">
For flakes in git repos, only files in the working tree will be copied to the store.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Therefore, if you use <code>git</code> for your flake, ensure to <code>git add</code> any project files after you first create them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
See also https://www.tweag.io/blog/2020-05-25-flakes/
</div>

<span id="Generate_flake.nix_file"></span>
====Создание файла flake.nix====

Чтобы начать базовое использование Flakes, выполните команду flake в каталоге проекта:

<syntaxHighlight lang=text>
nix flake init
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Flake schema ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The flake.nix file is a Nix file but that has special restrictions (more on that later).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
It has 4 top-level attributes:
</div>

* <code>description</code> это строка описывающая flake.

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code>inputs</code> is an attribute set of all the dependencies of the flake. The schema is described below.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code>outputs</code> is a function of one argument that takes an attribute set of all the realized inputs, and outputs another attribute set whose schema is described below.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code>nixConfig</code> is an attribute set of values which reflect the [https://nixos.org/manual/nix/stable/command-ref/conf-file.html values given to nix.conf]. This can extend the normal behavior of a user's nix experience by adding flake-specific configuration, such as a binary cache.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Input schema ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
[https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake.html#flake-inputs The nix flake inputs manual].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
[https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake.html#flake-references The nix flake references manual].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The inputs attribute defines the dependencies of the flake. For example, nixpkgs has to be defined as a dependency for a system flake in order for the system to build properly.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Nixpkgs can be defined using the following code:
</div>

<code>inputs.nixpkgs.url = "github:NixOS/nixpkgs/<branch name>";</code>

<div lang="en" dir="ltr" class="mw-content-ltr">
For any repository with its own flake.nix file, the website must also be defined. Nix knows where the nixpkgs repository is, so stating that it's on GitHub is unnecessary.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example, adding [[Hyprland]] as an input would look something like this:
</div>

<code>inputs.hyprland.url = "github:hyprwm/Hyprland";</code>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you want to make Hyprland follow the nixpkgs input to avoid having multiple versions of nixpkgs, this can be done using the following code:
</div>

<code>inputs.hyprland.inputs.nixpkgs.follows = "nixpkgs";</code>

<div lang="en" dir="ltr" class="mw-content-ltr">
Using curly brackets({}), we can shorten all of this and put it in a table. The code will look something like this:
</div>

<syntaxhighlight lang="nix">
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/<branch name>";
hyprland = {
url = "github:hyprwm/Hyprland";
inputs.nixpkgs.follows = "nixpkgs";
};
};
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Output schema ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This is described in the nix package manager [https://github.com/NixOS/nix/blob/master/src/nix/flake-check.md src/nix/flake-check.md].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the inputs are resolved, they're passed to the function `outputs` along with with `self`, which is the directory of this flake in the store. `outputs` returns the outputs of the flake, according to the following schema.
</div>

В которой:

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code><system></code> is something like "x86_64-linux", "aarch64-linux", "i686-linux", "x86_64-darwin"
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code><name></code> is an attribute name like "hello".
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code><flake></code> is a flake name like "nixpkgs".
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code><store-path></code> is a <code>/nix/store..</code> path
</div>

<syntaxHighlight lang=nix>
{ self, ... }@inputs:
{
# Executed by `nix flake check`
checks."<system>"."<name>" = derivation;
# Executed by `nix build .#<name>`
packages."<system>"."<name>" = derivation;
# Executed by `nix build .`
packages."<system>".default = derivation;
# Executed by `nix run .#<name>`
apps."<system>"."<name>" = {
type = "app";
program = "<store-path>";
};
# Executed by `nix run . -- <args?>`
apps."<system>".default = { type = "app"; program = "..."; };

# Formatter (alejandra, nixfmt or nixpkgs-fmt)
formatter."<system>" = derivation;
# Used for nixpkgs packages, also accessible via `nix build .#<name>`
legacyPackages."<system>"."<name>" = derivation;
# Overlay, consumed by other flakes
overlays."<name>" = final: prev: { };
# Default overlay
overlays.default = final: prev: { };
# Nixos module, consumed by other flakes
nixosModules."<name>" = { config, ... }: { options = {}; config = {}; };
# Default module
nixosModules.default = { config, ... }: { options = {}; config = {}; };
# Used with `nixos-rebuild switch --flake .#<hostname>`
# nixosConfigurations."<hostname>".config.system.build.toplevel must be a derivation
nixosConfigurations."<hostname>" = {};
# Used by `nix develop .#<name>`
devShells."<system>"."<name>" = derivation;
# Used by `nix develop`
devShells."<system>".default = derivation;
# Hydra build jobs
hydraJobs."<attr>"."<system>" = derivation;
# Used by `nix flake init -t <flake>#<name>`
templates."<name>" = {
path = "<store-path>";
description = "template description goes here?";
};
# Used by `nix flake init -t <flake>`
templates.default = { path = "<store-path>"; description = ""; };
}
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
You can also define additional arbitrary attributes, but these are the outputs that Nix knows about.
</div>

<span id="nix_run"></span>
==== `nix run` ====

<div lang="en" dir="ltr" class="mw-content-ltr">
When output <code>apps.<system>.myapp</code> is not defined, <code>nix run myapp</code> runs <code><packages or legacyPackages.<system>.myapp>/bin/<myapp.meta.mainProgram or myapp.pname or myapp.name (the non-version part)></code>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Using flakes with stable Nix ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
There exists the [https://github.com/edolstra/flake-compat flake-compat] library that you can use to shim <code>default.nix</code> and <code>shell.nix</code> files. It will download the inputs of the flake, pass them to the flake’s <code>outputs</code> function and return an attribute set containing <code>defaultNix</code> and <code>shellNix</code> attributes. The attributes will contain the output attribute set with an extra <code>default</code> attribute pointing to current platform’s <code>defaultPackage</code> (resp. <code>devShell</code> for <code>shellNix</code>).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Place the following into <code>default.nix</code> (for <code>shell.nix</code>, replace <code>defaultNix</code> with <code>shellNix</code>) to use the shim:
</div>

<syntaxHighlight lang=nix>
(import (
fetchTarball {
url = "https://github.com/edolstra/flake-compat/archive/12c64ca55c1014cdc1b16ed5a804aa8576601ff2.tar.gz";
sha256 = "0jm6nzb83wa6ai17ly9fzpqc40wg1viib8klq8lby54agpl213w5"; }
) {
src = ./.;
}).defaultNix
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
You can also use the lockfile to make updating the hashes easier using <code>nix flake lock --update-input flake-compat</code>. Add the following to your <code>flake.nix</code>:
</div>

<syntaxHighlight lang=nix>
inputs.flake-compat = {
url = "github:edolstra/flake-compat";
flake = false;
};
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
and add <code>flake-compat</code> to the arguments of <code>outputs</code> attribute. Then you will be able to use <code>default.nix</code> like the following:
</div>

<syntaxhighlight lang="nix">
(import (
let
lock = builtins.fromJSON (builtins.readFile ./flake.lock);
nodeName = lock.nodes.root.inputs.flake-compat;
in
fetchTarball {
url =
lock.nodes.${nodeName}.locked.url
or "https://github.com/edolstra/flake-compat/archive/${lock.nodes.${nodeName}.locked.rev}.tar.gz";
sha256 = lock.nodes.${nodeName}.locked.narHash;
}
) { src = ./.; }).defaultNix
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Accessing flakes from Nix expressions ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you want to access a flake from within a regular Nix expression on a system that has flakes enabled, you can use something like <code>(builtins.getFlake "/path/to/directory").packages.x86_64-linux.default</code>, where 'directory' is the directory that contains your <code>flake.nix</code>.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Making your evaluations pure ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Nix flakes run in pure evaluation mode, which is underdocumented. Some tips for now:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* fetchurl and fetchtar [https://github.com/NixOS/nix/blob/36c4d6f59247826dde32ad2e6b5a9471a9a1c911/src/libexpr/primops/fetchTree.cc#L201 require] a sha256 argument to be considered pure.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* builtins.currentSystem is non-hermetic and impure. This can usually be avoided by passing the system (i.e., x86_64-linux) explicitly to derivations requiring it.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Imports from channels like <code><nixpkgs></code> can be made pure by instead importing from the <code>output</code> function in <code>flake.nix</code>, where the arguments provide the store path to the flake's inputs:
</div>

<syntaxhighlight lang="nix">
outputs = { self, nixpkgs, ... }:
{
nixosConfigurations.machine = nixpkgs.lib.nixosSystem {
modules = [
"${nixpkgs}/nixos/modules/<some-module>.nix"
./machine.nix
];
};
};
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
== The nix flakes command ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The {{ic|nix flake}} subcommand is described in [https://nixos.org/manual/nix/unstable/command-ref/new-cli/nix3-flake.html command reference page of the unstable manual].
</div>

<span id="Install_packages_with_`nix_profile`"></span>
== Установка пакетов с помощью `nix-profile` ==

[https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-profile-install.html <code>nix profile install</code> в документации]

<div lang="en" dir="ltr" class="mw-content-ltr">
== Using nix flakes with NixOS ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{Ic|nixos-rebuild switch}} will read its configuration from <code>/etc/nixos/flake.nix</code> if it is present.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
A basic nixos flake.nix could look like this:
</div>

<syntaxhighlight lang="nix">
{
inputs.nixpkgs.url = github:NixOS/nixpkgs/nixos-unstable;
outputs = { self, nixpkgs }: {
# replace 'joes-desktop' with your hostname here.
nixosConfigurations.joes-desktop = nixpkgs.lib.nixosSystem {
modules = [ ./configuration.nix ];
};
};
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you want to pass on the flake inputs to external configuration files, you can use the <code>specialArgs</code> attribute:
</div>

<syntaxhighlight lang="nix">
{
inputs.nixpkgs.url = github:NixOS/nixpkgs/nixos-unstable;
inputs.home-manager.url = github:nix-community/home-manager;

outputs = { self, nixpkgs, ... }@inputs: {
nixosConfigurations.fnord = nixpkgs.lib.nixosSystem {
specialArgs = { inherit inputs; };
modules = [ ./configuration.nix ];
};
};
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
Then, you can access the flake inputs from the file <code>configuration.nix</code> like this:
</div>

<syntaxhighlight lang="nix">
{ config, lib, inputs, ... }: {
# do something with home-manager here, for instance:
imports = [ inputs.home-manager.nixosModules.default ];
...
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{Ic|nixos-rebuild}} also allows to specify different flake using the <code>--flake</code> flag (# is optional):
</div>

<syntaxhighlight lang="console">
$ sudo nixos-rebuild switch --flake .
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
By default nixos-rebuild will use the currents system hostname to lookup the right nixos configuration in <code>nixosConfigurations</code>. You can also override this by using appending it to the flake parameter:
</div>

<syntaxhighlight lang="console">
$ sudo nixos-rebuild switch --flake /etc/nixos#joes-desktop
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
To switch a remote host you can use:
</div>

<syntaxhighlight lang="bash">
$ nixos-rebuild --flake .#mymachine \
--target-host mymachine-hostname \
--build-host mymachine-hostname --fast \
switch
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{warning|Remote building seems to have an issue that's [https://github.com/NixOS/nixpkgs/issues/134952#issuecomment-1367056358 resolved by setting the <code>--fast</code> flag].}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Pinning the registry on NixOS ==
</div>

<syntaxhighlight lang="nix">
{ inputs, ... }:
{
nix.registry = {
nixpkgs.flake = inputs.nixpkgs;
};
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
To make sure the registry entry is "locked", use the following:
</div>

<syntaxHighlight lang=nix>
nix.registry = {
nixpkgs.to = {
type = "path";
path = pkgs.path;
narHash = builtins.readFile
(pkgs.runCommandLocal "get-nixpkgs-hash"
{ nativeBuildInputs = [ pkgs.nix ]; }
"nix-hash --type sha256 --sri ${pkgs.path} > $out");
};
};
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
This has the unfortunate side-effect of requiring import-from-derivation and slowing down build times, however it may greatly speed up almost every eval. Full-time flakes users may be able to just use <code>narHash = pkgs.narHash</code>.
</div>

<span id="Super_fast_nix-shell"></span>
== Супер быстрая nix-shell ==

<div lang="en" dir="ltr" class="mw-content-ltr">
A feature of the nix Flake edition is that Nix evaluations are cached.
</div>

Допустим, в вашем проекте есть файл <code>shell.nix</code>, который выглядит следующим образом:

<syntaxhighlight lang="nix">
{
pkgs ? import <nixpkgs> { },
}:
pkgs.mkShell {
packages = [ pkgs.nixfmt ];

shellHook = ''
# ...
'';
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
Running nix-shell can be a bit slow and take 1-3 seconds.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Now create a <code>flake.nix</code> file in the same repository:
</div>

<syntaxhighlight lang="nix">
{
inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";

outputs =
{ nixpkgs, ... }:
{
/*
This example assumes your system is x86_64-linux
change as neccesary
*/
devShells.x86_64-linux =
let
pkgs = nixpkgs.legacyPackages.x86_64-linux;
in
{
default = pkgs.mkShell {
packages = [ pkgs.hello ];
};
};
};
}
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
( If you're in a git repository run `git add flake.nix` so that Nix recognizes it. )
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
And finally, run <code>nix develop</code>. This is what replaces the old nix-shell invocation.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Exit and run again, this command should now be super fast.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{warning|TODO: there is an alternative version where the defaultPackage is a pkgs.buildEnv that contains all the dependencies. And then nix shell is used to open the environment.}}
</div>

<span id="Automatically_switch_nix_shells_with_nix-direnv"></span>
=== Автоматическое переключение оболочек nix с nix-direnv ===

<div lang="en" dir="ltr" class="mw-content-ltr">
You can easily switch nix shells when you cd into different projects with [https://github.com/nix-community/nix-direnv nix-direnv].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Pushing Flakes to Cachix ==
</div>

https://docs.cachix.org/pushing#flakes

<div lang="en" dir="ltr" class="mw-content-ltr">
To push ''all'' flake outputs automatically, checkout [https://github.com/srid/devour-flake#usage devour-flake].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Build specific attributes in a flake repository ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When in the repository top-level, run <code>nix build .#<attr></code>. It will look in the <code>legacyPackages</code> and <code>packages</code> output attributes for the corresponding derivation.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Eg, in nixpkgs:
</div>

<syntaxHighlight lang=console>
$ nix build .#hello
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Building flakes from a Git repo url with submodules ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As per nix 2.9.1, git submodules in package <code>src</code>'s won't get copied to the nix store, this may cause the build to fail. To workaround this, use:
</div>

<syntaxhighlight lang="console">
nix build '.?submodules=1#hello'
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
See: https://github.com/NixOS/nix/pull/5434
</div>

<span id="Importing_packages_from_multiple_nixpkgs_branches"></span>
== Импорт пакетов из нескольких веток nixpkgs ==

<div lang="en" dir="ltr" class="mw-content-ltr">
A NixOS config flake could be as follows:
</div>

<syntaxhighlight lang="nix">
{
description = "NixOS configuration with two or more channels";

inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-23.11";
nixpkgs-unstable.url = "github:NixOS/nixpkgs/nixos-unstable";
};

outputs =
{ nixpkgs, nixpkgs-unstable, ... }:
{
nixosConfigurations."<hostname>" = nixpkgs.lib.nixosSystem {
modules = [
{
nixpkgs.overlays = [
(final: prev: {
unstable = nixpkgs-unstable.legacyPackages.${prev.system};
# use this variant if unfree packages are needed:
# unstable = import nixpkgs-unstable {
# inherit system;
# config.allowUnfree = true;
# };
})
];
}
./configuration.nix
];
};
};
}
</syntaxhighlight>

<syntaxhighlight lang="nix">
# NixOS configuration.nix, can now use "pkgs.package" or "pkgs.unstable.package"
{ pkgs, ... }:
{
environment.systemPackages = [
pkgs.firefox
pkgs.unstable.chromium
];
# ...
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the variable <code>nixpkgs</code> points to the flake, you can also define <code>pkgs</code> with overlays with:
</div>

<syntaxhighlight lang="nix">
pkgs = import nixpkgs { system = "x86_64-linux"; overlays = [ /*the overlay in question*/ ]; };
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Getting ''Instant'' System Flakes Repl ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
How to get a nix repl out of your system flake:
</div>

<syntaxhighlight lang="text">
$ nix repl

nix-repl> :lf /path/to/flake
Added 18 variables.

nix-repl> nixosConfigurations.myHost.config.networking.hostName
"myHost"

</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
However, this won't be instant upon evaluation if any file changes have been done since your last configuration rebuild. Instead, if one puts:
</div>

<syntaxHighlight lang=nix>
nix.nixPath = let path = toString ./.; in [ "repl=${path}/repl.nix" "nixpkgs=${inputs.nixpkgs}" ];
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
In their system <code>flake.nix</code> configuration file, and includes the following file in their root directory flake as <code>repl.nix</code>:
</div>

<syntaxHighlight lang=nix>
let
flake = builtins.getFlake (toString ./.);
nixpkgs = import <nixpkgs> { };
in
{ inherit flake; }
// flake
// builtins
// nixpkgs
// nixpkgs.lib
// flake.nixosConfigurations
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
(Don't forget to <code>git add repl.nix && nixos-rebuild switch --flake "/etc/nixos"</code>)
Then one can run (or bind a shell alias):
</div>

<syntaxHighlight lang=bash>
source /etc/set-environment && nix repl $(echo $NIX_PATH | perl -pe 's|.*(/nix/store/.*-source/repl.nix).*|\1|')</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
This will launch a repl with access to <code>nixpkgs</code>, <code>lib</code>, and the <code>flake</code> options in a split of a second.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
An alternative approach to the above shell alias is omitting <code>repl</code> from <code>nix.nixPath</code> and creating a shell script:
</div>

<syntaxHighlight lang=nix>
nix.nixPath = [ "nixpkgs=${inputs.nixpkgs}" ];
environment.systemPackages = let
repl_path = toString ./.;
my-nix-fast-repl = pkgs.writeShellScriptBin "my-nix-fast-repl" ''
source /etc/set-environment
nix repl "${repl_path}/repl.nix" "$@"
'';
in [
my-nix-fast-repl
];
</syntaxHighlight>

<span id="Enable_unfree_software"></span>
== Включить несвободное ПО ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Refer to [[Unfree software|Unfree Software]].
</div>

<span id="Development_tricks"></span>
== Трюки для разработки ==

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Build a package added in a PR ===
</div>

<syntaxHighlight>
nix build github:nixos/nixpkgs?ref=pull/<PR_NUMBER>/head#<PACKAGE>
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
this allows building a package that has not yet been added to nixpkgs.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
note that this will download a full source tarball of nixpkgs. if you already have a local clone, using that may be faster due to delta compression:
</div>

<syntaxHighlight>
git fetch upstream pull/<PR_NUMBER>/head && git checkout FETCH_HEAD && nix build .#PACKAGE
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
this allows building a package that has not yet been added to nixpkgs.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== How to add a file locally in git but not include it in commits ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When a git folder exists, flake will only copy files added in git to maximize reproducibility (this way if you forgot to add a local file in your repo, you will directly get an error when you try to compile it). However, for development purpose you may want to create an alternative flake file, for instance containing configuration for your preferred editors as described [https://discourse.nixos.org/t/local-personal-development-tools-with-flakes/22714/8 here]… of course without committing this file since it contains only your own preferred tools. You can do so by doing something like that (say for a file called <code>extra/flake.nix</code>):
</div>

<syntaxHighlight>
git add --intent-to-add extra/flake.nix
git update-index --skip-worktree --assume-unchanged extra/flake.nix
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Rapid iteration of a direct dependency ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
One common pain point with using Nix as a development environment is the need to completely rebuild dependencies and re-enter the dev shell every time they are updated. The <code>nix develop --redirect <flake> <directory></code> command allows you to provide a mutable dependency to your shell as if it were built by Nix.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Consider a situation where your executable, <code>consumexe</code>, depends on a library, <code>libdep</code>. You're trying to work on both at the same time, where changes to <code>libdep</code> are reflected in real time for <code>consumexe</code>. This workflow can be achieved like so:
</div>

<syntaxHighlight lang=bash>
cd ~/libdep-src-checkout/
nix develop # Or `nix-shell` if applicable.
export prefix="./install" # configure nix to install it here
buildPhase # build it like nix does
installPhase # install it like nix does
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
Now that you've built the dependency, <code>consumexe</code> can take it as an input. '''In another terminal''':
</div>

<syntaxHighlight lang=bash>
cd ~/consumexe-src-checkout/
nix develop --redirect libdep ~/libdep-src-checkout/install
echo $buildInputs | tr " " "\n" | grep libdep
# Output should show ~/libdep-src-checkout/ so you know it worked
</syntaxHighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Nix warns you that your redirected flake isn't actually used as an input to the evaluated flake, try using the <code>--inputs-from .</code> flag. If all worked well you should be able to <code>buildPhase && installPhase</code> when the dependency changes and rebuild your consumer with the new version ''without'' exiting the development shell.
</div>

<span id="See_also"></span>
== См. также ==

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://nix.dev/concepts/flakes Flakes] - nix.dev
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://github.com/NixOS/rfcs/pull/49 RFC 49] (2019) - Original flakes specification
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://jade.fyi/blog/flakes-arent-real/ Flakes aren't real and can't hurt you] (Jade Lovelace, 2024)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://github.com/ryan4yin/nixos-and-flakes-book NixOS & Flakes Book](Ryan4yin, 2023) - 🛠️ ❤️ An unofficial NixOS & Flakes book for beginners.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://xeiaso.net/blog/nix-flakes-1-2022-02-21 Nix Flakes: an Introduction] (Xe Iaso, 2022)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://serokell.io/blog/practical-nix-flakes Practical Nix Flakes] (Alexander Bantyev, 2021) - Intro article on working with Nix and Flakes
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://www.tweag.io/blog/2020-05-25-flakes/ Nix Flakes, Part 1: An introduction and tutorial] (Eelco Dolstra, 2020)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://www.tweag.io/blog/2020-06-25-eval-cache/ Nix Flakes, Part 2: Evaluation caching] (Eelco Dolstra, 2020)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://www.tweag.io/blog/2020-07-31-nixos-flakes/ Nix Flakes, Part 3: Managing NixOS systems] (Eelco Dolstra, 2020)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://nixos.org/manual/nix/unstable/command-ref/new-cli/nix3-flake.html Nix flake command reference manual] - Many additional details about flakes, and their parts.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://www.youtube.com/watch?v=QXUlhnhuRX4&list=PLgknCdxP89RcGPTjngfNR9WmBgvD_xW0l Nix flakes 101: Introduction to nix flakes] (Jörg Thalheim, 2020)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://github.com/NixOS/nix/blob/master/src/nix/flake.md spec describing flake inputs in more detail]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://github.com/numtide/flake-utils flake-utils: Library to avoid some boiler-code when writing flakes]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://zimbatm.com/NixFlakes/#direnv-integration zimbat's direnv article]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://github.com/nix-community/todomvc-nix building Rust and Haskell flakes]
</div>

[[Category:Software]]
[[Category:Nix]]
[[Category:Flakes]]

Translations:Flakes/44/ru

2025-01-10T20:39:40Z

Unabomberlive: Created page with "В которой:"

В которой:

VR/ru

2025-01-10T20:36:35Z

Unabomberlive: Created page with "VR"

<div lang="en" dir="ltr" class="mw-content-ltr">
== Monado ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
[https://monado.freedesktop.org/ Monado] is an open source OpenXR runtime. It offers support for a variety of hardware using its built-in drivers and can be used to run any OpenXR and, with the help of OpenComposite, most OpenVR applications.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Monado can be configured using its NixOS options since 24.05:
</div>

{{file|/etc/nixos/configuration.nix|nix|3=services.monado = {
enable = true;
defaultRuntime = true; # Register as default OpenXR runtime
};}}

<div lang="en" dir="ltr" class="mw-content-ltr">
In order to configure Monado, you might want to add additional environment variables:
</div>

{{file|/etc/nixos/configuration.nix|nix|3=systemd.user.services.monado.environment = {
STEAMVR_LH_ENABLE = "1";
XRT_COMPOSITOR_COMPUTE = "1";
};}}

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Hand Tracking ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may notice that running <code>monado-services</code> will fail due to the lack of hand tracking data. There are 2 ways to remedy this, either disable hand tracking altogether, or download the hand tracking data.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To disable hand tracking, modify the environment variable to include <code>WMR_HANDTRACKING = "0";</code>, so that it will look like this.
</div>

{{file|/etc/nixos/configuration.nix|nix|3=systemd.user.services.monado.environment = {
STEAMVR_LH_ENABLE = "1";
XRT_COMPOSITOR_COMPUTE = "1";
WMR_HANDTRACKING = "0";
};}}

<div lang="en" dir="ltr" class="mw-content-ltr">
To get hand tracking to work, you require <code>git-lfs</code> to be enabled. The standard way of enabling <code>git-lfs</code> is through the configuration below
</div>

{{file|/etc/nixos/configuration.nix|nix|3=programs.git = {
enable = true;
lfs.enable = true;
};}}

<div lang="en" dir="ltr" class="mw-content-ltr">
After making sure <code>git-lfs</code> is enabled, run these commands and restart <code>monado-service</code>
</div>

{{Commands|
$ mkdir -p ~/.local/share/monado
$ cd ~/.local/share/monado
$ git clone https://gitlab.freedesktop.org/monado/utilities/hand-tracking-models
}}

<div lang="en" dir="ltr" class="mw-content-ltr">
For further information about available environment variables and tweaks, read the [https://lvra.gitlab.io/docs/fossvr/monado/ Linux VR Adventures wiki] and the [https://monado.freedesktop.org/getting-started.html#environment-variables Monado documentation about environment variables]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== OpenComposite ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
[https://gitlab.com/znixian/OpenOVR OpenComposite] is a compatibility layer for running OpenVR applications on an OpenXR runtime like Monado. It is comparable to tools like DXVK or vkd3d, but for translating OpenVR calls to OpenXR.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
In order to run OpenVR games on anything other than SteamVR, you need to configure the OpenVR runtime path defined in <code>~/.config/openvr/openvrpaths.vrpath</code>. A reliable way to do this is to use [[Home Manager]] to create this file.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{Warning|Older versions of Proton will always query the current OpenVR and OpenXR runtime. If you use OpenComposite, and it fails to initialize an OpenXR context, Proton will fail to launch. A workaround is to delete the ~/.config/openvr/openvrpaths.vrpath file and then retry launching the game.}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If this file is not set to read-only, SteamVR will add its runtime path back, hence the use for Home Manager.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
An example configuration for enabling OpenComposite may look like this:
</div>

{{file|~/.config/home-manager/home.nix|nix|3=# For Monado:
xdg.configFile."openxr/1/active_runtime.json".source = "${pkgs.monado}/share/openxr/1/openxr_monado.json";

# For WiVRn:
xdg.configFile."openxr/1/active_runtime.json".source = "${pkgs.wivrn}/share/openxr/1/openxr_wivrn.json";

xdg.configFile."openvr/openvrpaths.vrpath".text = ''
{
"config" :
[
"${config.xdg.dataHome}/Steam/config"
],
"external_drivers" : null,
"jsonid" : "vrpathreg",
"log" :
[
"${config.xdg.dataHome}/Steam/logs"
],
"runtime" :
[
"${pkgs.opencomposite}/lib/opencomposite"
],
"version" : 1
}
'';}}

<div lang="en" dir="ltr" class="mw-content-ltr">
If you are planning to play any OpenVR game on Steam or OpenXR games through Proton, you will have to use OpenComposite in this manner. In most cases you also have to allow access to the socket path of your OpenXR runtime to Steam's runtime, by using the following launch options for XR applications on Steam: <code>env PRESSURE_VESSEL_FILESYSTEMS_RW=$XDG_RUNTIME_DIR/monado_comp_ipc %command%</code>. This example is for Monado, while other XR runtimes might differ.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== WiVRn ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
WiVRn is an OpenXR streaming application built around Monado. It wirelessly connects a standalone VR headset to a Linux computer. If your headset is not wireless, look at [[VR#Monado|Monado]] instead.
Example usage of the WiVRn module:
</div>

{{File|/etc/nixos/configuration.nix|nix|3=services.wivrn = {
enable = true;
openFirewall = true;

# Write information to /etc/xdg/openxr/1/active_runtime.json, VR applications
# will automatically read this and work with WiVRn (Note: This does not currently
# apply for games run in Valve's Proton)
defaultRuntime = true;

# Run WiVRn as a systemd service on startup
autoStart = true;

# Config for WiVRn (https://github.com/WiVRn/WiVRn/blob/master/docs/configuration.md)
config = {
enable = true;
json = {
# 1.0x foveation scaling
scale = 1.0;
# 100 Mb/s
bitrate = 100000000;
encoders = [
{
encoder = "vaapi";
codec = "h265";
# 1.0 x 1.0 scaling
width = 1.0;
height = 1.0;
offset_x = 0.0;
offset_y = 0.0;
}
];
};
};
};}}

<div lang="en" dir="ltr" class="mw-content-ltr">
Like Monado, you will also have to add the launch argument for WiVRn to allow access to the socket: <code>PRESSURE_VESSEL_FILESYSTEMS_RW=$XDG_RUNTIME_DIR/wivrn/comp_ipc %command%</code>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Envision ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Envision is an orchestrator for the FOSS VR stack. It handles the building and configuration of Monado, WiVRn, OpenComposite, and other utilities of the FOSS VR stack such as the Lighthouse driver, OpenHMD, Survive, and WMR. You can enable it with the Envision module:
</div>

{{File|/etc/nixos/configuration.nix|nix|3=programs.envision = {
enable = true;
openFirewall = true; # This is set true by default
};}}

<div lang="en" dir="ltr" class="mw-content-ltr">
== SteamVR ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
[https://store.steampowered.com/app/250820/SteamVR/ SteamVR] is a proprietary OpenVR runtime with compatibility for OpenXR. It is part of [[Steam]] and doesn't need any additional setup on NixOS apart from enabling Steam.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
After installing SteamVR through Steam and plugging in a SteamVR-compatible headset, SteamVR should work for the most part.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
On initial setup, SteamVR will ask for elevated permissions, to set up a file capability for one of its binaries. This is needed to allow asynchronous reprojection to work. Clients need the <code>CAP_SYS_NICE</code> capability to acquire a high-priority context, which is a requirement for asynchronous reprojection.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{Note|Steam is run in a bubblewrap-based FHS environment. This environment runs Steam in a user namespace, which prevents it from using any capabilities or setuid binaries. This means that asynchronous reprojection can not be used on NixOS, without patching the kernel to remove these restrictions completely. See this [https://github.com/NixOS/nixpkgs/issues/217119 Nixpkgs issue]}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Patching AMDGPU to allow high priority queues ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
By applying [https://github.com/Frogging-Family/community-patches/blob/a6a468420c0df18d51342ac6864ecd3f99f7011e/linux61-tkg/cap_sys_nice_begone.mypatch this patch], the AMDGPU kernel driver will ignore process privileges and allow any application to create high priority contexts.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{Warning|This removes intentional restrictions from the kernel, and it could cause scheduling issues. While it has not been reported that it does cause issues, this should be considered an unsupported configuration.}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==== Applying as a NixOS kernel patch ====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To workaround the <code>CAP_SYS_NICE</code> requirement, we can apply a kernel patch using the following NixOS configuration snippet:
</div>

{{file|/etc/nixos/configuration.nix|nix|3=boot.kernelPatches = [
{
name = "amdgpu-ignore-ctx-privileges";
patch = pkgs.fetchpatch {
name = "cap_sys_nice_begone.patch";
url = "https://github.com/Frogging-Family/community-patches/raw/master/linux61-tkg/cap_sys_nice_begone.mypatch";
hash = "sha256-Y3a0+x2xvHsfLax/uwycdJf3xLxvVfkfDVqjkxNaYEo=";
};
}
];
}}

<div lang="en" dir="ltr" class="mw-content-ltr">
It is also possible to just patch amdgpu and build it as an out-of-tree module, as described in [[Linux_kernel#Patching_a_single_In-tree_kernel_module]]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== wlx-overlay-s ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
[https://github.com/galister/wlx-overlay-s wlx-overlay-s] is a lightweight OpenXR/OpenVR overlay for Wayland and X11 desktops. It works with SteamVR as well as Monado/WiVRn natively.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==== SteamVR autostart ====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When launching wlx-overlay-s in SteamVR (or any OpenVR compositor) it will register an autostart manifest. Currently, this manifest will reference a Nix store path of wlx-overlay-s, which might get garbage collected after rebuilds of your NixOS/Nix profile. A workaround is to regularly run the following command to update the manifest's store path:{{Commands|
# Run wlx-overlay-s and replace any running instance
$ wlx-overlay-s --replace}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== See also ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://lvra.gitlab.io Linux VR Adventures Wiki]
[[Category:Video]]
[[Category:Hardware]]
[[Category:Desktop]]
[[Category:Gaming]]
</div>

Translations:VR/Page display title/ru

2025-01-10T20:36:32Z

Unabomberlive: Created page with "VR"

NixOS as a desktop/ru

2025-01-10T20:36:05Z

Unabomberlive: Created page with "==== Видеопособие ===="

<languages/>
NixOS может быть использована для разных целей. Если вы желаете использовать её как основную десктопную ОС для повседневного использования ( на реальном железе или [https://twitter.com/mitchellh/status/1346136404682625024 виртуальной машине]), то эта страница для вас. Даже если вы планируете использовать NixOS в облаке или на специально настроенных серверах, вы, возможно, хотите начать с уроков, изложенных здесь, чтобы ближе познакомиться с экосистемой Nix.

<span id="Installation"></span>
== Установка ==

<span id="Wiki_method"></span>
=== Метод Wiki ===

Если вы предпочитаете чтение, для начала посмотрите [[NixOS_Installation_Guide/ru|инструкцию по установке]]. Если же видео, пролистайте ниже до секции "Видео инструкции". Учитывайте, что для десктопной установки, вам потребуется как минимум 30 GiB места на диске, чтобы вместить рабочее окружение (например GNOME, KDE, или XFCE), браузеры (например Firefox), и другие графические утилиты (такие как VSCode), что вполне разумно для повседневного использования. Для минимальной установки, вероятно, хватит и 15 Gib.

<span id="Video_guide"></span>
=== Видео инструкции ===

Для визуальных гайдов, смотрите [[Wil T Nix Guides]](англ). [[Wil_T_Nix_Guides|второе видео]] - лаконичный гайд по установке. Это серия из 8 видео, записанных в начала 2021, также объясняет базы использования NixOS на ПК и конфигурирования по вашему вкусу.

<span id="Managing_your_configuration"></span>
== Обслуживание своей конфигурации ==

<div lang="en" dir="ltr" class="mw-content-ltr">
It is possible to manage your entire configuration using the methods documented in the [https://nixos.org/manual/nixos/stable/index.html NixOS official manual]. However, most community members who use NixOS on the desktop prefer to manage their user configurations (e.g. "dotfiles") using [[Home Manager]] (citation needed). Home Manager is a user oriented tool for declaring what you want installed and how you want it configured, and thus would be used in lieu of most settings you would otherwise put into a [https://nixos.org/manual/nixos/stable/#sec-changing-config configuration.nix] or through [[FAQ#How_can_I_manage_software_with_nix-env_like_with_configuration.nix.3F|nix-env]]
</div>

<span id="Video_guide"></span>
=== Видео инструкции ===

<div lang="en" dir="ltr" class="mw-content-ltr">
Wil T's guides are about an even mix of:
# Hands-on bootstrapping to get to being able to very capably manage your system using Home Manager, git versioning, and eventually Flakes.
# Conceptual overviews and general exposition of the Nix ecosystem, community, and available resources.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The [[Wil_T_Nix_Guides#NixOS_Installation_Guide|second video]], starting from about 27 minutes in, is also an introduction to and guide to setting up Home Manager.
</div>

<span id="Modularizing_your_configuration"></span>
== Модульная конфигурация ==

<span id="With_NixOS_Modules"></span>
=== С помощью модулей NixOS ===

<div lang="en" dir="ltr" class="mw-content-ltr">
configuration.nix is an instance of a [[NixOS modules|NixOS module]], which makes it easy to break your configuration into several files. Modules can:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Import other modules
* Declare new options
* Provide values for options (this is what most of your default configuration.nix does)
* Reference option values from other modules (via the <code>config</code> attribute passed to all modules)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As long as you declare options for any values you want to share between modules, you can divide your configuration however you like into files that get imported, directly or transitively, by your root configuration.nix file. You can also import modules from remote sources, using functions like <code>builtins.fetchTarball</code>. See the [[NixOS modules|wiki page]] or the [https://nixos.org/manual/nixos/stable/#sec-writing-modules NixOS manual] for more information.
</div>

<span id="With_Flakes"></span>
=== С помощью Flakes ===

<div lang="en" dir="ltr" class="mw-content-ltr">
If you want a more composable<sup>[citation needed]</sup> NixOS configuration setup, the still-experimental [[Flakes]] feature is causing a lot of excitement in the community. Managing flakes requires a good basic understanding and some existing hands on experience with the Nix ecosystem.
</div>

<span id="Video_guide"></span>
==== Видеопособие ====

<div lang="en" dir="ltr" class="mw-content-ltr">
Videos [[Wil_T_Nix_Guides#Intro_to_Flakes|seven]] and [[Wil_T_Nix_Guides#Moving_NixOS_System_Configuration_into_a_Flake|eight]] of Wil T's original 8-part series are a good overview of what Flakes enable and how to get started with them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Beyond initial setup ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
After you are familiar with the Nix ecosystem and have a functional desktop install of NixOS, you will likely be interested in customizations and more detailed setup.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Learn by example ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you are comfortable managing your system through a git repo using flakes, then there are many repositories you can learn from now!
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Check out [[Comparison of NixOS setups]] for a table comparing some popular choices.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
See [[Configuration Collection]] for a long list within the wiki.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Additionally, the following topic searches on Github should uncover many useful examples.
* [https://github.com/topics/nix-flake nix-flake]
* [https://github.com/topics/nixos-configuration nixos-configuration]
* [https://github.com/topics/nixos-dotfiles nixos-dotfiles]
</div>

[[Category:Desktop]]
[[Category:Guide]]

Translations:NixOS as a desktop/19/ru

2025-01-10T20:36:03Z

Unabomberlive: Created page with "==== Видеопособие ===="

==== Видеопособие ====

Fzf

2024-12-19T09:27:06Z

Unabomberlive: Home-manager integrations

{{DISPLAYTITLE:fzf}}
[https://github.com/junegunn/fzf fzf] is a general-purpose command-line fuzzy finder.

= Shell extensions =
fzf provides additional key bindings (CTRL-T, CTRL-R, and ALT-C) for shells

First install <code>fzf</code> in your profile, then use one of the following methods:

== Bash ==
=== With Home-manager ===
There is option to enable fzf bash integration
<syntaxhighlight lang="nix">
programs.fzf.enableBashIntegration = true;
</syntaxhighlight>
=== Without Home-manager ===
To enable fzf in bash add the following line to <code>$HOME/.bashrc</code>
<syntaxhighlight lang="bash">eval "$(fzf --bash)"</syntaxhighlight>

== Zsh ==
You can enable fzf in [[zsh]].
=== With Home-manager ===
There is option to enable fzf zsh integration
<syntaxhighlight lang="nix">
programs.fzf.enableZshIntegration = true;
</syntaxhighlight>
=== Without Home-manager ===
To enable fzf in bash add the following line to
<code>$HOME/.zshrc</code>
<syntaxhighlight lang="bash">
eval "$(fzf --zsh)"
</syntaxhighlight>

== Fish ==
To enable fzf in [[fish]].
=== With Home-manager ===
There is option to enable fzf fish integration
<syntaxhighlight lang="nix">
programs.fzf.enableFishIntegration = true;
</syntaxhighlight>
=== Without Home-Manager ===
To enable fzf in fish add the following line to <code>$HOME/.config/fish/functions/fish_user_key_bindings.fish</code>

<syntaxhighlight lang="fish">
fzf --fish | source
</syntaxhighlight>

= Examples =

== Search all nix packages ==

You can interactively search the list of available packages with:

<syntaxhighlight lang="bash">
nix-env -qa | fzf
</syntaxhighlight>

[[Category:Applications]]
[[Category:Shell]]

NixOS Wiki/ru

2024-11-05T11:38:48Z

Unabomberlive:

<languages/>
__NOTOC__
<div class="row home-panes">
<div class="col-md-7">
{{home:box|get-started|icon=clarifications|Приступаем|
Это официальная Wiki NixOS.
Она включает в себя темы, не освещённые в [https://nixos.org/nixos/manual Мануале по NixOS]: руководства пользователя NixOS, примеры конфигурации и советы по устранению неполадок.

NixOS - это операционная система Linux, основанная на менеджере пакетов Nix и репозитории пакетов Nixpkgs.

Новичкам в NixOS рекомендуется прочитать обзорную статью [[Nix Ecosystem|Экосистема Nix]], чтобы получить полное представление. Для более конкретного ознакомления см:
* [[NixOS]]
* [[Nix package manager]]
* Репозиторий пакетов [[Nixpkgs]]
* [[Overview of the Nix Language |Nix Language]]
Если вы хотите попробовать Nix в автономном режиме в другом дистрибутиве Linux или на Mac, сделайте первые шаги на [[nix.dev]].

В экосистеме Nix существует множество дополнительных инструментов, таких как:

* [[Home manager|Home-manager]] для управления профилем пользователя и содержимым домашнего каталога
* [[Flakes|Nix Flakes]] вместо nix-channel

Они добавляют сложности и поначалу могут сбить с толку, и вы даже можете решить, что они вам не нужны.
Начните с простой Nix/NixOS, а Home Manager и/или Flakes интегрируйте в свою систему только после того, как вы уверенно освоите Nix/NixOS и поймете их значение}}.

{{home:box|hosting|icon=cloud|Установка NixOS|

* На Персональном Компьютере, с [[NixOS as a desktop]]
* На ARM, с [[NixOS on ARM]]
* В облаке, с помощью [[NixOS friendly hosters]]
}}

{{home:box|doctopics|icon=manual|Разделы документации|
Первым пунктом должны быть [[Resources]], который служит шлюзом к наиболее важной документации. Некоторые основные моменты приведены ниже.

Основные справочные материалы:
* [https://nixos.org/nixos/manual/ Руководство по NixOS]
* [https://nixos.org/nix/manual/ Руководство по Nix]
* [https://nixos.org/nixpkgs/manual/ Руководство по Nixpkgs]
* [https://nixos.org/hydra/manual/ Руководство Hydra]

Основные категории страниц:
* [[:{{ns:14}}:Software|Программное обеспечение]]
* [[:{{ns:14}}:Hardware|Аппаратное обеспечение]]
* [[:{{ns:14}}:Desktop|Desktop]] - настройка для ПК
* [[:{{ns:14}}:Server|Server]] - настройка для Сервера
* [[:{{ns:14}}:Community|Community]] - люди, общение, работа над NixOS

<div class="mw-translate-fuzzy">
См. также:
* [[FAQ]]
* [[Nix vs. Linux Standard Base|Nix против стандартной базы Linux]]
* [[Terms and Definitions in Nix Project|Термины и определения в Nix Project]]
* [[Cheatsheet|Cheatsheet / Сравнение между Ubuntu и NixOS]]
}}
</div>

{{home:box|wikipages|Служебные страницы|3=<ul>
<li><span class="plainlinks">[{{fullurl:Special:SpecialPages}} Overview of special pages]</span></li>
<li><span class="plainlinks">[{{fullurl:Special:AllPages|hideredirects=1}} Все страницы на {{SERVERNAME}}]</span></li>
<li>[[Special:Categories|Все категории на {{SERVERNAME}}]]</li>
<li>[{{fullurl:Special:RecentChanges|hidebots=1&reviewStatus=unpatrolled}} Непроверенные изменения на {{SERVERNAME}}]</li>
</ul>}}
</div>
<div class="col-md-5">
{{home:box|get-in-touch|icon=dialog-hi|Связь|
<b>С сообществом</b>
* [https://nixos.org/ Официальный сайт NixOS]
* [[Nix Community|Обзор сообщества]]
* [[Get In Touch|Чаты и форумы]]
* [[Support|Получить поддержку]]
* [[Get In Touch#Events|События]]

<b> О Wiki</b>
* Чат Matrix для редакторов Wiki
* [[Contributing to the wiki]]
}}
{{home:box|news|Новости|{{NixOS_Wiki:News}}
[[NixOS_Wiki:News{{!}}... все новостные статьи →]]
}}
</div>
</div>

NixOS Wiki/ru

2024-11-05T11:38:39Z

Unabomberlive:

<languages/>
__NOTOC__
<div class="row home-panes">
<div class="col-md-7">
{{home:box|get-started|icon=clarifications|Приступаем|
Это официальная Wiki NixOS.
Она включает в себя темы, не освещённые в [https://nixos.org/nixos/manual Мануале по NixOS]: руководства пользователя NixOS, примеры конфигурации и советы по устранению неполадок.

NixOS - это операционная система Linux, основанная на менеджере пакетов Nix и репозитории пакетов Nixpkgs.

Новичкам в NixOS рекомендуется прочитать обзорную статью [[Nix Ecosystem|Экосистема Nix]], чтобы получить полное представление. Для более конкретного ознакомления см:
* [[NixOS]]
* [[Nix package manager]]
* Репозиторий пакетов [[Nixpkgs]]
* [[Overview of the Nix Language |Nix Language]]
Если вы хотите попробовать Nix в автономном режиме в другом дистрибутиве Linux или на Mac, сделайте первые шаги на [[nix.dev]].

В экосистеме Nix существует множество дополнительных инструментов, таких как:

* [[Home manager|Home-manager]] для управления профилем пользователя и содержимым домашнего каталога
* [[Flakes|Nix Flakes]] вместо nix-channel

Они добавляют сложности и поначалу могут сбить с толку, и вы даже можете решить, что они вам не нужны.
Начните с простой Nix/NixOS, а Home Manager и/или Flakes интегрируйте в свою систему только после того, как вы уверенно освоите Nix/NixOS и поймете их значение}}.

{{home:box|hosting|icon=cloud|Установка NixOS|

* На Персональном Компьютере, с [[NixOS as a desktop]]
* На ARM, с [[NixOS on ARM]]
* В облаке, с помощью [[NixOS friendly hosters]]
}}

{{home:box|doctopics|icon=manual|Разделы документации|
Первым пунктом должны быть [[Resources]], который служит шлюзом к наиболее важной документации. Некоторые основные моменты приведены ниже.

Основные справочные материалы:
* [https://nixos.org/nixos/manual/ Руководство по NixOS]
* [https://nixos.org/nix/manual/ Руководство по Nix]
* [https://nixos.org/nixpkgs/manual/ Руководство по Nixpkgs]
* [https://nixos.org/hydra/manual/ Руководство Hydra]

Основные категории страниц:
* [[:{{ns:14}}:Software|Программное обеспечение]]
* [[:{{ns:14}}:Hardware|Аппаратное обеспечение]]
* [[:{{ns:14}}:Desktop|Desktop]] - настройка для ПК
* [[:{{ns:14}}:Server|Server]] - настройка для Сервера
* [[:{{ns:14}}:Community|Community]] - люди, общение, работа над NixOS

<div class="mw-translate-fuzzy">
См. также:
* [[FAQ]]
* [[Nix vs. Linux Standard Base|Nix против стандартной базы Linux]]
* [[Terms and Definitions in Nix Project|Термины и определения в Nix Project]]
* [[Cheatsheet|Cheatsheet / Сравнение между Ubuntu и NixOS]]
}}
</div>

<div class="mw-translate-fuzzy">
{{home:box|wikipages|Служебные страницы|3=<ul>
<li><span class="plainlinks">[{{fullurl:Special:SpecialPages}} Overview of special pages]</span></li>
<li><span class="plainlinks">[{{fullurl:Special:AllPages|hideredirects=1}} Все страницы на {{SERVERNAME}}]</span></li>
<li>[[Special:Categories|Все категории на {{SERVERNAME}}]]</li>
<li>[{{fullurl:Special:RecentChanges|hidebots=1&reviewStatus=unpatrolled}} Непроверенные изменения на {{SERVERNAME}}]</li>
</ul>}}
</div>
<div class="col-md-5">
{{home:box|get-in-touch|icon=dialog-hi|Связь|
<b>С сообществом</b>
* [https://nixos.org/ Официальный сайт NixOS]
* [[Nix Community|Обзор сообщества]]
* [[Get In Touch|Чаты и форумы]]
* [[Support|Получить поддержку]]
* [[Get In Touch#Events|События]]
</div>

<b> О Wiki</b>
* Чат Matrix для редакторов Wiki
* [[Contributing to the wiki]]
}}
{{home:box|news|Новости|{{NixOS_Wiki:News}}
[[NixOS_Wiki:News{{!}}... все новостные статьи →]]
}}
</div>
</div>

NixOS Wiki/ru

2024-11-05T11:37:26Z

Unabomberlive:

<languages/>
__NOTOC__
<div class="row home-panes">
<div class="col-md-7">
{{home:box|get-started|icon=clarifications|Приступаем|
Это официальная Wiki NixOS.
Она включает в себя темы, не освещённые в [https://nixos.org/nixos/manual Мануале по NixOS]: руководства пользователя NixOS, примеры конфигурации и советы по устранению неполадок.

NixOS - это операционная система Linux, основанная на менеджере пакетов Nix и репозитории пакетов Nixpkgs.

<div class="mw-translate-fuzzy">
Новичкам в NixOS рекомендуется прочитать обзорную статью [[Nix Ecosystem|Экосистема Nix]], чтобы получить полное представление. Для более конкретного ознакомления см:
* [[NixOS]]
* [[Nix package manager]]
* Репозиторий пакетов [[Nixpkgs]]
* [[Overview of the Nix Language |Nix Language]]
Если вы хотите попробовать Nix в автономном режиме в другом дистрибутиве Linux или на Mac, сделайте первые шаги на [[nix.dev]].
</div>

В экосистеме Nix существует множество дополнительных инструментов, таких как:

* [[Home manager|Home-manager]] для управления профилем пользователя и содержимым домашнего каталога
* [[Flakes|Nix Flakes]] вместо nix-channel

Они добавляют сложности и поначалу могут сбить с толку, и вы даже можете решить, что они вам не нужны.
Начните с простой Nix/NixOS, а Home Manager и/или Flakes интегрируйте в свою систему только после того, как вы уверенно освоите Nix/NixOS и поймете их значение}}.

{{home:box|hosting|icon=cloud|Установка NixOS|

* На Персональном Компьютере, с [[NixOS as a desktop]]
* На ARM, с [[NixOS on ARM]]
* В облаке, с помощью [[NixOS friendly hosters]]
}}

{{home:box|doctopics|icon=manual|Разделы документации|
Первым пунктом должны быть [[Resources]], который служит шлюзом к наиболее важной документации. Некоторые основные моменты приведены ниже.

Основные справочные материалы:
* [https://nixos.org/nixos/manual/ Руководство по NixOS]
* [https://nixos.org/nix/manual/ Руководство по Nix]
* [https://nixos.org/nixpkgs/manual/ Руководство по Nixpkgs]
* [https://nixos.org/hydra/manual/ Руководство Hydra]

Основные категории страниц:
* [[:{{ns:14}}:Software|Программное обеспечение]]
* [[:{{ns:14}}:Hardware|Аппаратное обеспечение]]
* [[:{{ns:14}}:Desktop|Desktop]] - настройка для ПК
* [[:{{ns:14}}:Server|Server]] - настройка для Сервера
* [[:{{ns:14}}:Community|Community]] - люди, общение, работа над NixOS

<div class="mw-translate-fuzzy">
См. также:
* [[FAQ]]
* [[Nix vs. Linux Standard Base|Nix против стандартной базы Linux]]
* [[Terms and Definitions in Nix Project|Термины и определения в Nix Project]]
* [[Cheatsheet|Cheatsheet / Сравнение между Ubuntu и NixOS]]
}}
</div>

<div class="mw-translate-fuzzy">
{{home:box|wikipages|Служебные страницы|3=<ul>
<li><span class="plainlinks">[{{fullurl:Special:SpecialPages}} Overview of special pages]</span></li>
<li><span class="plainlinks">[{{fullurl:Special:AllPages|hideredirects=1}} Все страницы на {{SERVERNAME}}]</span></li>
<li>[[Special:Categories|Все категории на {{SERVERNAME}}]]</li>
<li>[{{fullurl:Special:RecentChanges|hidebots=1&reviewStatus=unpatrolled}} Непроверенные изменения на {{SERVERNAME}}]</li>
</ul>}}
</div>
<div class="col-md-5">
{{home:box|get-in-touch|icon=dialog-hi|Связь|
<b>С сообществом</b>
* [https://nixos.org/ Официальный сайт NixOS]
* [[Nix Community|Обзор сообщества]]
* [[Get In Touch|Чаты и форумы]]
* [[Support|Получить поддержку]]
* [[Get In Touch#Events|События]]
</div>

<b> О Wiki</b>
* Чат Matrix для редакторов Wiki
* [[Contributing to the wiki]]
}}
{{home:box|news|Новости|{{NixOS_Wiki:News}}
[[NixOS_Wiki:News{{!}}... все новостные статьи →]]
}}
</div>
</div>

Translations:NixOS Wiki/12/ru

2024-11-05T11:37:22Z

Unabomberlive:

* [[Home manager|Home-manager]] для управления профилем пользователя и содержимым домашнего каталога
* [[Flakes|Nix Flakes]] вместо nix-channel

NixOS Wiki/ru

2024-11-05T11:36:35Z

Unabomberlive:

<languages/>
__NOTOC__
<div class="row home-panes">
<div class="col-md-7">
{{home:box|get-started|icon=clarifications|Приступаем|
Это официальная Wiki NixOS.
Она включает в себя темы, не освещённые в [https://nixos.org/nixos/manual Мануале по NixOS]: руководства пользователя NixOS, примеры конфигурации и советы по устранению неполадок.

NixOS - это операционная система Linux, основанная на менеджере пакетов Nix и репозитории пакетов Nixpkgs.

<div class="mw-translate-fuzzy">
Новичкам в NixOS рекомендуется прочитать обзорную статью [[Nix Ecosystem|Экосистема Nix]], чтобы получить полное представление. Для более конкретного ознакомления см:
* [[NixOS]]
* [[Nix package manager]]
* Репозиторий пакетов [[Nixpkgs]]
* [[Overview of the Nix Language |Nix Language]]
Если вы хотите попробовать Nix в автономном режиме в другом дистрибутиве Linux или на Mac, сделайте первые шаги на [[nix.dev]].
</div>

В экосистеме Nix существует множество дополнительных инструментов, таких как:

<div class="mw-translate-fuzzy">
* Home-manager для управления профилем пользователя и содержимым домашнего каталога
* Nix Flakes вместо nix-channel
</div>

Они добавляют сложности и поначалу могут сбить с толку, и вы даже можете решить, что они вам не нужны.
Начните с простой Nix/NixOS, а Home Manager и/или Flakes интегрируйте в свою систему только после того, как вы уверенно освоите Nix/NixOS и поймете их значение}}.

{{home:box|hosting|icon=cloud|Установка NixOS|

* На Персональном Компьютере, с [[NixOS as a desktop]]
* На ARM, с [[NixOS on ARM]]
* В облаке, с помощью [[NixOS friendly hosters]]
}}

{{home:box|doctopics|icon=manual|Разделы документации|
Первым пунктом должны быть [[Resources]], который служит шлюзом к наиболее важной документации. Некоторые основные моменты приведены ниже.

Основные справочные материалы:
* [https://nixos.org/nixos/manual/ Руководство по NixOS]
* [https://nixos.org/nix/manual/ Руководство по Nix]
* [https://nixos.org/nixpkgs/manual/ Руководство по Nixpkgs]
* [https://nixos.org/hydra/manual/ Руководство Hydra]

Основные категории страниц:
* [[:{{ns:14}}:Software|Программное обеспечение]]
* [[:{{ns:14}}:Hardware|Аппаратное обеспечение]]
* [[:{{ns:14}}:Desktop|Desktop]] - настройка для ПК
* [[:{{ns:14}}:Server|Server]] - настройка для Сервера
* [[:{{ns:14}}:Community|Community]] - люди, общение, работа над NixOS

<div class="mw-translate-fuzzy">
См. также:
* [[FAQ]]
* [[Nix vs. Linux Standard Base|Nix против стандартной базы Linux]]
* [[Terms and Definitions in Nix Project|Термины и определения в Nix Project]]
* [[Cheatsheet|Cheatsheet / Сравнение между Ubuntu и NixOS]]
}}
</div>

<div class="mw-translate-fuzzy">
{{home:box|wikipages|Служебные страницы|3=<ul>
<li><span class="plainlinks">[{{fullurl:Special:SpecialPages}} Overview of special pages]</span></li>
<li><span class="plainlinks">[{{fullurl:Special:AllPages|hideredirects=1}} Все страницы на {{SERVERNAME}}]</span></li>
<li>[[Special:Categories|Все категории на {{SERVERNAME}}]]</li>
<li>[{{fullurl:Special:RecentChanges|hidebots=1&reviewStatus=unpatrolled}} Непроверенные изменения на {{SERVERNAME}}]</li>
</ul>}}
</div>
<div class="col-md-5">
{{home:box|get-in-touch|icon=dialog-hi|Связь|
<b>С сообществом</b>
* [https://nixos.org/ Официальный сайт NixOS]
* [[Nix Community|Обзор сообщества]]
* [[Get In Touch|Чаты и форумы]]
* [[Support|Получить поддержку]]
* [[Get In Touch#Events|События]]
</div>

<b> О Wiki</b>
* Чат Matrix для редакторов Wiki
* [[Contributing to the wiki]]
}}
{{home:box|news|Новости|{{NixOS_Wiki:News}}
[[NixOS_Wiki:News{{!}}... все новостные статьи →]]
}}
</div>
</div>

Hardware/System76/galp5/ru

2024-10-15T18:49:05Z

Unabomberlive: Created page with "System76 Galago Pro - это Linux-ноутбук под управлением System76 Open Firmware (основанной на coreboot+EDK2) от System76."

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
System76 Galago Pro - это Linux-ноутбук под управлением System76 Open Firmware (основанной на coreboot+EDK2) от System76.
<span id="Status"></span>
== Состояние ==
Устройство загружает NixOS.
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
За это отвечает пакет firmware-manager, который можно включить в конфигурации следующим образом:
{{file|configuration.nix|nix|<nowiki>
{
hardware.system76.enableAll = true;
};
</nowiki>
}}
=== galp5 ===
==== GTX 1650/1650 Ti ====
* Модуль NixOS Hardware при использовании [[Special:MyLanguage/Flakes|Flakes]]: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
* Модуль NixOS Hardware при использовании каналов: <code><nixos-hardware/system76/galp5-1650></code>
<span id="Tech_Docs"></span>
=== Техническая документация ===
Речь в документации идет о замене и обновлении таких компонентов, как оперативная память и диски.
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/1/ru

2024-10-15T18:49:03Z

Unabomberlive: Created page with "System76 Galago Pro - это Linux-ноутбук под управлением System76 Open Firmware (основанной на coreboot+EDK2) от System76."

System76 Galago Pro - это Linux-ноутбук под управлением System76 Open Firmware (основанной на coreboot+EDK2) от System76.

Hardware/System76/galp5/ru

2024-10-15T18:48:44Z

Unabomberlive: Created page with "Речь в документации идет о замене и обновлении таких компонентов, как оперативная память и диски."

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</div>
<span id="Status"></span>
== Состояние ==
Устройство загружает NixOS.
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
За это отвечает пакет firmware-manager, который можно включить в конфигурации следующим образом:
{{file|configuration.nix|nix|<nowiki>
{
hardware.system76.enableAll = true;
};
</nowiki>
}}
=== galp5 ===
==== GTX 1650/1650 Ti ====
* Модуль NixOS Hardware при использовании [[Special:MyLanguage/Flakes|Flakes]]: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
* Модуль NixOS Hardware при использовании каналов: <code><nixos-hardware/system76/galp5-1650></code>
<span id="Tech_Docs"></span>
=== Техническая документация ===
Речь в документации идет о замене и обновлении таких компонентов, как оперативная память и диски.
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/13/ru

2024-10-15T18:48:43Z

Речь в документации идет о замене и обновлении таких компонентов, как оперативная память и диски.

Hardware/System76/galp5/ru

2024-10-15T18:48:00Z

Unabomberlive:

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</div>
<span id="Status"></span>
== Состояние ==
Устройство загружает NixOS.
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
За это отвечает пакет firmware-manager, который можно включить в конфигурации следующим образом:
{{file|configuration.nix|nix|<nowiki>
{
hardware.system76.enableAll = true;
};
</nowiki>
}}
=== galp5 ===
==== GTX 1650/1650 Ti ====
* Модуль NixOS Hardware при использовании [[Special:MyLanguage/Flakes|Flakes]]: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
* Модуль NixOS Hardware при использовании каналов: <code><nixos-hardware/system76/galp5-1650></code>
<span id="Tech_Docs"></span>
=== Техническая документация ===
<div lang="en" dir="ltr" class="mw-content-ltr">
This goes over replacing and upgrading components such as RAM and drives.
</div>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/10/ru

2024-10-15T18:47:58Z

Unabomberlive:

* Модуль NixOS Hardware при использовании [[Special:MyLanguage/Flakes|Flakes]]: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>

Hardware/System76/galp5/ru

2024-10-15T18:46:44Z

Unabomberlive:

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</div>
<span id="Status"></span>
== Состояние ==
Устройство загружает NixOS.
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
За это отвечает пакет firmware-manager, который можно включить в конфигурации следующим образом:
{{file|configuration.nix|nix|<nowiki>
{
hardware.system76.enableAll = true;
};
</nowiki>
}}
=== galp5 ===
==== GTX 1650/1650 Ti ====
* Модуль NixOS Hardware при использовании Flakes: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
* Модуль NixOS Hardware при использовании каналов: <code><nixos-hardware/system76/galp5-1650></code>
<span id="Tech_Docs"></span>
=== Техническая документация ===
<div lang="en" dir="ltr" class="mw-content-ltr">
This goes over replacing and upgrading components such as RAM and drives.
</div>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/10/ru

2024-10-15T18:46:43Z

Unabomberlive:

* Модуль NixOS Hardware при использовании Flakes: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>

Hardware/System76/galp5/ru

2024-10-15T18:46:25Z

Unabomberlive: Created page with "* Модуль NixOS Hardware при использовании каналов: <code><nixos-hardware/system76/galp5-1650></code>"

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</div>
<span id="Status"></span>
== Состояние ==
Устройство загружает NixOS.
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
За это отвечает пакет firmware-manager, который можно включить в конфигурации следующим образом:
{{file|configuration.nix|nix|<nowiki>
{
hardware.system76.enableAll = true;
};
</nowiki>
}}
=== galp5 ===
==== GTX 1650/1650 Ti ====
* Модуль NixOS Hardware в Flake: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
* Модуль NixOS Hardware при использовании каналов: <code><nixos-hardware/system76/galp5-1650></code>
<span id="Tech_Docs"></span>
=== Техническая документация ===
<div lang="en" dir="ltr" class="mw-content-ltr">
This goes over replacing and upgrading components such as RAM and drives.
</div>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/11/ru

2024-10-15T18:46:24Z

Unabomberlive: Created page with "* Модуль NixOS Hardware при использовании каналов: <code><nixos-hardware/system76/galp5-1650></code>"

* Модуль NixOS Hardware при использовании каналов: <code><nixos-hardware/system76/galp5-1650></code>

Hardware/System76/galp5/ru

2024-10-15T18:45:58Z

Unabomberlive: Created page with "* Модуль NixOS Hardware в Flake: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>"

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</div>
<span id="Status"></span>
== Состояние ==
Устройство загружает NixOS.
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
За это отвечает пакет firmware-manager, который можно включить в конфигурации следующим образом:
{{file|configuration.nix|nix|<nowiki>
{
hardware.system76.enableAll = true;
};
</nowiki>
}}
=== galp5 ===
==== GTX 1650/1650 Ti ====
* Модуль NixOS Hardware в Flake: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for channels: <code><nixos-hardware/system76/galp5-1650></code>
</div>
<span id="Tech_Docs"></span>
=== Техническая документация ===
<div lang="en" dir="ltr" class="mw-content-ltr">
This goes over replacing and upgrading components such as RAM and drives.
</div>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/10/ru

2024-10-15T18:45:58Z

Unabomberlive: Created page with "* Модуль NixOS Hardware в Flake: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>"

* Модуль NixOS Hardware в Flake: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>

Hardware/System76/galp5/ru

2024-10-15T18:45:17Z

Unabomberlive: Created page with "За это отвечает пакет firmware-manager, который можно включить в конфигурации следующим образом:"

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</div>
<span id="Status"></span>
== Состояние ==
Устройство загружает NixOS.
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
За это отвечает пакет firmware-manager, который можно включить в конфигурации следующим образом:
{{file|configuration.nix|nix|<nowiki>
{
hardware.system76.enableAll = true;
};
</nowiki>
}}
=== galp5 ===
==== GTX 1650/1650 Ti ====
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for flakes: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for channels: <code><nixos-hardware/system76/galp5-1650></code>
</div>
<span id="Tech_Docs"></span>
=== Техническая документация ===
<div lang="en" dir="ltr" class="mw-content-ltr">
This goes over replacing and upgrading components such as RAM and drives.
</div>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/7/ru

2024-10-15T18:45:16Z

Unabomberlive: Created page with "За это отвечает пакет firmware-manager, который можно включить в конфигурации следующим образом:"

За это отвечает пакет firmware-manager, который можно включить в конфигурации следующим образом:

Hardware/System76/galp5/ru

2024-10-15T18:44:42Z

Unabomberlive: Created page with "== Состояние =="

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</div>
<span id="Status"></span>
== Состояние ==
Устройство загружает NixOS.
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
<div lang="en" dir="ltr" class="mw-content-ltr">
These are handled by the firmware-manager package which can be enabled in your configuration like this:
</div>
{{file|configuration.nix|nix|<nowiki>
{
hardware.system76.enableAll = true;
};
</nowiki>
}}
=== galp5 ===
==== GTX 1650/1650 Ti ====
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for flakes: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for channels: <code><nixos-hardware/system76/galp5-1650></code>
</div>
<span id="Tech_Docs"></span>
=== Техническая документация ===
<div lang="en" dir="ltr" class="mw-content-ltr">
This goes over replacing and upgrading components such as RAM and drives.
</div>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/2/ru

2024-10-15T18:44:41Z

Unabomberlive: Created page with "== Состояние =="

== Состояние ==

Hardware/System76/galp5/ru

2024-10-15T18:44:25Z

Unabomberlive: Created page with "Устройство загружает NixOS."

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
== Status ==
</div>
Устройство загружает NixOS.
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
<div lang="en" dir="ltr" class="mw-content-ltr">
These are handled by the firmware-manager package which can be enabled in your configuration like this:
</div>
{{file|configuration.nix|nix|<nowiki>
{
hardware.system76.enableAll = true;
};
</nowiki>
}}
=== galp5 ===
==== GTX 1650/1650 Ti ====
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for flakes: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for channels: <code><nixos-hardware/system76/galp5-1650></code>
</div>
<span id="Tech_Docs"></span>
=== Техническая документация ===
<div lang="en" dir="ltr" class="mw-content-ltr">
This goes over replacing and upgrading components such as RAM and drives.
</div>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/3/ru

2024-10-15T18:44:22Z

Unabomberlive: Created page with "Устройство загружает NixOS."

Устройство загружает NixOS.

Hardware/System76/galp5

2024-10-15T18:43:35Z

Unabomberlive:

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<translate>

The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</translate>
<translate>
== Status == 
</translate>
<translate>

The device boots NixOS.
</translate>
<translate>
== Known issues == 
</translate>
<translate>
== Configuration == 
</translate>
<translate>
=== BIOS === 
</translate>
<translate>

These are handled by the firmware-manager package which can be enabled in your configuration like this:
</translate>
{{file|configuration.nix|nix|<nowiki>
{
hardware.system76.enableAll = true;
};
</nowiki>
}}
<translate>
=== galp5 === 
</translate>
<translate>
==== GTX 1650/1650 Ti ==== 
</translate>
<translate>

* NixOS Hardware module for flakes: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
</translate>
<translate>

* NixOS Hardware module for channels: <code><nixos-hardware/system76/galp5-1650></code>
</translate>
<translate>
=== Tech Docs === 
</translate>
<translate>

This goes over replacing and upgrading components such as RAM and drives.
</translate>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Hardware/System76/galp5

2024-10-15T18:43:05Z

Unabomberlive:

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<translate>

The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</translate>
<translate>
== Status == 
</translate>
<translate>

The device boots NixOS.
</translate>
<translate>
== Known issues == 
</translate>
<translate>
== Configuration == 
</translate>
<translate>
=== BIOS === 
</translate>
<translate>

These are handled by the firmware-manager package which can be enabled in your configuration like this:
</translate>
{{file|disko-config.nix|nix|<nowiki>
{
hardware.system76.enableAll = true;
};
</nowiki>
}}
<translate>
=== galp5 === 
</translate>
<translate>
==== GTX 1650/1650 Ti ==== 
</translate>
<translate>

* NixOS Hardware module for flakes: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
</translate>
<translate>

* NixOS Hardware module for channels: <code><nixos-hardware/system76/galp5-1650></code>
</translate>
<translate>
=== Tech Docs === 
</translate>
<translate>

This goes over replacing and upgrading components such as RAM and drives.
</translate>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Hardware/System76/galp5/ru

2024-10-15T18:40:53Z

Unabomberlive: Created page with "=== Техническая документация ==="

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
== Status ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The device boots NixOS.
</div>
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
<div lang="en" dir="ltr" class="mw-content-ltr">
These are handled by the firmware-manager package which can be enabled in your configuration like this:
</div>
{
hardware.system76.enableAll = true;
};
=== galp5 ===
==== GTX 1650/1650 Ti ====
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for flakes: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for channels: <code><nixos-hardware/system76/galp5-1650></code>
</div>
<span id="Tech_Docs"></span>
=== Техническая документация ===
<div lang="en" dir="ltr" class="mw-content-ltr">
This goes over replacing and upgrading components such as RAM and drives.
</div>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/12/ru

2024-10-15T18:40:52Z

Unabomberlive: Created page with "=== Техническая документация ==="

=== Техническая документация ===

Hardware/System76/galp5/ru

2024-10-15T18:40:29Z

Unabomberlive: Created page with "==== GTX 1650/1650 Ti ===="

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
== Status ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The device boots NixOS.
</div>
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
<div lang="en" dir="ltr" class="mw-content-ltr">
These are handled by the firmware-manager package which can be enabled in your configuration like this:
</div>
{
hardware.system76.enableAll = true;
};
=== galp5 ===
==== GTX 1650/1650 Ti ====
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for flakes: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for channels: <code><nixos-hardware/system76/galp5-1650></code>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
=== Tech Docs ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
This goes over replacing and upgrading components such as RAM and drives.
</div>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/9/ru

2024-10-15T18:40:24Z

Unabomberlive: Created page with "==== GTX 1650/1650 Ti ===="

==== GTX 1650/1650 Ti ====

Hardware/System76/galp5/ru

2024-10-15T18:40:23Z

Unabomberlive: Created page with "=== galp5 ==="

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
== Status ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The device boots NixOS.
</div>
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
<div lang="en" dir="ltr" class="mw-content-ltr">
These are handled by the firmware-manager package which can be enabled in your configuration like this:
</div>
{
hardware.system76.enableAll = true;
};
=== galp5 ===
<div lang="en" dir="ltr" class="mw-content-ltr">
==== GTX 1650/1650 Ti ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for flakes: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for channels: <code><nixos-hardware/system76/galp5-1650></code>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
=== Tech Docs ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
This goes over replacing and upgrading components such as RAM and drives.
</div>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/8/ru

2024-10-15T18:40:22Z

Unabomberlive: Created page with "=== galp5 ==="

=== galp5 ===

Hardware/System76/galp5/ru

2024-10-15T18:40:17Z

Unabomberlive: Created page with "== Настройка =="

{{DISPLAYTITLE:System76 Galago Pro}}
{{Hardware/breadcrumb}}<div class="infobox">
{|class="table"
|-
!colspan="2" class="title"|System76 Galago Pro
|-
!Manufacturer
|System76
|-
!Architecture
|x86_64-linux
|-
!colspan="2" class="title"|galp5
|-
!Status
|supported
|-
!Maintainer
|[[User:Ahoneybun|Ahoneybun]]
|}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The System76 Galago Pro is a Linux laptop running System76 Open Firmware (based on coreboot+EDK2) from System76
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
== Status ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The device boots NixOS.
</div>
<span id="Known_issues"></span>
== Известные проблемы ==
<span id="Configuration"></span>
== Настройка ==
=== BIOS ===
<div lang="en" dir="ltr" class="mw-content-ltr">
These are handled by the firmware-manager package which can be enabled in your configuration like this:
</div>
{
hardware.system76.enableAll = true;
};
<div lang="en" dir="ltr" class="mw-content-ltr">
=== galp5 ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== GTX 1650/1650 Ti ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for flakes: <code>nixos-hardware.nixosModules.system76-galp5-1650</code>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* NixOS Hardware module for channels: <code><nixos-hardware/system76/galp5-1650></code>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
=== Tech Docs ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
This goes over replacing and upgrading components such as RAM and drives.
</div>
https://tech-docs.system76.com/models/galp5/README.html

[[Category: Incomplete]]

Translations:Hardware/System76/galp5/5/ru

2024-10-15T18:40:17Z

Unabomberlive: Created page with "== Настройка =="

== Настройка ==