hrvoj3e

## PHP 7.3
apt update
apt install software-properties-common
apt-add-repository ppa:ondrej/php
apt install yaz libyaz5-dev
apt install php7.3-dev php7.3 php7.3-fpm
pecl channel-update pecl.php.net
pecl install yaz
  ## Installing '/usr/lib/php/20180731/yaz.so'
  ## install ok: channel://pecl.php.net/yaz-1.2.3

hrvoj3e

openapi: 3.0.2
info:
  title: demo
  version: 1.0.0
  description: ''
paths:
  /demo:
    get:
      parameters: 
        - in: query

hrvoj3e

    location /my-subfolder/ {
        # Forward incoming requests to local tusd instance
        proxy_pass http://192.168.54.111:8472/;
        proxy_redirect ~/files/(.*)$ $scheme://$host/my-subfolder/files/$1;

        # Disable request and response buffering
        proxy_request_buffering  off;
        proxy_buffering          off;
        proxy_http_version       1.1;

hrvoj3e

<?php

namespace App\Providers;

use App\Auth\UserProvider;
use Illuminate\Foundation\Support\Providers\AuthServiceProvider as ServiceProvider;

class AuthServiceProvider extends ServiceProvider
{
    /**

hrvoj3e

upstream phpfpm {
    #server unix:/var/run/php5-fpm.sock;
    #avoid sockets for nginx-fpm on Linux, they are good for BSD
    server 127.0.0.1:9000;
}

server {
    listen 8080;
    server_name sumhr.com;
    rewrite ^(.*) $scheme://www.sumhr.com$1 permanent;

hrvoj3e

Interface bonding

Configure an LACP active network interface bonding on Ubuntu 18.04 using netplan:

root@srv01:~# mv /etc/netplan/50-cloud-init.yaml /etc/netplan/01-netcfg.yaml
root@srv01:~# cat /etc/netplan/01-netcfg.yaml 
network:
    version: 2
    renderer: networkd
 ethernets:

hrvoj3e

version: '3.7'

services:
  whoami:
    image: jwilder/whoami

    ports:
      - 127.0.0.1:7000:8000

  cors:

hrvoj3e

<?php

namespace Core\UserBundle\Controller;

use Symfony\Bundle\FrameworkBundle\Controller\Controller;
use Symfony\Component\HttpFoundation\Request;

class SecurityController extends Controller
{
    public function loginAction(Request $request)

hrvoj3e

First of all, please note that token expiration and revoking are two different things.

1. Expiration only happens for web apps, not for native mobile apps, because native apps never expire.
2. Revoking only happens when (1) uses click the logout button on the website or native Apps;(2) users reset their passwords; (3) users revoke their tokens explicitly in the administration panel.

1. How to hadle JWT expiration

A JWT token that never expires is dangerous if the token is stolen then someone can always access the user's data.

Quoted from JWT RFC:

hrvoj3e

Keybase proof

I hereby claim:

• I am hrvoj3e on github.
• I am hrvoj3e (https://keybase.io/hrvoj3e) on keybase.
• I have a public key ASCouDrOYVr7vbfxwRQatfK00eIaLr07bFnUYfPSHn131Ao

To claim this, I am signing this object: