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.
| #!/bin/bash | |
| # if we are testing a PR, merge it with the latest master branch before testing | |
| # this ensures that all tests pass with the latest changes in master. | |
| set -eu -o pipefail | |
| PR_NUMBER=${CI_PULL_REQUEST//*pull\//} | |
| err=0 | |
| if [ -z "$PR_NUMBER" ]; then |
| #!/bin/bash | |
| if [ "$EUID" -ne 0 ] | |
| then echo "Must be root" | |
| exit | |
| fi | |
| apt-get update -y | |
| apt-get upgrade -y | |
| apt-get dist-upgrade -y |
Want to use Nix for development but you're not sure how? Concerned about the
fluidity of nixpkgs channels or not being able to easily install arbitrary
package versions?
When I first heard about Nix it seemed like the perfect tool for a developer. When I tried to actually use it for developing and deploying web apps, though, the pieces just didn't seem to add up.
The first step is to read the Code Contribution Guidelines documentation to get a good understanding of policies used by the project
Once that is done, the following commands illustrate a straight forward setup for submitting pull requests to the project:
| #!/bin/bash | |
| # The script does automatic checking on a Go package and its sub-packages, including: | |
| # 1. gofmt (http://golang.org/cmd/gofmt/) | |
| # 2. goimports (https://github.com/bradfitz/goimports) | |
| # 3. golint (https://github.com/golang/lint) | |
| # 4. go vet (http://golang.org/cmd/vet) | |
| # 5. race detector (http://blog.golang.org/race-detector) | |
| # 6. test coverage (http://blog.golang.org/cover) | |
| set -e |
| #!/bin/bash | |
| #set -e | |
| #set -x | |
| fail() { | |
| echo $1 | |
| [ -e ${EBS_DEVICE} ] && [ "$VOLUME_ID" != "" ] && [ $REGION != "" ] && { | |
| ec2-detach-volume --region $REGION $VOLUME_ID | |
| ec2-delete-volume --region $REGION $VOLUME_ID |
| # Raw transaction API example work-through | |
| # Send coins to a 2-of-3 multisig, then spend them. | |
| # | |
| # For this example, I'm using these three keypairs (public/private) | |
| # 0491bba2510912a5bd37da1fb5b1673010e43d2c6d812c514e91bfa9f2eb129e1c183329db55bd868e209aac2fbc02cb33d98fe74bf23f0c235d6126b1d8334f86 / 5JaTXbAUmfPYZFRwrYaALK48fN6sFJp4rHqq2QSXs8ucfpE4yQU | |
| # 04865c40293a680cb9c020e7b1e106d8c1916d3cef99aa431a56d253e69256dac09ef122b1a986818a7cb624532f062c1d1f8722084861c5c3291ccffef4ec6874 / 5Jb7fCeh1Wtm4yBBg3q3XbT6B525i17kVhy3vMC9AqfR6FH2qGk | |
| # 048d2455d2403e08708fc1f556002f1b6cd83f992d085097f9974ab08a28838f07896fbab08f39495e15fa6fad6edbfb1e754e35fa1c7844c41f322a1863d46213 / 5JFjmGo5Fww9p8gvx48qBYDJNAzR9pmH5S389axMtDyPT8ddqmw | |
| # First: combine the three keys into a multisig address: | |
| ./bitcoind createmultisig 2 '["0491bba2510912a5bd37da1fb5b1673010e43d2c6d812c514e91bfa9f2eb129e1c183329db55bd868e209aac2fbc02cb33d98fe74bf23f0c235d6126b1d8334f86","04865c40293a680cb9c020e7b1e106d8c1916d3cef99aa431a56d253e69256dac09ef122b1a9 |
| # Inspired from http://blog.hio.fr/2011/09/17/doctrine2-yaml-mapping-example.html | |
| MyEntity: | |
| type: entity | |
| repositoryClass: MyRepositoryClass | |
| table: my_entity | |
| namedQueries: | |
| all: "SELECT u FROM __CLASS__ u" | |
| # Class-Table-Inheritance |