doytsujin

package akkahttptest

import akka.actor.ActorSystem
import akka.http.Http
import akka.stream.FlowMaterializer
import akka.http.server._
import akka.http.marshalling.PredefinedToResponseMarshallers._
import akka.stream.scaladsl.{HeadSink, Source}

object Proxy extends App {

doytsujin

package akkahttptest

import akka.actor.ActorSystem
import akka.http.Http
import akka.stream.FlowMaterializer
import akka.http.server._
import akka.http.marshalling.PredefinedToResponseMarshallers._
import akka.stream.scaladsl.{HeadSink, Source}

object Proxy extends App {

doytsujin

package mapmap

trait ECtx

trait KCtx

trait Var[C, T] {
  def get(c: C): T
}

doytsujin

package controllers

import config.{EndpointConfig => Config}

import play.api.mvc._
import play.api.Play.current
import play.api.libs.ws.{WSRequest, WS}

import scala.concurrent.Future
import scala.concurrent.ExecutionContext.Implicits.global

doytsujin

using System.Net;  
using Microsoft.Bot.Connector;

public static async Task<HttpResponseMessage> Run(HttpRequestMessage req, TraceWriter log)
{   
    log.Verbose($"C# HTTP trigger function processed a request. RequestUri={req.RequestUri}");

    var msg = await req.Content.ReadAsAsync<Message>();

doytsujin

#!/bin/bash

# Inspired by http://www.devthought.com/code/create-a-github-pull-request-from-the-terminal/
targetbranch=master

if test "$1"; then
        targetbranch=$1
fi

repo=`git remote -v | grep -m 1 "(push)" | sed -e "s/.*github.com[:/]\(.*\)\.git.*/\1/"`

doytsujin

#!/bin/bash

# customizable
LIST_DATA="#{window_name} #{pane_title} #{pane_current_path} #{pane_current_command}"
FZF_COMMAND="fzf-tmux -p --delimiter=: --with-nth 4 --color=hl:2"

# do not change
TARGET_SPEC="#{session_name}:#{window_id}:#{pane_id}:"

# select pane

doytsujin

Automated Docker releases using Maven and GitHub Actions

Life is too short for tedious, manual release processes.

Here, we will use Maven's [Release plugin][maven-release] to execute releases. Instead of triggering the release process manually, we will use a [GitHub Actions][gh-actions] workflow on the master branch. All development work is done on the dev branch (or feature branches) and a release is done when (and only when) the dev branch is merged with the master branch.

doytsujin

This was mirrored from the snapshot of earthserver.com available on archive.org
--------------------------------------------------------------------------------


Setting up a modern C++ development environment on Linux with Clang and Emacs

I am an independent game developer and this is my personal wiki.
Please feel free to email [email protected], and to follow @Earthserver
(Redirected from Setting up a C++11 development environment on Linux with Clang and Emacs)

doytsujin

resource "azurerm_resource_group" "dnsprivatezones" {
  name     = "connectivity-dnsprivatezones-001"
  location = "West Europe"
  tags = {
    "Usage" = "Azure Private DNS Zones for Private Endpoints"
  }
}
resource "azurerm_private_dns_zone" "azureautomation" {
  name                = "privatelink.azure-automation.net"
  resource_group_name = azurerm_resource_group.dnsprivatezones.name