7rin0

<VirtualHost *:80>
    DocumentRoot "/home/dev/server/project/dist/"
    ServerName vuejs.project.local	

    <Directory /home/dev/server/project/dist/>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride all
    	  Require all granted
        Order allow,deny
    	  allow from all

tanaikech

Remove Third-party Apps with Account Access using Google Apps Script

Overview

This is a method for removing Third-party Apps with Account Access using a script.

Demo

Description

When users create a script in a project and run the script, if the methods which are required to use scopes are included, users have to authorize to use the scopes using the browser. By authorizing it, users can use the script. The authorized projects can be seen at Third-party Apps with Account Access. One day, I had a situation that it required to remove the authorization of project, because of the security. Third-party Apps with Account Access can be manually removed as you know. But at that time, I wanted to remove using a script. So I came up with this method.

soulmachine

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:

apisandipas

Creating share buttons with just URL's

Twitter

http://twitter.com/share?text=<TITLE>&url=<URL>

E.g. http://twitter.com/share?text=This+is+google+a+search+engine&url=https%3A%2F%2Fwww.google.com

Facebook

http://www.facebook.com/sharer.php?u=&p[title]=

parmentf

Inspired by dannyfritz/commit-message-emoji

See also gitmoji.

Commit type	Emoji
Initial commit	🎉 :tada:
Version tag	🔖 :bookmark:
New feature	✨ :sparkles:
Bugfix	🐛 :bug:

JacobBennett

I recently ran into a problem where I had a suite of applications hosted on a set of subdomains that all needed to be able to share a single cookie. Any cookies other than the shared cookie needed to stay specific to their subdomain, but this one shared cookie needed to be accessible to any of them. I also wanted to accomplish this using Laravel's Cookie facade.

The Problem

To accomplish this, there were two issues to solve.

1. All cookies created by the Laravel framework are encrypted by default. (link)
2. I needed to figure out how to set a domain on the shared cookie that was different than the domain it was being set from.

Setting Non-Encrypted Cookies

In Laravel 5.1, a feature was added which allows you to add a list of cookie names that should not be encrypted to the EncryptCookies Middleware under the $except array. Check out [the docs](http://laravel.com/docs/5.1/responses#attaching-cookies

mrliptontea

Sublime Text 3 - Useful Shortcuts (Windows)

General

Shortcut	Description
Ctrl+Shift+P	command prompt
Ctrl+Alt+P	switch project
Ctrl+P	go to file
Ctrl+G	go to line

ahmadazimi

<?php

/**
 * http://stackoverflow.com/questions/11305797/remove-zero-width-space-characters-from-a-javascript-string
 * U+200B zero width space
 * U+200C zero width non-joiner Unicode code point
 * U+200D zero width joiner Unicode code point
 * U+FEFF zero width no-break space Unicode code point
 */