This is an example of how to use the Google Drive file picker and Google Drive API to retrieve files from Google Drive using pure JavaScript. At the time of writing (14th July 2013), Google have good examples for using these two APIs separately, but no documentation on using them together.
Note that this is just sample code, designed to be concise to demonstrate the API. In a production environment, you should include more error handling.
See a demo at http://stuff.dan.cx/js/filepicker/google/
| sudo apt-get update | |
| sudo apt-get install python-virtualenv | |
| sudo apt-get install python-dev | |
| sudo apt-get install postgresql | |
| sudo apt-get install postgresql-server-dev-9.3 | |
| sudo apt-get install redis-server | |
| sudo -u postgres createuser -s sentry | |
| sudo -u postgres psql -c "alter user sentry with password 'sentry';" |
| server { | |
| listen 80; ## listen for ipv4; this line is default and implied | |
| listen [::]:80 default ipv6only=on; ## listen for ipv6 | |
| root /usr/share/nginx/www; | |
| index index.php index.html index.htm; | |
| # Make site accessible from http://localhost/ | |
| server_name _; |
| /* | |
| This script, when used with Google Apps Scripts, will delete 400 emails and | |
| can be triggered to run every few minutes without user interaction enabling you | |
| to bulk delete email in Gmail without getting the #793 error from Gmail. | |
| Google returns a maximum of 500 email threads in a single API call. | |
| This script fetches 400 threads in case 500 threads is causing timeouts | |
| Configure the search query in the code below to match the type of emails | |
| you want to delete |
This is a small write up about how to migrate your pritunl install between servers. It's not especially detailed because I'm lazy and your migration story will most likely be different. All this can be avoided by using a remote/hosted mongo instance(compose.io, mongolab, etc.) and simply pointing your pritunl instance at that. If you want more details ask, and I'll do my best to answer and update this write-up accordingly. Also, feel free to criticize my grammar and spelling.
In this short tutorial I will show you a (kind of hacky, but working) option to set up your koel instance so that you can store your media files on S3 as provided by Amazon. I will also share some of the insights and experiences I had with the setup. Be aware that it's not officially supported and it might work differently to from what you expect. I myself have not had the setup running for a very long time yet. Feel free to share your thoughts in the comments below or add to the document.
If you feel like supporting me, maybe use my Digital Ocean referral link when signing up. If you do that, please also support the original authors of the various tools. They did the hard work, I just glued it together.
| namespace App\Http\Middleware; | |
| use Illuminate\Support\Facades\Log; | |
| class LogAfterRequest { | |
| public function handle($request, \Closure $next) | |
| { | |
| return $next($request); | |
| } |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>GridLayer Test</title> | |
| <meta charset="utf-8" /> | |
| <link rel="stylesheet" href="https://unpkg.com/[email protected]/dist/leaflet.css" /> | |
| <style> | |
| body { | |
| padding: 0; | |
| margin: 0; |
| <?php | |
| //disable execution time limit when downloading a big file. | |
| set_time_limit(0); | |
| /** @var \League\Flysystem\Filesystem $fs */ | |
| $fs = Storage::disk('local')->getDriver(); | |
| $fileName = 'bigfile'; | |
| $metaData = $fs->getMetadata($fileName); |
