Create new migration script:
php artisan make:migration add_api_token --table=users| #!/usr/bin/env bash | |
| rm -rf "${HOME}/Library/Caches/CocoaPods" | |
| rm -rf "`pwd`/Pods/" | |
| pod update |
| <html> | |
| <div id="product_name">Kacamata</div> | |
| <div id="product_group">Fashion</div> | |
| <div id="product_id">10</div> | |
| <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script> | |
| <script language="JavaScript"> | |
| var product_id = $('#product_id').text() | |
| var product_name = $('#product_name').text() | |
| var product_group = $('#product_group').text() | |
| var phone = ['6281312020954','6281312020941','6281312020938'] |
| import java.awt.Color; | |
| import java.awt.Graphics; | |
| import java.awt.Point; | |
| import java.awt.event.KeyEvent; | |
| import java.awt.event.KeyListener; | |
| import java.util.ArrayList; | |
| import java.util.Collections; | |
| import javax.swing.JFrame; | |
| import javax.swing.JPanel; |
If you're doing stuff with Ruby on a Mac, e.g. installling Jekyll or something, by default you'll end up having to use the sudo command to do stuff, since the permission to modify the default config is not available to your user account.
This sucks and should be avoided. Here's how to fix that.
To make this better, we are going install a new, custom Ruby. This used to be a big, scary thing, but thanks to the awesome tools Homebrew and rbenv, it's a snap.*
A word of warning: you will have to use Terminal to install this stuff. If you are uncomfortable with text, words, and doing stuff with your computer beyond pointing and hoping, this may not work well for you. But if that's the case, I'm not sure why you were trying to use Ruby in the first place.
| DRONE_HOST=https://loc-drone-ci.localtunnel.me | |
| DRONE_GITHUB_CLIENT=af516d1889d283a6a30d | |
| DRONE_GITHUB_SECRET=64994dabf745bc5076734aeff4cb41cd268782f8 | |
| DRONE_SECRET=drone-local-bla-bla-bla |
RDBMS-based job queues have been criticized recently for being unable to handle heavy loads. And they deserve it, to some extent, because the queries used to safely lock a job have been pretty hairy. SELECT FOR UPDATE followed by an UPDATE works fine at first, but then you add more workers, and each is trying to SELECT FOR UPDATE the same row (and maybe throwing NOWAIT in there, then catching the errors and retrying), and things slow down.
On top of that, they have to actually update the row to mark it as locked, so the rest of your workers are sitting there waiting while one of them propagates its lock to disk (and the disks of however many servers you're replicating to). QueueClassic got some mileage out of the novel idea of randomly picking a row near the front of the queue to lock, but I can't still seem to get more than an an extra few hundred jobs per second out of it under heavy load.
So, many developers have started going straight t
| #!/bin/bash | |
| ################################################################################ | |
| # Rather than run postgres in its own container, we want to run it on | |
| # the (Ubuntu) host and allow: | |
| # | |
| # + peer connections on the host | |
| # + local md5 connections from any docker container | |
| # | |
| # THIS IS COPY/PASTED FROM COMMAND LINE INPUT AND IS UNTESTED AS A SINGLE SCRIPT | |
| ################################################################################ |