We’re happy to announce Magenta, a project from the Google Brain team that asks: Can we use machine learning to create compelling art and music? If so, how? If not, why not?
// Settings edited by user | |
const YOUR_KEEP3R_ADDRESSS = ""; | |
const YOUR_KEEP3R_PRIVATE_KEY = ""; | |
// Code starts here | |
const { ethers } = require("ethers"); | |
const privateKey = Buffer.from(YOUR_KEEP3R_PRIVATE_KEY, 'hex'); | |
const UniswapSlidingWindow = "UniswapSlidingWindow"; | |
const HegicPoolKeep3r = "HegicPoolKeep3r"; |
30 0 * * * root /usr/local/bin/sendy-backup > /dev/null 2>&1 |
############## | |
# pretty prompt and font colors | |
############## | |
# alter the default colors to make them a bit prettier | |
echo -en "\e]P0000000" #black | |
echo -en "\e]P1D75F5F" #darkred | |
echo -en "\e]P287AF5F" #darkgreen | |
echo -en "\e]P3D7AF87" #brown | |
echo -en "\e]P48787AF" #darkblue |
- name: Run DB/API integration test suite | |
hosts: localhost | |
become: True | |
become_method: sudo | |
tasks: | |
- name: Use PSQL to Close Postgres DB connection to the master database | |
become: True | |
become_user: postgres |
IMPORTANT: Read this before implementing one of the configuration files below (for either Varnish 3.x or 4.x+).
USE: Replace the contents of the main Varnish configuration file located in /etc/varnish/default.vcl (root server access required - obviously) with the contents of the configuration you'll use (depending on your Varnish version) from the 2 examples provided below.
IMPORTANT: The following setup assumes a 180 sec (3 minute) cache time for cacheable content that does not have the correct cache-control HTTP headers. You can safely increase this to 300 sec (or more) for less busier sites or drop it to 60 sec or even 30 sec for high traffic sites. It obviously depends on your use case.
# to generate your dhparam.pem file, run in the terminal | |
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |
The new location is https://github.com/psanford/mirabox. I've turned it into a full git repository so that it is easier for others to contribute. This gist will not be updated anymore and I won't be checking the comments. Please open an issue or a pull request on the git repo.
There's not a lot of good documentation about Globalscale Technology's [Mirabox][1] so this page is intended to document everything I know about it. My goal is to run a modern kernel and bootloader on the Mirabox.
# | |
# A CORS (Cross-Origin Resouce Sharing) config for nginx | |
# | |
# == Purpose | |
# | |
# This nginx configuration enables CORS requests in the following way: | |
# - enables CORS just for origins on a whitelist specified by a regular expression | |
# - CORS preflight request (OPTIONS) are responded immediately | |
# - Access-Control-Allow-Credentials=true for GET and POST requests |
# | |
# Slightly tighter CORS config for nginx | |
# | |
# A modification of https://gist.github.com/1064640/ to include a white-list of URLs | |
# | |
# Despite the W3C guidance suggesting that a list of origins can be passed as part of | |
# Access-Control-Allow-Origin headers, several browsers (well, at least Firefox) | |
# don't seem to play nicely with this. | |
# |