Edit — best to first try:
mariadb-secure-installation -u $(whoami)
Original version here below in case the above does not work for you.
Edit — best to first try:
mariadb-secure-installation -u $(whoami)
Original version here below in case the above does not work for you.
#!/usr/bin/env bash | |
# Recursively remove all special characters from filenames by renaming them to their ASCII normalized forms. | |
# | |
# By default it does a dry run, to actually move the files uncomment the `mv -vi ...` line. | |
# | |
# This is useful for cleaning up network shares that will be shared via SMB/NFS between Unix/macOS/Windows | |
# where non-ASCII filenames can sometimes cause "file does not exist" errors when trying to access the files. | |
# | |
# This script removes leading/trailing whitespace in filenames and replaces accents and non-english | |
# characters with their ASCII equivalent, if no ASCII equivalent exists, it removes the character e.g.: |
#!/usr/bin/env bash | |
readonly TOKEN=YOUR_APP_TOKEN | |
readonly DIR=/YOUR_DIR_PATH | |
FILE=$1 | |
BASENAME=$(basename $FILE) | |
if [ -f "$FILE" ]; then |
#!/bin/bash -x | |
#Date: 21/7/2017 | |
#Author: Mohan | |
#Purpose: To upload files to AWS S3 via Curl | |
#Uploads file at the top level folder by default | |
#S3 parameters | |
S3KEY="XXXXXXXXXXX" | |
S3SECRET="XXXXXXXXXXXXXXXX" |
Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.
It sometimes happen you need change code on a machine from which you cannot push to the repo.
You’re ready to copy/paste what diff
outputs to your local working copy.
You think there must be a better way to proceed and you’re right. It’s a simple 2 steps process:
1. Generate the patch:
git diff > some-changes.patch
Adyen Test Card Numbers | |
These cards are only valid on our TEST system and they will never involve any actual transaction or transfer of funds. The TEST card numbers will not work on the Adyen LIVE Platform. | |
For all cards use the following expiration and CVV2/CVC2/or CID for Amex. | |
For all cards: | |
Expiration Dates CVV2 / CVC3 CID (American Express) | |
08/2018 OR 10/2020 737 7373 |