This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Aug 30 09:24:03 comonad gnome-keyring-daemon[2179]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory | |
Aug 30 09:24:03 comonad .gnome-keyring-[2179]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// @flow | |
// So `declareService` receives a service declaration that provides some properties | |
// for creating a service including some functions for mapping service responses and | |
// query parameters. I thought it would be nice to parameterize `ServiceDeclaration` | |
// over the types of those mapping functions. | |
// | |
// Am I making sense? Does the *code* make any sense? If not how should I change it? | |
/* types.js -------------------------------------------------------- */ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
self: super: | |
{ | |
nix-venient = | |
let | |
inherit (super) stdenv lib curl jq makeWrapper fetchFromGitHub; | |
in | |
stdenv.mkDerivation rec { |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Apparently there is some confusion around the usage and inner workings of nix-channel. In order to improve the situation | |
we could perhaps host a little Q&A session in which we talk about usage patterns etc. | |
To make this as efficient as possible can we perhaps already collect some questions around nix-channel so we can start with those? |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
read -r -d '' TEMPLATE << EOM | |
with (import <nixpkgs> {}); | |
stdenv.mkDerivation { | |
name = "dev-shell"; | |
src = null; | |
buildInputs = [ __PKGS__ ]; | |
} | |
EOM |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
network.description = "hc-web continuous integration server"; | |
jenkinsMaster = | |
{ config, pkgs, ... }: | |
{ | |
# server config ... | |
}; | |
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* how do you decide if a candidate has the *potential* (not current skillset) to become a craftsman | |
* do you have a fixed roadmap for the apprenticeship? Is it the same for everyone? | |
* is there a fixed schedule for apprentices? Mondays "learning", Tue "production work", .... | |
* do you always have *one* mentor per *one* apprentice? | |
* how to bootstrap craftsmanship in our big company? turn everyone into an apprentice? | |
* what do you think about gamification/awarding badges to people as encouragement? (impact on salary?) | |
* what is the secret of your interview success? :) | |
====== |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[global_config] | |
borderless = True | |
inactive_color_offset = 0.94 | |
tab_position = right | |
[keybindings] | |
[layouts] | |
[[default]] | |
[[[child1]]] | |
parent = window0 | |
type = Terminal |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ stdenv, | |
cmake, | |
freetype, | |
fontconfig, | |
xclip, | |
pkgconfig, | |
fetchFromGitHub, | |
libX11, | |
gperf, | |
libXcursor, |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
module Main where | |
main :: IO () | |
main = putStrLn "Salute" |