This is inspired by A half-hour to learn Rust and Zig in 30 minutes.
Your first Go program as a classical "Hello World" is pretty simple:
First we create a workspace for our project:
This is inspired by A half-hour to learn Rust and Zig in 30 minutes.
Your first Go program as a classical "Hello World" is pretty simple:
First we create a workspace for our project:
| { | |
| "emojis": [ | |
| {"emoji": "👩👩👧👧", "name": "family: woman, woman, girl, girl", "shortname": ":woman_woman_girl_girl:", "unicode": "1F469 200D 1F469 200D 1F467 200D 1F467", "html": "👩‍👩‍👧‍👧", "category": "People & Body (family)", "order": ""}, | |
| {"emoji": "👩👩👧👦", "name": "family: woman, woman, girl, boy", "shortname": ":woman_woman_girl_boy:", "unicode": "1F469 200D 1F469 200D 1F467 200D 1F466", "html": "👩‍👩‍👧‍👦", "category": "People & Body (family)", "order": ""}, | |
| {"emoji": "👩👩👦👦", "name": "family: woman, woman, boy, boy", "shortname": ":woman_woman_boy_boy:", "unicode": "1F469 200D 1F469 200D 1F466 200D 1F466", "html": "👩‍👩‍👦‍👦", "category": "People & Body (family)", "order": ""}, | |
| {"emoji": "👨👩👧👧", "name": "family: man, woman, girl, girl", "shortname": ":man_woman_girl_girl:", "unicode": "1F468 200D 1F469 200D 1F467 200D 1F467", "html": "👨‍👩&z |
I made a set of helm charts to quickly establish a deepstream system on a kubernetes cluster.
To set up your own deepstream cluster:
helm repo add peardeck-test-charts https://peardeck.github.io/test-charts/
helm fetch peardeck-test-charts/deepstream-nginx-redis
helm install deepstream-nginx-redis-1.0.0.tgz
| #! /bin/bash | |
| SEARCHED=$1 | |
| if [ -z $SEARCHED ]; then | |
| SEARCHED=/api/flights/fares | |
| fi | |
| echo "Protecting $SEARCHED" | |
| echo "Reading:" |
| # To enable rate limiting simply add the following line to the top-level of your config file: | |
| # 1 request / second | |
| limit_req_zone $binary_remote_addr zone=login:10m rate=1r/s; | |
| # Then apply it to a location by adding a rate limiting burst to your server block: | |
| location /account/login/ { | |
| # apply rate limiting | |
| limit_req zone=login burst=5; |
| 'use strict'; | |
| import {Actions} from "react-native-router-flux"; | |
| // var Sinch = require('./Sinch-javascript/sinch-rtc') | |
| import Camera from 'react-native-camera'; | |
| var GiftedMessenger = require('react-native-gifted-messenger'); | |
| var GiftedSpinner = require('react-native-gifted-spinner'); | |
| var React = require('react-native'); | |
| const timer = require('react-native-timer'); | |
| var { | |
| AppRegistry, |
| Stream.unfold({0, 1}, fn {x, y} -> {x, {y, x + y}} end) |
| defmodule Ebid do | |
| import Plug.Conn | |
| def init(options) do | |
| # initialize options | |
| options | |
| end | |
| def call(conn, _opts) do |
via https://www.reddit.com/r/startups/comments/4f74dv/quit_my_full_time_corporate_job_built_an_ios_game/
Publishers are not created equal. It's something I learned very quickly when trying to understand the App Store feature mechanics. If you are Warner Brothers, SquareEnix, Kim Kardashian, King, etc, you get a red carpet to getting featured. You can release whatever trash or shoddy port you want, and you'll get featured. So you have two options, accept this and play by the rules I'm about to lay out, or don't participate.
Here's the list of tips. You really need to do all these things. It's how you show Apple that they can take you seriously as a game developer.
| server { | |
| # ... | |
| # files starting with .dot | |
| # | |
| location ~ /\. { | |
| deny all; |