This document now exists on the official ASP.NET core docs page.
- Application
- Request Handling
This document now exists on the official ASP.NET core docs page.
client { | |
enabled = true | |
node_class = "" | |
no_host_uuid = false | |
servers = ["10.253.155.163","10.253.155.17","10.253.155.102"] | |
max_kill_timeout = "30s" |
#!/bin/bash | |
service_name="backup-all-secrets" | |
secret_list=( `docker secret ls --format "{{ .Name }}"` ) | |
cmd="docker service create \ | |
--name $service_name \ | |
--constraint node.hostname==`hostname` " | |
for secret in "${secret_list[@]}" |
using System; | |
using System.Linq; | |
using System.Reflection; | |
using Microsoft.Extensions.DependencyInjection; | |
public static class ServiceCollectionExtentions | |
{ | |
public static void AddAllTypes<T>(this IServiceCollection services | |
, Assembly[] assemblies | |
, bool additionalRegisterTypesByThemself = false |
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
FROM microsoft/mssql-server-linux | |
COPY . /usr/src/app | |
ENTRYPOINT [ "/bin/bash", "/usr/src/app/docker-entrypoint.sh" ] | |
CMD [ "/opt/mssql/bin/sqlservr" ] |
$/
artifacts/
build/
docs/
lib/
packages/
samples/
src/
tests/