Changes with .dev
domains in
mind.
Step 1 : Assign at least two IP address to your MAC OS (one per domain), let's say :
192.168.0.51
192.168.0.52
To setup the second IP you will have to add a second Ethernet Adapter (logical not physical).
Changes with .dev
domains in
mind.
Step 1 : Assign at least two IP address to your MAC OS (one per domain), let's say :
192.168.0.51
192.168.0.52
To setup the second IP you will have to add a second Ethernet Adapter (logical not physical).
import React, { useState, useEffect } from 'react' | |
//i'm using react-bootstrap for UI elements | |
import { Table, Button, ButtonGroup } from "react-bootstrap"; | |
//firebase config | |
import firebase from './../../Firebase' | |
export default function App() { | |
const [list, setList] = useState([]); | |
const [page, setPage] = useState(1); |
# This is a sample build configuration for PHP. | |
# Check our guides at https://confluence.atlassian.com/x/e8YWN for more examples. | |
# Only use spaces to indent your .yml configuration. | |
# ----- | |
# You can specify a custom docker image from Docker Hub as your build environment. | |
image: php:7.1.29 | |
pipelines: | |
default: | |
- step: | |
name: Deploy to dev |
<!doctype html> | |
<html ⚡4email> | |
<head> | |
<meta charset="utf-8"> | |
<script async src="https://cdn.ampproject.org/v0.js"></script> | |
<script async custom-element="amp-bind" src="https://cdn.ampproject.org/v0/amp-bind-0.1.js"></script> | |
<script async custom-element="amp-carousel" src="https://cdn.ampproject.org/v0/amp-carousel-0.1.js"></script> | |
<style amp4email-boilerplate>body{visibility:hidden}</style> | |
<style amp-custom> |
exFAT support on macOS seems to have some bugs because my external drives with exFAT formatting will randomly get corrupted.
Disk Utility is unable to repair this at first, but the fix is this:
diskutil list
to find the right drive id.disk1s1
sudo fsck_exfat -d <id from above>
. eg sudo fsck_exfat -d disk1s3
-d
is debug so you'll see all your files output as they're processed.YES
if it gives you the prompt Main boot region needs to be updated. Yes/No?
#!/bin/sh | |
PROJECT=`php -r "echo dirname(dirname(dirname(realpath('$0'))));"` | |
STAGED_FILES_CMD=`git diff --cached --name-only --diff-filter=ACMR HEAD | grep \\\\.php` | |
# Determine if a file list is passed | |
if [ "$#" -eq 1 ] | |
then | |
oIFS=$IFS | |
IFS=' |
{ | |
"key_events": { | |
"key_unknown": "adb shell input keyevent 0", | |
"key_soft_left": "adb shell input keyevent 1", | |
"key_soft_right": "adb shell input keyevent 2", | |
"key_home": "adb shell input keyevent 3", | |
"key_back": "adb shell input keyevent 4", | |
"key_call": "adb shell input keyevent 5", | |
"key_endcall": "adb shell input keyevent 6", | |
"key_0": "adb shell input keyevent 7", |
git log --graph --oneline --decorate ( git fsck --no-reflog | awk '/dangling commit/ {print $3}' )
This will show you all the commits at the tips of your commit graph which are no longer referenced from any branch or tag – every lost commit, including every stash commit you’ve ever created, will be somewhere in that graph.
adb help // List all comands | |
== Adb Server | |
adb kill-server | |
adb start-server | |
== Adb Reboot | |
adb reboot | |
adb reboot recovery | |
adb reboot-bootloader |
Commonly, npm modules are source controlled using a single dedicated repo for each module. When forking and patching such an existing npm module, typical approaches are either:
"dependencies": {
"patchedmodule": "git+https://github.com/myuser/patchedmodule.git#mypatch"
}