#Web scrapers on the internet
See this repo to contribute/see more: https://github.com/cassidoo/scrapers
diff --git a/index.html b/index.html | |
index 6582498..12f71ac 100644 | |
--- a/index.html | |
+++ b/index.html | |
@@ -98,6 +98,7 @@ comments: false | |
<div> | |
<!-- Tab panes --> | |
<div class="tab-content"> | |
+ {% increment issue_number %} | |
{% for tab in site.data.data.tabs %} |
#!/usr/bin/env bash | |
#---------------------------------------------------------------------- | |
# Functions | |
#---------------------------------------------------------------------- | |
# Exits the script with the given exit code after waiting | |
# for a keypress. | |
# | |
# @param [Integer] $1 exit code. | |
function key_exit() { |
{ | |
"env": { | |
"browser": true, | |
"node": true, | |
"es6": true | |
}, | |
"globals": { | |
"nconf": true | |
}, | |
"parser": "babel-eslint", |
#Web scrapers on the internet
See this repo to contribute/see more: https://github.com/cassidoo/scrapers
For security, since this script injects CSS via AJAX, first fork the main slack night mode repo. The reason is explained here
UPDATE: The code has been modified to download the remote css to a local file and use ruby sass compiler to verify there is no malicious code in the remote css. This will error if the code has been modified to include anything malicious (i.e. script or img tags etc.) It's also been refactored to use the local file inside the js injection, it makes sure it's safe first in the very unlikely event the local file somehow differs from the remote css. The chances of this happening are remote, but this should suffice for safety.
~/lacostenycoder/scripts/ruby/
remote_repo
variable in ruby script to use YOUR repo. The rawgit.com file is creaecho 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc | |
. ~/.bashrc | |
mkdir ~/local | |
mkdir ~/node-latest-install | |
cd ~/node-latest-install | |
curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1 | |
./configure --prefix=~/local | |
make install # ok, fine, this step probably takes more than 30 seconds... | |
curl https://www.npmjs.org/install.sh | sh |
As often happens, I found the official documentation and forum answers to be "close, but no cigar", and so had to experiment a little to get things working.
The main problem for me was a lack of concrete configuration examples. That's not entirely GitHub's fault: having migrated from Google Domains to Namecheap in the middle of this project, I was once again reminded of how many different ways there are to do things in the name service universe [1].
Although you'd think the simplest setup would be to merely configure for the subdomain case (https://www.example.com), in my experience using the apex domain (https://example.com) instead resulted in fewer complications.
So here's my recipe for using a custom domain with GitHub pages where Namecheap is the DNS provider:
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\