Scott Yu scootcho

Deploying Parse Server on AWS

Note: this is a work-in-progress and will be updated with more information over the next few days.

Intro

This guide will walk you through deploying your own instance of the open-source Parse Server. This would be a good starting point for testing your existing application to see if the functionality provided by the server is enough for your application, and to potentially plan your migration off the Parse Platform.

This guide will walk you through using Elastic Beanstalk (EB), which is an AWS service similar to Heroku. Why use EB rather than Heroku? Elastic Beanstalk does not lock you into Heroku-specific ways of doing things, is likely cheaper to run your backend on than Heroku, and it integrates with other services that AWS offer (and they offer almost everything one needs to run an application these days).

Dell XPS for Ubuntu 18.04

Bios:

press F12 on the Dell startup screen

disable safe boot
Change SATA Operation from "RAID On" to "AHCI"
Enable Legacy Boot as well as UEFI

Install Ubuntu from USB drive

Instructions are here: https://www.ubuntu.com/download/desktop

Bucket Policy

Bucket policy is an access policy available for you to grant anonymous permissions to your Minio resources. Bucket policy uses JSON-based access policy language.

This section presents a few examples of typical use cases for bucket policies. The policies use testbucket strings in the resource value. To test these policies, you need to replace these strings with your bucket name. For more information please read Amazon S3 access policy language

Granting Read-Only Permission to an Anonymous User

The following example policy grants the s3:GetObject permission to any public anonymous users. This permission allows anyone to read the object data under testbucket, which is useful for when you have publicly readable assets. A typical example is a website assets stored in testbucket.

Current strategy

$  ./zenbot.sh trade gdax.eth-USD --trend_ema 20 -period 7m --max_slippage_pct 0.48 --poll_trades 6000 --order_poll_time 6000 --order_adjust_time 6000 --oversold_rsi_periods=1000 --oversold_rsi=1000 --rsi_periods=1100 --neutral_rate=0.1 --max_sell_loss_pct=0.85 --max_buy_loss_pct=5 --buy_pct=100 --sell_pct=100 --selector gdax.eth-usd  --markup_sell_pct 0.25  --markdown_buy_pct 0.00  --reset-profit

The role of buy & sell percentages (PCT)

Tuning Intel Skylake and beyond for optimal performance and feature level support on Linux:

Note that on Skylake, Kabylake (and the now cancelled "Broxton") SKUs, functionality such as power saving, GPU scheduling and HDMI audio have been moved onto binary-only firmware, and as such, the GuC and the HuC blobs must be loaded at run-time to access this functionality.

Enabling GuC and HuC on Skylake and above requires a few extra parameters be passed to the kernel before boot.

Instructions provided for both Fedora and Ubuntu (including Debian):

Note that the firmware for these GPUs is often packaged by your distributor, and as such, you can confirm the firmware blob's availability by running:

	// code courtesy of Toby team

	chrome.storage.local.get("state", o => (
	((f, t) => {
	let e = document.createElement("a");
	e.setAttribute("href", `data:text/plain;charset=utf-8,${encodeURIComponent(t)}`);
	e.setAttribute("download", f);
	e.click();
	})(`TobyBackup${Date.now()}.json`, o.state)
	));

	#!/usr/bin/env sh
	#i tried it and working like charm just have to note make the file .sh chmod +x and you may need sudo to run with permission but be carefull with sudo
	#be sure the $JAVA_HOME is configure correctly or make it static as commentedline 7 below
	OLDDIR="$PWD"

	if [ -z "$CACERTS_FILE" ]; then
	# you should have java home configure to point for example /usr/lib/jvm/default-java/jre/lib/security/cacerts
	CACERTS_FILE=$JAVA_HOME/jre/lib/security/cacerts
	fi

	packages:
	yum:
	git: []
	gcc: []
	make: []
	openssl-devel: []
	ImageMagick: []

	option_settings:
	- option_name: NODE_ENV

	'use strict';
	/*
	CUSTOM METHODS TO EXTEND ORM
	*/
	module.exports = {

	/*
	var instance = new orm.bulkUpsert({
	knex: knex,
	model: 'modelName',

	{
	"USD": {
	"symbol": "$",
	"name": "US Dollar",
	"symbol_native": "$",
	"decimal_digits": 2,
	"rounding": 0,
	"code": "USD",
	"name_plural": "US dollars"
	},