ghuntley

background

1. Now that coder is in nixpkgs at https://search.nixos.org/packages?channel=22.11&show=coder&from=0&size=50&sort=relevance&type=packages&query=coder
2. The next step is to enable running coder in NixOS via services.coder.enable = true;
3. Thus design configuration options such as https://search.nixos.org/options?channel=22.11&show=services.znc.user&from=0&size=50&sort=relevance&type=packages&query=znc
4. Refer to https://github.com/NixOS/nixpkgs/blob/nixos-22.11/nixos/modules/services/networking/znc/default.nix for an example of what is to be achieved.

next steps

1. What configuration options should we expose vs encouraging usage of extraFlags?

ghuntley

# Edit this configuration file to define what should be installed on
# your system.  Help is available in the configuration.nix(5) man page
# and in the NixOS manual (accessible by running ‘nixos-help’).

{ config, lib, pkgs, ... }:
{
  imports =
    [
      ./hardware-configuration.nix
    ];

ghuntley

terraform {
  required_providers {
    coder = {
      source  = "coder/coder"
      version = "0.4.9"
    }
    docker = {
      source  = "kreuzwerker/docker"
      version = "~> 2.20.2"
    }

ghuntley

## Learn more about this file at 'https://www.gitpod.io/docs/references/gitpod-yml'
##
## This '.gitpod.yml' file when placed at the root of a project instructs
## Gitpod how to prepare & build the project, start development environments
## and configure continuous prebuilds. Prebuilds when enabled builds a project
## like a CI server so you can start coding right away - no more waiting for
## dependencies to download and builds to finish when reviewing pull-requests
## or hacking on something new.
##
## With Gitpod you can develop software from any device (even iPads) via 

ghuntley

POST https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery HTTP/1.1
content-type: application/json
accept: application/json;api-version=3.0-preview.1
accept-encoding: gzip

{
  filters: [
    {
      criteria: [
        {

ghuntley

observations

• Using https://github.com/ghuntley/python-repro/commit/248b8d687524a61569ab7324616eb4223d7be980
• Which has the following requirements.txt

# Essentials:
datasette
sqlite-utils
pip

ghuntley

👋 Hi, I'm Geoff. I stole off all your NFTs.

I respectfully ask that you don't quote me as “$company person Geoffrey Huntley said” – if I speak for a company, I will publish on its channels. My full name is "Geoffrey Huntley" please use that and not "Geoff Huntley".

• website: https://ghuntley.com/
• newsletter: https://ghuntley.com/newsletter
• twitter: https://www.twitter.com/geoffreyhuntley.com
• linkedin: https://www.linkedin.com/in/geoffreyhuntley

ghuntley

2021-10-27 13:22:54.5507|INFO|Microsoft.Oryx.BuildScriptGeneratorCli.CommandBase|Oryx command line: /opt/buildscriptgen/GenerateBuildScript.dll build --manifest-dir /workspaces/.oryx -p virtualenv_name=.venv --log-file /workspaces/.oryx/build.log /workspaces/new
2021-10-27 13:22:54.6711|DEBUG|Microsoft.Oryx.BuildScriptGenerator.DefaultBuildScriptGenerator|Available checkers: 5
2021-10-27 13:22:54.6808|DEBUG|Microsoft.Oryx.Detector.Node.NodeDetector|Could not find package.json/package-lock.json/yarn.lock in repo
2021-10-27 13:22:54.6875|DEBUG|Microsoft.Oryx.Detector.Node.NodeDetector|Could not find typical Node.js files in repo
2021-10-27 13:22:54.6875|DEBUG|Microsoft.Oryx.Detector.Node.NodeDetector|App in repo is not a NodeJS app
2021-10-27 13:22:54.6915|INFO|Microsoft.Oryx.Detector.Python.PythonDetector|Cound not find requirements.txt at the root of the repo.
2021-10-27 13:22:54.6942|DEBUG|Microsoft.Oryx.Detector.Python.PythonDetector|Could not find file 'runtime.txt' in source repo
2021-10-27 13:22:54.6969

ghuntley

# NOTICES AND INFORMATION
Do Not Translate or Localize

This software incorporates material from third parties. Microsoft makes certain
open source code available at https://3rdpartysource.microsoft.com, or you may
send a check or money order for US $5.00, including the product name, the open
source component name, and version number, to:

Source Code Compliance Team
Microsoft Corporation

ghuntley

To Microsoft Developer Division Leadership,

Those of us who work in the Microsoft Developer Division (DevDiv) would like to respond to the recent controversy surrounding the pulling and reinstating of the "dotnet watch" feature of dotnet 6. While we are grateful that cooler heads prevailed and "dotnet watch" was preserved, we do not feel confident that this will not happen again?quite the opposite.

To show this point, we will look at the recent blog post by Scott Hunter (https://devblogs.microsoft.com/dotnet/net-hot-reload-support-via-cli/). Based on everything we know of the situation and how the Developer Division operates, little of what Scott wrote seems true and contradicts what happened. To be clear, this is not an attack on Scott Hunter; and instead, it shows how far others are willing to go to protect management.

"As a team, we are committed to .NET being an open platform and doing our development in the open. The very fact that we decided to adopt an open posture by default from the start for dev