download and install Solr from http://lucene.apache.org/solr/.
you can access Solr admin from your browser: http://localhost:8983/solr/
use the port number used in installation.
download and install Solr from http://lucene.apache.org/solr/.
you can access Solr admin from your browser: http://localhost:8983/solr/
use the port number used in installation.
| 'use strict'; | |
| var EventEmitter = require('events').EventEmitter; | |
| var httpMocks = require('node-mocks-http'); | |
| module.exports = { | |
| createRequest: httpMocks.createRequest.bind(httpMocks), | |
| createResponse: function (opts) { | |
| opts = opts || {}; | |
| opts.eventEmitter = EventEmitter; |
xdebug.ini file).xdebug.trace_output_dir is writable by the webserver user (www-data).produce_segmentation.php to test.xdebug.trace_output_dir.| #!/usr/bin/env node | |
| var fs = require('fs'); | |
| var args = fs.readFileSync(process.argv[2], 'utf8'); | |
| var changed = false; | |
| var jsonPath = null; | |
| var json = null; | |
| var keyValReplacementString = args.split(' '); | |
| keyValReplacementString.forEach(function(i){ |
If you're aiming for a seamless Arch Linux installation in UEFI mode, follow along as this guide will walk you through the process step by step. We'll be using LUKS (Linux Unified Key Setup) and LVM (Logical Volume Manager) partitions on LUKS to achieve full disk encryption.
Note: I have updated this doc for UEFI mode. For those with BIOS/MBR systems, you can refer to the previous version, but keep in mind that it might be outdated and no longer accurate.
If you're only interested in installing Linux and not setting up dual boot with Windows, feel free to skip the Windows-related sections.
| digraph architecture { | |
| rankdir=LR; | |
| // Storage - #303F9F (dark blue) | |
| node[fillcolor="#303F9F" style="filled" fontcolor="white"]; | |
| database[label="DB"]; cache[label="Redis"]; | |
| // Client-side Apps - #FFEB3B (yellow) | |
| node[fillcolor="#FFEB3B" style="filled" fontcolor="black"]; | |
| front_end[label="Front-end App"]; extension[label="Browser Extension"]; |
Info: https://www.nginx.com/resources/admin-guide/nginx-https-upstreams/
Source: http://nategood.com/client-side-certificate-authentication-in-ngi
This is SSL, so you'll need an cert-key pair for you/the server, the api users/the client and a CA pair. You will be the CA in this case (usually a role played by VeriSign, thawte, GoDaddy, etc.), signing your client's certs. There are plenty of tutorials out there on creating and signing certificates, so I'll leave the details on this to someone else and just quickly show a sample here to give a complete tutorial. NOTE: This is just a quick sample of creating certs and not intended for production.
| # Generate the private and public keys | |
| openssl ecparam -name secp256k1 -genkey -noout | openssl ec -text -noout > key | |
| # Extract the public key and remove the EC prefix 0x04 | |
| cat key | grep pub -A 5 | tail -n +2 | tr -d '\n[:space:]:' | sed 's/^04//' > pub | |
| # Extract the private key and remove the leading zero byte | |
| cat key | grep priv -A 3 | tail -n +2 | tr -d '\n[:space:]:' | sed 's/^00//' > priv | |
| # Generate the hash and take the address part |
This is a compiled list of falsehoods programmers tend to believe about working with time.
Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.