-
(multiple answer) Git is:
- a. A version control system
- b. Centralized
- c. Distributed
- d. The same as GitHub
-
(T/F) Git and GitHub are the same thing.
user nginx; | |
worker_processes auto; | |
error_log /dev/stderr warn; | |
pid /var/run/nginx.pid; | |
worker_rlimit_nofile 100000; | |
events { | |
worker_connections 102400; |
#!/bin/sh | |
cd /home/vault | |
if [[ ! -f jq ]] | |
then | |
echo "Download jq command..." | |
wget https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64 -O jq | |
chmod +x jq | |
fi |
# | |
# Based on https://hub.docker.com/_/sonarqube | |
# | |
version: "3.7" | |
services: | |
sonarqube: | |
container_name: sonarqube |
How to transcribe Thai speech in videos into text.
-
Google Cloud or Firebase project with billing enabled.
-
ffmpeg
or Docker.
Preface
Listen, if you want to use Zuul, the easiest path is just use the Spring Boot version. I'm not exactly a fan of Spring in general, but this is the only solution available that's the least painful. Recent release of Spring Cloud Gateway looks promising but I'm satisfied so far with Spring Boot + Zuul that I'm not that interested in evaluating Spring Cloud Gateway,
We are also talking about Zuul 1.x here. Zuul 2.x is a whole can of worms I'd rather not rant about here.
This applies to Finchley (2.x) from SR1 release (may apply to other releases but not guaranteed)
- Re: using logback. The documentation says it's recommended to use
logback-spring.xml
in your classpath, but it doesn't work. You should actually uselogback.xml
or your logging configuration is not recognized at all. While at the subject, it is recommended not to use asynchronous logging at all. U
## this GeoIP dat file relate on centos environment please change to your OS path | |
geoip_country /usr/share/GeoIP/GeoIP-initial.dat; | |
map $request_uri $request_uri_path { | |
"~^(?P<path>[^?]*)(\?.*)?$" $path; | |
} | |
map $upstream_response_time $new_upstream_response_time { | |
default $upstream_response_time; | |
'' null; |
package main | |
import ( | |
"io" | |
"net/http" | |
"sync/atomic" | |
) | |
func index() http.Handler { | |
return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) { |
package main | |
import ( | |
"context" | |
"flag" | |
"fmt" | |
"log" | |
"net/http" | |
"os" | |
"os/signal" |
This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.
While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.