People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
| #!/bin/bash | |
| function countContainers() { | |
| docker ps -q $1 | wc -l | |
| } | |
| function countCrashedContainers() { | |
| docker ps -a | grep -v -F 'Exited (0)' | grep -c -F 'Exited (' | |
| } |
| #!/bin/bash | |
| ## THIS IS THE OLD WAY | |
| ## Nowadays, simply follow the Compose installation instructions in the official documentation: | |
| ## https://docs.docker.com/compose/install/ | |
| # get latest docker compose released tag | |
| COMPOSE_VERSION=$(curl -s https://api.github.com/repos/docker/compose/releases/latest | grep 'tag_name' | cut -d\" -f4) |
type below:
brew update
brew install redis
To have launchd start redis now and restart at login:
brew services start redis
While a lot of Node.js guides recommend using JWT as an alternative to session cookies (sometimes even mistakenly calling it "more secure than cookies"), this is a terrible idea. JWTs are absolutely not a secure way to deal with user authentication/sessions, and this article goes into more detail about that.
Secure user authentication requires the use of session cookies.
Cookies are small key/value pairs that are usually sent by a server, and stored on the client (often a browser). The client then sends this key/value pair back with every request, in a HTTP header. This way, unique clients can be identified between requests, and client-side settings can be stored and used by the server.
Session cookies are cookies containing a unique session ID that is generated by the server. This session ID is used by the server to identify the client whenever it makes a request, and to associate session data with that request.
*S
| #!/bin/bash | |
| # This script provides easy way to debug remote Erlang nodes that is running in a kubernetes cluster. | |
| # Usage: ./erl-observe.sh -l app=my_all -n default -c erlang_cookie | |
| # | |
| # Don't forget to include `:runtime_tools` in your mix.exs application dependencies. | |
| set -e | |
| # Trap exit so we can try to kill proxies that has stuck in background | |
| function cleanup { | |
| echo " - Stopping kubectl proxy." |
| class ApplicationController < ActionController::Base | |
| protect_from_forgery with: :exception | |
| around_action :global_request_logging | |
| def global_request_logging | |
| http_request_header_keys = request.headers.env.keys.select{|header_name| header_name.match("^HTTP.*|^X-User.*")} | |
| http_request_headers = request.headers.env.select{|header_name, header_value| http_request_header_keys.index(header_name)} | |
| puts '*' * 40 | |
| pp request.method |
TLDR: JWTs should not be used for keeping your user logged in. They are not designed for this purpose, they are not secure, and there is a much better tool which is designed for it: regular cookie sessions.
If you've got a bit of time to watch a presentation on it, I highly recommend this talk: https://www.youtube.com/watch?v=pYeekwv3vC4 (Note that other topics are largely skimmed over, such as CSRF protection. You should learn about other topics from other sources. Also note that "valid" usecases for JWTs at the end of the video can also be easily handled by other, better, and more secure tools. Specifically, PASETO.)
A related topic: Don't use localStorage (or sessionStorage) for authentication credentials, including JWT tokens: https://www.rdegges.com/2018/please-stop-using-local-storage/
The reason to avoid JWTs comes down to a couple different points:
| matrix = [[1,2,3,4], [5,6,7,8]] | |
| defmodule Matrix do | |
| def transpose([[] | _]), do: [] | |
| def transpose(m) do | |
| [Enum.map(m, &hd/1) | transpose(Enum.map(m, &tl/1))] | |
| end | |
| end | |
| IO.inspect matrix |
