thanhleviet

Tested on nginx version 1.1.9, ubuntu 12.04
-Command lines in order:
sudo touch /etc/nginx/site-availables/geoserver.conf
sudo vi /etc/nginx/site-availables/geoserver.conf
sudo ln -s /etc/nginx/site-availables/geoserver.conf /etc/nginx/site-enabled/geoserver.conf
sudo service nginx start

Content of geoserver.conf

server {

plentz

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

tcjr

// The API accepts the page parameter and returns the pagination info in meta

{
  "messages": [ ... ],
  "meta": {
    "pagination": {
      "total_pages": 3,
      "current_page": 1,
      "total_count": 55
    }

trbngr

import { GraphQLScalarType } from 'graphql';
import { GraphQLError } from 'graphql/error';
import { Kind } from 'graphql/language';
import moment from 'moment';
import tz from 'moment-timezone';

function coerceDate(value) {

    if(typeof value === 'string')
        value = moment(value);

dbismut

export function actionTypeBuilder(prefix) {
  return {
    type: actionType => `${prefix}/${actionType}`,
    loading: actionType => `${actionType}/loading`,
    ready: actionType => `${actionType}/ready`,
    stopped: actionType => `${actionType}/stopped`,
    changed: actionType => `${actionType}/changed`,
    error: actionType => `${actionType}/error`,
    success: actionType => `${actionType}/success`
  };

brendanvinson

/*
First run npm install topojson --save and then link "node_modules/topojson/build/topojson.min.js" 
above this snippet in your html.

Usage: http://leafletjs.com/reference.html#geojson
*/

L.TopoJSON = L.GeoJSON.extend({
    addData: function (data) {
        var geojson, key;

mpneuried

# import config.
# You can change the default config with `make cnf="config_special.env" build`
cnf ?= config.env
include $(cnf)
export $(shell sed 's/=.*//' $(cnf))

# import deploy config
# You can change the default deploy config with `make cnf="deploy_special.env" release`
dpl ?= deploy.env
include $(dpl)

samsch

Stop using JWTs!

TLDR: JWTs should not be used for keeping your user logged in. They are not designed for this purpose, they are not secure, and there is a much better tool which is designed for it: regular cookie sessions.

If you've got a bit of time to watch a presentation on it, I highly recommend this talk: https://www.youtube.com/watch?v=pYeekwv3vC4 (Note that other topics are largely skimmed over, such as CSRF protection. You should learn about other topics from other sources. Also note that "valid" usecases for JWTs at the end of the video can also be easily handled by other, better, and more secure tools. Specifically, PASETO.)

A related topic: Don't use localStorage (or sessionStorage) for authentication credentials, including JWT tokens: https://www.rdegges.com/2018/please-stop-using-local-storage/

The reason to avoid JWTs comes down to a couple different points:

• The JWT specification is specifically designed only for very short-live tokens (~5 minute or less). Sessions

JoelQ

#!/bin/sh

set -e

echo "== BUILDING THE APP =="
yarn parcel build src/index.html

echo "== CONFIGURING REDIRECTS  =="
if [ "$CONTEXT" = "production" ]; then
  cp production_redirects dist/_redirects

filipenevola

/**
Snippets showing how to configure Apollo with Meteor in two different ways:
1 - Using DDP (websocket connection)
2 - Using HTTP (post requests)

I'm using a regular HTTP post approach when isAPIModule() returns true 
and DDP approach when returns false. I control isAPIModule changing
a setting in the deployment settings.json

That is not necessary for almost every application but in my case I have