Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 43c663975caf8d3e931bfdb30573efd749075a44
https://github.com/NixOS/nixpkgs/commit/43c663975caf8d3e931bfdb30573efd749075a44
Author: Franz Pletz
Date: 2016-08-10 (Wed, 10 Aug 2016)
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 3822c56e1edcebd87b53169a469e27d7fde3f555
https://github.com/NixOS/nixpkgs/commit/3822c56e1edcebd87b53169a469e27d7fde3f555
Author: obadz
Date: 2016-08-10 (Wed, 10 Aug 2016)
Changed
Hello,
Am Dienstag, den 09.08.2016, 09:16 -0700 schrieb Colin Z:
> Hi all, I'm trying to get NixOS running on a Raspberry Pi 3 but ran
> into an issue with an outdated Nix
>
> I used the first image linked at https://nixos.org/wiki/Raspberry_Pi
> and after putting the latest firmware from
>
Just put haproxy in front and then.. oh wait, what if the haproxy
configuration changes? :p
Since systemd already does socket activation it would be nice if it could
also start a new process before sending the SIGTERM to the old one. The old
process would the stop accepting new connection but
On Tue, 9 Aug 2016 19:54:10 +0100 Luca Bruno
wrote:
> When using Nixos to define my system, I want to use Nixos to define my
> > system. No other 'orchestration' software or (god forbid) any
> > user/admin should change that the imperative way. Only then can I
> > use nix
Would you mind expanding on these two reasons ?
If I understand you well, the first is about using reload instead of
restart.
I guess it is useful for shorter downtimes, or even to avoid breaking
existing connections, right ?
This seems like a valid point to me. We could try to improve this.
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 88f3d043b63551377ecb7a6f50469e8c6cbe15f1
https://github.com/NixOS/nixpkgs/commit/88f3d043b63551377ecb7a6f50469e8c6cbe15f1
Author: Robert
Date: 2016-08-09 (Tue, 09 Aug
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 57b7c3c545f35385dbe5a1eab44028f9233b736e
https://github.com/NixOS/nixpkgs/commit/57b7c3c545f35385dbe5a1eab44028f9233b736e
Author: obadz
Date: 2016-08-09 (Tue, 09 Aug 2016)
Changed
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 918b11e64c99d094f8b91e87f7b7c6b11851ce55
https://github.com/NixOS/nixpkgs/commit/918b11e64c99d094f8b91e87f7b7c6b11851ce55
Author: Stefan Junker
Date: 2016-08-09 (Tue, 09
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 17f6219f387ce5e67aaed2bf81bd18c7426df7e9
https://github.com/NixOS/nixpkgs/commit/17f6219f387ce5e67aaed2bf81bd18c7426df7e9
Author: Franz Pletz
Date: 2016-08-09 (Tue, 09
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 4c43ac2db55a4313313d6d6393c40b771ae4c0ad
https://github.com/NixOS/nixpkgs/commit/4c43ac2db55a4313313d6d6393c40b771ae4c0ad
Author: Dan Peebles
Date: 2016-08-09 (Tue, 09 Aug 2016)
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: b91fc3f8d065cde3501d9dff7590bce57fe6678a
https://github.com/NixOS/nixpkgs/commit/b91fc3f8d065cde3501d9dff7590bce57fe6678a
Author: Fabian Schmitthenner
Date: 2016-08-09
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 6152cf32e31c232fa5ca21abdc02250e0d0e8e91
https://github.com/NixOS/nixpkgs/commit/6152cf32e31c232fa5ca21abdc02250e0d0e8e91
Author: Vladimír Čunát
Date: 2016-08-09 (Tue, 09 Aug 2016)
When using Nixos to define my system, I want to use Nixos to define my
> system. No other 'orchestration' software or (god forbid) any
> user/admin should change that the imperative way. Only then can I use
> nix the way its intended to have fully reproducible and revertable
> states.
>
Except
On Tue, 9 Aug 2016 18:06:50 +0100 Luca Bruno
wrote:
> So, there are few drawbacks with the read-only nginx config as it is.
> Of course, you can at any time run the nginx with an /etc/nginx
> config that you write imperatively, by creating a brand new systemd
> service and
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 21102b15892a24ba12aaf1dcc729389c6d36feb3
https://github.com/NixOS/nixpkgs/commit/21102b15892a24ba12aaf1dcc729389c6d36feb3
Author: Danny Arnold
Date: 2016-08-09 (Tue, 09 Aug 2016)
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 3efadce03b12ff6483d34b1353106161fff6a308
https://github.com/NixOS/nixpkgs/commit/3efadce03b12ff6483d34b1353106161fff6a308
Author: Moritz Ulrich
Date: 2016-08-09 (Tue, 09 Aug 2016)
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 3cf5d5ebed8c7c20f0da1ec3bc66388f1886b8ec
https://github.com/NixOS/nixpkgs/commit/3cf5d5ebed8c7c20f0da1ec3bc66388f1886b8ec
Author: Robin Gloster
Date: 2016-08-09 (Tue, 09 Aug 2016)
So, there are few drawbacks with the read-only nginx config as it is. Of
course, you can at any time run the nginx with an /etc/nginx config that
you write imperatively, by creating a brand new systemd service and
disregarding the existing one. After all nginx is quite a simple service to
run.
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: d6f1895039d8bf441637de17234b27649300a45c
https://github.com/NixOS/nixpkgs/commit/d6f1895039d8bf441637de17234b27649300a45c
Author: Markus Mueller
Date: 2016-08-09
Hi all, I'm trying to get NixOS running on a Raspberry Pi 3 but ran into an
issue with an outdated Nix
I used the first image linked at https://nixos.org/wiki/Raspberry_Pi and
after putting the latest firmware from
https://github.com/Hexxeh/rpi-firmware (including kernel7.img) on the boot
Hi,
You could have a `shell.nix` file as follows:
import ./default.nix { sampleproject = { outPath = ""; name =
"sampleproject"; } ; }
This is hacky but with that you will not copy the project tree into the nix
store when runninx `nix-shell` (this will only be done when running
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 74b3ad148d36f4e8b9a41a08cbf6e2407cdda425
https://github.com/NixOS/nixpkgs/commit/74b3ad148d36f4e8b9a41a08cbf6e2407cdda425
Author: obadz
Date: 2016-08-09 (Tue, 09 Aug 2016)
Changed
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 55d881eea334049dbb6ac10623bb895363857fca
https://github.com/NixOS/nixpkgs/commit/55d881eea334049dbb6ac10623bb895363857fca
Author: aszlig
Date: 2016-08-09 (Tue, 09 Aug 2016)
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 5d5b2d3f8f341c31a5da2ada182f8a2a9bb9935c
https://github.com/NixOS/nixpkgs/commit/5d5b2d3f8f341c31a5da2ada182f8a2a9bb9935c
Author: Kamil Chmielewski
Date: 2016-08-09 (Tue, 09 Aug
And one extra reason is that this way we can keep previous versions
(generations) of the config file, allowing quick rollbacks.
On Tue, Aug 9, 2016 at 2:34 PM Robin Gloster wrote:
> Hi,
>
> Adding to Eelco's explanation, this would also theoretically allow you to
> start e.g.
Hi nix devs,
I am posting here an issue reported on [1], hoping to get a quick fix
With my current version of nix, I observe the following behaviour after
some calls to nix:
The command hangs forever.
|$ nix-build ... these derivations will be built:
/nix/store/-.drv waiting for locks
Hi,
Adding to Eelco's explanation, this would also theoretically allow you to start
e.g.
different nginx servers on different versions with different configurations.
For
the most or probably all services more changes would be needed to support this
realistically.
Robin
-Original
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: b0b0a45bb1277e77528a0216a0f697540ef659a6
https://github.com/NixOS/nixpkgs/commit/b0b0a45bb1277e77528a0216a0f697540ef659a6
Author: Robin Gloster
Date: 2016-08-09 (Tue, 09 Aug 2016)
Is this intentional? I'm writing a service and want to know whether to do
like nginx or use /etc for configs.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Hello nix-dev,
I was wondering, what is the best way to develop a project outside of
nixpkgs? My current method is something like this:
# default.nix
{ sampleproject ? { outPath = ./.; name = "sampleproject"; }
, pkgs ? import {}
}:
with pkgs.python35Packages;
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 199f5a2844cb31be96872599d8db7105b572f116
https://github.com/NixOS/nixpkgs/commit/199f5a2844cb31be96872599d8db7105b572f116
Author: Benjamin Saunders
Date: 2016-08-09 (Tue, 09 Aug
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 746b591c684f4a69f85dd49c05961892a3ac2b4b
https://github.com/NixOS/nixpkgs/commit/746b591c684f4a69f85dd49c05961892a3ac2b4b
Author: Aneesh Agrawal
Date: 2016-08-09 (Tue, 09 Aug 2016)
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 00b05d47d30fff2ca1925ec38078907b95c6cb69
https://github.com/NixOS/nixpkgs/commit/00b05d47d30fff2ca1925ec38078907b95c6cb69
Author: Daiderd Jordan
Date: 2016-08-07 (Sun, 07 Aug 2016)
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 0d69547365f1196b9101dc4f362e12b6f1eb6441
https://github.com/NixOS/nixpkgs/commit/0d69547365f1196b9101dc4f362e12b6f1eb6441
Author: Matt McHenry
Date: 2016-08-08 (Mon, 08 Aug
35 matches
Mail list logo