You have a repository, call it alice/repo. You would like to transfer it to the user bob, so it will become bob/repo.
However, you make heavy use of the GitHub Pages feature, so that people are often accessing https://alice.github.io/repo/. GitHub will helpfully redirect all of your repository stuff hosted on github.com after the move, but will not redirect the GitHub Pages hosted on github.io.
| #-------------------------------------------------------------------# | |
| ### Csalásdetektálás - gépjárműbiztosítás ########################### | |
| ### BURN meetup 2017.03.29 ########################### | |
| #-------------------------------------------------------------------# | |
| # szükséges csomagok: | |
| # data.table | |
| # stringr | |
| # igraph |
| ``` r | |
| `?` <- function(x, y) { | |
| y <- substitute(y) | |
| if (!is.call(y) || !identical(as.symbol(":"), y[[1]])) stop("Invalid", call. = FALSE) | |
| eval(call("if", x, y[[2]], y[[3]])) | |
| } | |
| T ? 1 | |
| #> Error: Invalid |
Here is an attempt at working around adding .git into dockers accidentally, an issue you saw earlier.
Docker is written in go and supports some wildcards in the ADD command. https://stackoverflow.com/questions/26591862/using-docker-add-command-for-multiples-files links to: https://golang.org/src/path/filepath/match_test.go
Putting that together,
nfultz@nfultz:dockertest$tree -a
.
library(tidyverse)## Loading tidyverse: ggplot2
## Loading tidyverse: tibble
## Loading tidyverse: tidyr
## Loading tidyverse: readr
Just documenting docs, articles, and discussion related to gRPC and load balancing.
https://github.com/grpc/grpc/blob/master/doc/load-balancing.md
Seems gRPC prefers thin client-side load balancing where a client gets a list of connected clients and a load balancing policy from a "load balancer" and then performs client-side load balancing based on the information. However, this could be useful for traditional load banaling approaches in clound deployments.
https://groups.google.com/forum/#!topic/grpc-io/8s7UHY_Q1po
gRPC "works" in AWS. That is, you can run gRPC services on EC2 nodes and have them connect to other nodes, and everything is fine. If you are using AWS for easy access to hardware then all is fine. What doesn't work is ELB (aka CLB), and ALBs. Neither of these support HTTP/2 (h2c) in a way that gRPC needs.
Currently, only data within the last 90 days is available via the OpenAQ API. However, there is much more data available on OpenAQ and a variety of different access mechanisms. Note also that there is work under way to bring back to the API a mechanism to access the data older than 90 days, details here.
If you're looking to query across all the data or even easily export the data (or a subset of it), the easiest way to do that currently is using a service like Amazon Athena. I'll provide some directions on how to do that below, but at a high level, this will let you make any query of the entire dataset that you'd like (written in SQL). I'll also provide some sample queries so you can see what's possible.
On to the directions!
| \documentclass[15pt]{scrartcl} | |
| \usepackage[a6paper,left=1cm,right=1cm,top=2cm,bottom=1cm,heightrounded]{geometry} | |
| \usepackage[svgnames]{xcolor} | |
| \usepackage{pdflscape} | |
| \usepackage{setspace} | |
| \usepackage[utf8]{inputenc} | |
| \usepackage[T1]{fontenc} | |
| \usepackage{graphicx} | |
| \usepackage{wallpaper} | |
| \usepackage[normalem]{ulem} |
This is a simple utility script for cleaning up Firebase Hosting versions, leaving a specified number of versions remaining. This is primarily done to conserve storage usage, but may have other uses.
USE AT YOUR OWN RISK. NO WARRANTY IS PROVIDED. THIS SCRIPT DOES DELETE STUFF PERMANENTLY
node cleanupVersions.js [commit]
| "use strict"; | |
| // Lambda@Edge trigger to serve index.html when the | |
| // user requests /app/*; use in Cloudfront as a viewer-request | |
| // event | |
| exports.handler = (event, context, callback) => { | |
| const request = event.Records[0].cf.request; | |
| if (/^\/app($|\/)/.test(request.uri) || request.uri == "/") { | |
| request.uri = "index.html"; |
