Install Requirements Packages
opkg update && opkg install ca-certificates zsh curl git-http
Install oh-my-zsh
/* eslint-disable no-var, vars-on-top, no-param-reassign */ | |
function redirect(uri) { | |
// remove repeated slashes | |
uri = uri.replace(/\/+/g, "/"); | |
// remove trailing slash | |
if (uri !== "/" && uri.endsWith("/")) { | |
uri = uri.slice(0, -1); | |
} | |
return uri; |
{ | |
"barmode": "stack", | |
"legend": { | |
"bgcolor": "#fff", | |
"orientation": "h" | |
}, | |
"margin": { | |
"b": 30, | |
"l": 45, | |
"pad": 4, |
# Sample Nginx config with sane caching settings for modern web development | |
# | |
# Motivation: | |
# Modern web development often happens with developer tools open, e. g. the Chrome Dev Tools. | |
# These tools automatically deactivate all sorts of caching for you, so you always have a fresh | |
# and juicy version of your assets available. | |
# At some point, however, you want to show your work to testers, your boss or your client. | |
# After you implemented and deployed their feedback, they reload the testing page – and report | |
# the exact same issues as before! What happened? Of course, they did not have developer tools | |
# open, and of course, they did not empty their caches before navigating to your site. |
#!/usr/bin/env bash | |
function log () { | |
printf "%s %s\n" "->" "$1" | |
} | |
log "Updating all asdf-plugin remotes..." | |
asdf plugin update --all |
package test; | |
import com.fasterxml.jackson.core.JsonGenerator; | |
import com.fasterxml.jackson.core.JsonParser; | |
import com.fasterxml.jackson.databind.ObjectMapper; | |
import com.fasterxml.jackson.dataformat.xml.JacksonXmlModule; | |
import com.fasterxml.jackson.dataformat.xml.XmlMapper; | |
import com.fasterxml.jackson.module.jaxb.JaxbAnnotationIntrospector; | |
import foo.SampleBean; | |
import foo.SampleBeans; |
Moved to git repository: https://github.com/aliesbelik/load-testing-toolkit
Tools to benchmark & load-test your code or services
C
C
You can use this diagram as a template to create your own git branching diagrams. Here's how:
https://gist.githubusercontent.com/jwcastillo/d7cc7614751a521f7ca0a2d98be1c917/raw/d6db2ee72152d5f1e45cf94589f29997c157914d/multi-team-git-flow.xml