- have fun with them
- projections
- filters
- resource-keys
- scripting-gcloud
- gcloud alpha interactive
- https://medium.com/@Joachim8675309/getting-started-with-gcloud-sdk-part-1-114924737
- https://medium.com/@Joachim8675309/getting-started-with-gcloud-sdk-part-2-4d049a656f1a
- https://gist.github.com/bborysenko/97749fe0514b819a5a87611e6aea3db8
| import zmq | |
| from flask import Flask | |
| from threading import Thread | |
| HOST = '127.0.0.1' | |
| PORT = 9090 | |
| TASK_SOCKET = zmq.Context().socket(zmq.REQ) | |
| TASK_SOCKET.connect('tcp://{}:{}'.format(HOST, PORT)) | |
| app = Flask("app") |
| // See https://github.com/dialogflow/dialogflow-fulfillment-nodejs | |
| // for Dialogflow fulfillment library docs, samples, and to report issues | |
| 'use strict'; | |
| const functions = require('firebase-functions'); | |
| const {WebhookClient} = require('dialogflow-fulfillment'); | |
| const {Card, Suggestion} = require('dialogflow-fulfillment'); | |
| process.env.DEBUG = 'dialogflow:debug'; // enables lib debugging statements | |
@credit Yan Zhu (https://github.com/nina-zhu)
Before you start this guide, you should run through the "How To Serve Flask Applications with uWSGI and Nginx on Ubuntu 14.04" guide. This is necessary in order to set up virtualenv, uWSGI and Nginx. In that guide, we developed a very simple flask application having just 1 file "firstflask.py" with only 9 lines of code, it is a sample for showing you the general steps. In this guide, we will create a complete user session listing application, with login, logout functionality. We will use MariaDB to store the users records, and use Redis to store the session data and background tasks.
Let's get started.
| n02119789 1 kit_fox | |
| n02100735 2 English_setter | |
| n02110185 3 Siberian_husky | |
| n02096294 4 Australian_terrier | |
| n02102040 5 English_springer | |
| n02066245 6 grey_whale | |
| n02509815 7 lesser_panda | |
| n02124075 8 Egyptian_cat | |
| n02417914 9 ibex | |
| n02123394 10 Persian_cat |
Here at Glitterbug Tech, Django is the lifeline of everything we make and we are big fans! Django doesn't get in the way and lets us write the language we love, python, while providing an amazing set of tools that makes creating web applications fast and fun. But, as you know, code is executed synchronously before you can send back a response. Which means when you are generating that report from your database which has a million rows, your client has to wait for a response while your application huffs and puffs trying to get everything ready (Unless he times out, in which case you receive angry calls while you try to explain what "502 Bad Gateway" means). Sometimes you just want to make your site more responsive by pushing time consuming tasks in the background ("Your comment has been posted!" while a zmq process works in the backend adding it to your db/caching layer/pushing it to followers/creating rainbows). Wha