I hereby claim:
- I am fisadev on github.
- I am fisadev (https://keybase.io/fisadev) on keybase.
- I have a public key ASACr4B1E9t_KTdx562nHWZHfyyZxlthCjtbyyeArEtNjAo
To claim this, I am signing this object:
# python (flask) side: | |
import time | |
from flask import Response | |
app = Flask(__name__) | |
@app.route('/event_stream') | |
def stream(): | |
def event_stream(): |
I hereby claim:
To claim this, I am signing this object:
[general] | |
accounts = GMail | |
maxsyncaccounts = 3 | |
[Account GMail] | |
localrepository = Local | |
remoterepository = Remote | |
autorefresh = 5 | |
quick = 5 |
#!/usr/bin/env python | |
# coding: utf-8 | |
from os import system | |
PROJECT_PATH = 'path_to_your_project' | |
ACTIVATE_VENV = '. path_to_your_virtualenv/bin/activate' | |
def tmux(command): |
# based on the permission_required decorator, from django.contrib.auth | |
from django.contrib.auth.decorators import user_passes_test | |
from django.core.exceptions import PermissionDenied | |
def group_required(group_name, login_url=None, raise_exception=False): | |
""" | |
Decorator for views that checks whether a user belongs to a particular | |
group, redirecting to the log-in page if necessary. | |
If the raise_exception parameter is given the PermissionDenied exception |
Hi!
In 2018 Github Pages announced support for custom domains with HTTPS: https://github.blog/2018-05-01-github-pages-custom-domains-https/
This meant that Github had to generate certs which pointed to the custom domains the users were configuring for their pages. This worked perfectly until a few weeks ago, when all certs started to point to the default domains instead of the custom domains.
That bug breaks all the Github Pages that were using custom domains and HTTPS, because most browsers (Chrome, Firefox, Safari) now block access via HTTPS, warning the users that the sites are insecure and could steal info, etc.
# usage: | |
# e --> create and/or activate a virtualenv, named in a way that's unique and related to the current folder | |
# but stored under ~/venvs/ | |
# e NAME --> create and/or activate a virtualenv with the specified name, stored under ~/venvs/ | |
# you should replace `\/home\/fisa\/devel\/` (scaped text for `/home/fisa/devel/`) with the folder in which most | |
# of your projects live, so a venv for a project /home/fisa/devel/company_x/project_y/ will be named just | |
# "company_x_project_y", without the full path as part of the name. It's kind of a default prefix. | |
function e |
javascript:(function(){var currentUrl=window.location.href;if(currentUrl.startsWith("https://us02web.zoom.us/j/")){var newUrl=currentUrl.replace("https://us02web.zoom.us/j/","https://zoom.us/wc/join/");window.location.href=newUrl;}else{alert("This URL does not match the expected Zoom pattern.");}})(); |