| # Based on https://steveholgado.com/nginx-for-nextjs/ | |
| # - /var/cache/nginx sets a directory to store the cached assets | |
| # - levels=1:2 sets up a two‑level directory hierarchy as file access speed can be reduced when too many files are in a single directory | |
| # - keys_zone=STATIC:10m defines a shared memory zone for cache keys named “STATIC” and with a size limit of 10MB (which should be more than enough unless you have thousands of files) | |
| # - inactive=7d is the time that items will remain cached without being accessed (7 days), after which they will be removed | |
| # - use_temp_path=off tells NGINX to write files directly to the cache directory and avoid unnecessary copying of data to a temporary storage area first | |
| proxy_cache_path /var/cache/nginx levels=1:2 keys_zone=STATIC:10m inactive=7d use_temp_path=off; | |
| upstream nextjs_upstream { |
Rust error handling is nice but obligatory. Which makes it sometimes plenty of code.
Functions return values of type Result that is "enumeration". In Rust enumeration means complex value that has alternatives and that alternative is shown with a tag.
Result is defined as Ok or Err. The definition is generic, and both alternatives have
When I use docker to work with the shared workspace with host under Ubuntu, I find that files created by docker user is owned by root. This is not the same with macOS.
Maybe this is becuase docker is run by root user and the default user mapping mechanism is to map container-root to host-user or host-root. So can I map the container-root or container-any-user to host-current-user?
Fortunately the latest docker supports the re-map the container user to any host user via Linux namespace. Refer to this.
| /** | |
| * Pass in an element and its CSS Custom Property that you want the value of. | |
| * Optionally, you can determine what datatype you get back. | |
| * | |
| * @param {String} propKey | |
| * @param {HTMLELement} element=document.documentElement | |
| * @param {String} castAs='string' | |
| * @returns {*} | |
| */ | |
| const getCSSCustomProp = (propKey, element = document.documentElement, castAs = 'string') => { |
| # start vault in dev mode | |
| VAULT_UI=true vault server -dev -dev-root-token-id="password" | |
| # write some secrets for our example usage | |
| curl --request POST \ | |
| --silent \ | |
| --header "X-Vault-Token: password" \ | |
| --header "Content-Type: application/json" \ | |
| --data '{ "options": { "cas": 0 }, "data": { "username": "administrator", "password": "hunter2" } }' \ | |
| http://127.0.0.1:8200/v1/secret/data/dev | jq '.' |
Feel free to contact me at robert.balicki@gmail.com or tweet at me @statisticsftw
This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!
It assumes some knowledge of AWS.
source: https://byai.io/howto-tensorflow-1-6-on-mac-with-gpu-acceleration/
Caution - you have to disable SIP (System Integrity Protection)
I am moving this gist to a github repo so more people can contribute to it. Also, it makes it easier for me to version control.
Please go to - https://github.com/praveenpuglia/shadow-dom-in-depth for latest version of this document. Also, if you find the document useful, please shower your love, go ⭐️ it. :)
Heads Up! It's all about the V1 Spec.
In a nutshell, Shadow DOM enables local scoping for HTML & CSS.
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm
| function encrypt(text){ | |
| var cipher = crypto.createCipher('aes-256-cbc','d6F3Efeq') | |
| var crypted = cipher.update(text,'utf8','hex') | |
| crypted += cipher.final('hex'); | |
| return crypted; | |
| } | |
| function decrypt(text){ | |
| var decipher = crypto.createDecipher('aes-256-cbc','d6F3Efeq') | |
| var dec = decipher.update(text,'hex','utf8') |