Ventura docs for M2 Macs in this comment: https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd?permalink_comment_id=4555340#gistcomment-4555340
Old Monterey docs in this old revision: https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd/32c410e3a1de73539c76fa13ea5486569c4e0c5d
Solution for Sonoma: https://gist.github.com/sghiassy/a3927405cf4ffe81242f4ecb01c382ac
| #!/bin/sh | |
| f="$(dirname $0)/log.txt" | |
| if [ "$1" = "time" ]; then | |
| last="$(cat "$f" | grep "# " | tail -n 1 | sed 's/^.*: //' | cut -d '-' -f 1)" | |
| last=$(date +%s -d "$last") | |
| now=$(date +%s) | |
| diff=$(($now - $last)) |
| <# | |
| .Synopsis | |
| Robocopy wrapper with standard 0 (success) and 1 (failure) exit codes. | |
| .Parameter source | |
| Defines the source folder | |
| .Parameter target | |
| Defines the target folder | |
| .Parameter include | |
| Defines the files to include. Accepts wildcards. Eg: -include *.dll,*.pdb | |
| Optional, Default value is $null and will include all files from source. |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
