- Batman: Año Uno (1987)
- El Hombre Que Cae (1989)
- Catwoman, Her Sister’s Keeper (1989)
- Batman: Año Dos (1987)
- El Caso del Sindicato Químico (1939)
- Batman y los Hombres Monstruo (2007)
- Presa (1990)
- Batman y el Monje Loco (2007)
- El Hombre Que Ríe (2005)
curl -I -X OPTIONS \ | |
-H "Origin: http://EXAMPLE.COM" \ | |
-H 'Access-Control-Request-Method: GET' \ | |
http://EXAMPLE.COM/SOMETHING 2>&1 | grep 'Access-Control-Allow-Origin' |
const onDrop = useCallback((acceptedFiles) => { | |
const file = acceptedFiles.find(f => f) | |
const i = new Image() | |
i.onload = () => { | |
let reader = new FileReader() | |
reader.readAsDataURL(file) | |
reader.onload = () => { | |
console.log({ | |
src: file.preview, |
Tiny wrapper component for React-Datepicker to stylistically fit with Chakra-UI 1.x.
<DatePicker selectedDate={myDate} onChange={(d) => console.log(d)} />
Clearable version:
<DatePicker selectedDate={myDate} onChange={(d) => console.log(d)} isClearable={true} />
diff --git a/node_modules/@chakra-ui/toast/dist/esm/toast-manager.js b/node_modules/@chakra-ui/toast/dist/esm/toast-manager.js | |
index f64ed90..af3e367 100644 | |
--- a/node_modules/@chakra-ui/toast/dist/esm/toast-manager.js | |
+++ b/node_modules/@chakra-ui/toast/dist/esm/toast-manager.js | |
@@ -119,9 +119,18 @@ export class ToastManager extends React.Component { | |
var position = getToastPosition(prevState, id); | |
if (!position) return prevState; | |
return _extends({}, prevState, { | |
- [position]: prevState[position].map(toast => _extends({}, toast, { | |
- requestClose: toast.id === id ? true : toast.requestClose |
$ adb kill-server
$ sudo cp ~/Android/Sdk/platform-tools/adb /usr/bin/adb
$ sudo chmod +x /usr/bin/adb
$ adb start-server
{ | |
"particles": { | |
"number": { | |
"value": 80, | |
"density": { | |
"enable": true, | |
"value_area": 800 | |
} | |
}, | |
"color": { |
const imageData = [ 'image1.png', 'img2.png', 'img3.png' ]; | |
const currentImage = 0; | |
const handleImageChange = (direction) => { | |
if (direction == 'forward') | |
currentImage = (currentImage + 1) % imageData.length; | |
else | |
currentImage = (currentImage - 1 + imageData.length) % imageData.length; | |
} |
source: https://savedlog.com/uncategorized/letsencrypt-ssl-certificate-namecheap-hosting/
The “Positive SSL” certificate I bought along with my domain is invalid with any of my subdomains and cannot be used with wildcards. One annoying thing is that namecheap doesn’t offer auto installation of free let’s encrypt certificates, even though, they are saying “Namecheap is dedicated to data security and privacy for all internet users. We believe the movement to encrypt nearly all web traffic is a positive direction. As more sites embrace HTTPS and use of security products, providers of free SSL are beginning to come online.”
Let me show you what it needs to be done in order to “encrypt nearly all web traffic”.
First, not required but it’s helpful to enable ssh access, it is not enabled by default on the base hosting plans, just go an start a live chat and request ssh access.