As configured in my dotfiles.
start new:
tmux
start new with session name:
As configured in my dotfiles.
start new:
tmux
start new with session name:
# delete local tag '12345' | |
git tag -d 12345 | |
# delete remote tag '12345' (eg, GitHub version too) | |
git push origin :refs/tags/12345 | |
# alternative approach | |
git push --delete origin tagName | |
git tag -d tagName |
When hosting our web applications, we often have one public IP
address (i.e., an IP address visible to the outside world)
using which we want to host multiple web apps. For example, one
may wants to host three different web apps respectively for
example1.com
, example2.com
, and example1.com/images
on
the same machine using a single IP address.
How can we do that? Well, the good news is Internet browsers
from locust import HttpLocust, TaskSet, task | |
class MostBasicLoadTest(TaskSet): | |
def on_start(self): | |
""" on_start is called when a Locust start before any task is scheduled """ | |
self.login() | |
def login(self): | |
self.client.post("/api/api-token-auth/", | |
{ |
<script type="text/javascript" src="https://stc.pagseguro.uol.com.br/pagseguro/api/v2/checkout/pagseguro.directpayment.js"></script> | |
<script type="text/javascript"> | |
var paymentModule = 'pagseguro_app'; | |
checkoutCallbacks.add(pagseguroCheckout); | |
function pagseguroCheckout() { | |
if ($('input[name=module]').val() == paymentModule) { |
INSERT INTO `bancos` (`cod`, `banco`) VALUES (001,'001 - BANCO DO BRASIL S/A'); | |
INSERT INTO `bancos` (`cod`, `banco`) VALUES (002,'002 - BANCO CENTRAL DO BRASIL'); | |
INSERT INTO `bancos` (`cod`, `banco`) VALUES (003,'003 - BANCO DA AMAZONIA S.A'); | |
INSERT INTO `bancos` (`cod`, `banco`) VALUES (004,'004 - BANCO DO NORDESTE DO BRASIL S.A'); | |
INSERT INTO `bancos` (`cod`, `banco`) VALUES (007,'007 - BANCO NAC DESENV. ECO. SOCIAL S.A'); | |
INSERT INTO `bancos` (`cod`, `banco`) VALUES (008,'008 - BANCO MERIDIONAL DO BRASIL'); | |
INSERT INTO `bancos` (`cod`, `banco`) VALUES (020,'020 - BANCO DO ESTADO DE ALAGOAS S.A'); | |
INSERT INTO `bancos` (`cod`, `banco`) VALUES (021,'021 - BANCO DO ESTADO DO ESPIRITO SANTO S.A'); | |
INSERT INTO `bancos` (`cod`, `banco`) VALUES (022,'022 - BANCO DE CREDITO REAL DE MINAS GERAIS SA'); | |
INSERT INTO `bancos` (`cod`, `banco`) VALUES (024,'024 - BANCO DO ESTADO DE PERNAMBUCO'); |
This page provides a full overview of PHP's SessionHandler
life-cycle - this was generated by a set of test-scripts, in order to provide an exact overview of when and
what you can expect will be called in your custom SessionHandler
implementation.
Each example is a separate script being run by a client with cookies enabled.
To the left, you can see the function being called in your script, and to the right, you can see the resulting calls being made to a custom session-handler registed using session_set_save_handler().
<?php | |
/** | |
* simple method to encrypt or decrypt a plain text string | |
* initialization vector(IV) has to be the same when encrypting and decrypting | |
* | |
* @param string $action: can be 'encrypt' or 'decrypt' | |
* @param string $string: string to encrypt or decrypt | |
* | |
* @return string | |
*/ |