description) to allow all kernel-related packages to be overriden
easily. For instance, you can now say in configuration.nix
boot = {
kernelPackages = pkgs: pkgs.kernelPackages_2_6_25;
};
to use Linux 2.6.25.x. Externel kernel module packages (like
the NVIDIA drivers) appropriate for this kernel will then be used
automatically.
svn path=/nixos/trunk/; revision=11880
Eelco, can your review this patch ?
I hope it fits your design - if not revert it
This way we can drop the mod_php option (See example)
svn path=/nixos/trunk/; revision=11734
and a httpsPort, there are now options "port" and "enableSSL". So
to get https you should typically set up a vhost like this:
virtualHosts = [
{ hostName = "foo.example.org";
enableSSL = true;
sslServerCert = "...";
sslServerKey = "...";
}
];
* sslServerCert and sslServerKey can be set per vhost. This is
currently only useful when doing IP-based vhosting.
* enableUserDir is now a per-vhost setting, as it should be.
* Convenience option globalRedirect to redirect the entire host to
some URL.
svn path=/nixos/trunk/; revision=11704
add `/var/run/current-system/sw/lib' to `LD_LIBRARY_PATH'. This should allow
NSS modules to be added and taken into account by applications without
the need to reboot.
svn path=/nixos/trunk/; revision=11290
Currently, the solution is a bit hackish since running applications
will not work after a `nixos-rebuild' because `libnss_mdns' is not
in their `LD_LIBRARY_PATH'.
svn path=/nixos/trunk/; revision=11162
This is really a hack since programs not known to `system.nix' will not be in the path
of `activate-configuration', which consequently creates empty `.real' files under
`/var/setuid-wrappers'. I don't know what the best way to address this is: let admins
write `.real' files by hand? Add a `setuidPackages' attribute, listing the names of
packages that contain the binaries listed in `setuidPrograms'?
svn path=/nixos/trunk/; revision=11153
( added \n in config concatenation as well )
added serviceProposal, examples see upstart-jobs/newProposal/*.nix
enhancement: everything belonging to one job is within the same file
(was: upstart-jobs/default.nix, options.nix and the job file)
drawback: options won't be included within the manual
(can be fixed see comments in options.nix)
comment: looking at the funtion newProposalJobs maybe it's overkill?
Hope it pays off if we start having dozens of small different services..
svn path=/nixos/trunk/; revision=11141
* Allow multiple instantiations of a subservice (for instance,
multiple Subversion subservices in the same Apache server).
svn path=/nixos/trunk/; revision=10675