rictorres

JavaScript to Rust Cheat Sheet

The goal of this is to have an easily-scannable reference for the most common syntax idioms in JavaScript and Rust so that programmers most comfortable with JavaScript can quickly get through the syntax differences and feel like they could read and write basic Rust programs.

What do you think? Does this meet its goal? If not, why not?

Variables

JavaScript:

rictorres

How to setup Let's Encrypt for Nginx on Ubuntu 18.04 (including IPv6, HTTP/2 and A+ SSL rating)

---

Virtual hosts

Let's say you want to host domains first.com and second.com.

Create folders for their files:

rictorres

3rd-party image processing/manipulation services

• http://www.imgix.com/
• http://cloudinary.com/
• http://www.cdnconnect.com/
• http://cloudresize.com/
• http://cloudimage.io/
• http://www.blitline.com/

rictorres

'use strict';

var mysqlBackup  = require('./mysql-backup');
var schedule     = require('node-schedule');

schedule.scheduleJob({ hour: 22, minute: 0 }, mysqlBackup);

rictorres

Keen.configure(window.ENV.keenProjectId,window.ENV.keenApiKey),
 
Keen.onChartsReady(function(){
       var e=new Keen.Series("connect",{
               analysisType:"count",
               timeframe:"last_7_days",
               interval:"daily"
       }),
 
       t=new Keen.Series("connect",{

rictorres

# to generate your dhparam.pem file, run in the terminal
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048

rictorres

Setting up a SSL Cert from Comodo

I use Namecheap.com as a registrar, and they resale SSL Certs from a number of other companies, including Comodo.

These are the steps I went through to set up an SSL cert.

Purchase the cert

rictorres

Nginx FastCGI response buffer sizes

By default when Nginx starts receiving a response from a FastCGI backend (such as PHP-FPM) it will buffer the response in memory before delivering it to the client. Any response larger than the set buffer size is saved to a temporary file on disk. This process is also explained at the Nginx ngx_http_fastcgi_module page document page.

Since disk is slow and memory is fast the aim is to get as many FastCGI responses passing through memory only. On the flip side we don't want to set an excessively large buffer as they are created and sized on a per request basis (it's not shared).

The related Nginx options are:

• fastcgi_buffering appeared in Nginx 1.5.6 (1.6.0 stable) and can be used to turn buffering completely on/off. It's on by default.
• [fastcgi_buffer_size](http://nginx.org/en/docs/http/ngx_ht

rictorres

 http {
    proxy_cache_path  /var/cache/nginx levels=1:2 keys_zone=one:8m max_size=3000m inactive=600m;
    proxy_temp_path /var/tmp;
    include       mime.types;
    default_type  application/octet-stream;
    sendfile        on;
    keepalive_timeout  65;

    gzip on;
    gzip_comp_level 6;

rictorres

// This is from my comment here: http://wolfram.kriesing.de/blog/index.php/2008/javascript-remove-element-from-array/comment-page-2#comment-466561

/*
 * How to delete items from an Array in JavaScript, an exhaustive guide
 */

// DON'T use the delete operator, it leaves a hole in the array:
var arr = [4, 5, 6];
delete arr[1]; // arr now: [4, undefined, 6]