- C-a == Ctrl-a
- M-a == Alt-a
:q close
:w write/saves
:wa[!] write/save all windows [force]
:wq write/save and close
Note: I'm currently taking a break from this course to focus on my studies so I can finally graduate
# ~/.bashrc: executed by bash(1) for non-login shells. | |
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) | |
# for examples | |
# If not running interactively, don't do anything | |
[ -z "$PS1" ] && return | |
# don't put duplicate lines in the history. See bash(1) for more options | |
# ... or force ignoredups and ignorespace | |
HISTCONTROL=ignoredups:ignorespace |
Prerequisites:
Software components used:
#Understanding closures, callbacks and promises
For a code newbie like myself, callbacks, closures and promises are scary JavaScript concepts.
10 months into my full-time dev career, and I would struggle to explain these words to a peer.
So I decided it was time to face my fears, and try to get my head around each concept.
Here are the notes from my initial reading. I'll continue to refine them as my understanding improves.
#!/bin/bash | |
sudo apt-get update | |
sudo apt-get upgrade | |
ln -s "/mnt/c/Users/Daniel/Documents/homeflow" ~/homeflow | |
ln -s "/mnt/c/Users/Daniel/Documents" ~/documents | |
mkdir .ssh | |
cp documents/id* .ssh/ | |
sudo chmod 600 .ssh/* | |
cd homeflow/attis | |
git pull |
This article will explain how to set up a secure web server with NodeJS which only accepts connection from users with SSL certificates that you have signed. This is an efficient way to ensure that no other people are able to access the web server, without building a login system which will be significantly weaker.
I will not explain how to create a certificate authority (CA), create certificates or sign them. If you need to read up on this, have a look at this excelent article on how to do it with OpenSSL (Mac and Linux): https://help.ubuntu.com/community/OpenSSL#Practical_OpenSSL_Usage It is also possible to do this on a Mac with the keychain application, and I assume it is possible on a Windows machine aswell.
This architecture will allow you to have one web server communicating with an array of trusted clients, the web server itself can be on the public internet, that will not decrease the level of security, but it will only ser
<div class="def-panel" id="UDDIV_1"> | |
<div id="UDDIV_2"> | |
<div id="UDDIV_4"> | |
Top Definition | |
</div> | |
<div class="share small-6 columns" id="UDDIV_5"> | |
<a href="" target="_blank" id="UDA_6"> | |
<i class="svgicon svgicon-ud_twitter" id="UDI_7"> | |
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 34 34" id="UDsvg_8"><path d="M7.3 8c5.4 2.8 9.9 2.6 9.9 2.6s-1.7-6.2 3.6-8.9 9 1.9 9 1.9.9-.3 1.6-.5c.7-.3 1.7-.7 1.7-.7l-1.6 3 2.5-.3s-.3.5-1.3 1.4l-1.4 1.4s.4 7.4-3.4 13.1c-3.8 5.7-8.7 9.1-15.9 9.9C4.9 31.6.2 28.6.2 28.6s3.1-.2 5.1-1 4.9-2.8 4.9-2.8-4.1-1.3-5.5-2.7c-1.5-1.4-1.8-2.3-1.8-2.3l4-.1s-4.2-2.3-5.4-4.1S0 12.1 0 12.1l3.1 1.3S.5 9.8.2 7s.5-4.3.5-4.3S1.9 5.2 7.3 8z" id="UDpath_9"></path></svg> | |
</i> |