2 nice "tail -f" replacement:
- lnav
- tspin
A place for all technical hints
2 nice "tail -f" replacement:
If your conda env is nodejs v18, doing a conda install nodejs=26 is likely to create a lot of conflict.
Consider remove those conflicting packages and install the nodejs v26:
To add CSP to root if sort of funny. The following will NOT work for most cases !!
<LocationMatch "^/$">
Header set Content-Security-Policy "unsafe-inline"
</LocationMatch>
Case 1: The root (/) is associated with DocumentRoot
In this case, because you used the DocumentRoot, the 'Header set' behavior is not applied. You need to match the final resulting document, e.g.
<LocationMatch "^/index.html$">
Header set Content-Security-Policy "unsafe-inline"
</LocationMatch>
Case 2: The root (/) is redirected via Rewrite rule
In this case, because it is a HTTP 301 response, the 'Header set' behavior is not applied (It only applies to HTTP 200 response by default). You need to use 'Header always set':
<LocationMatch "^/$">
Header always set Content-Security-Policy "unsafe-inline"
</LocationMatch>
To access window's localhost from wsl, you can set networkingMode=mirrored in .wslconfig
Reference:
https://learn.microsoft.com/en-us/windows/wsl/wsl-config#configuration-settings-for-wslconfig
Use the following alias:
alias nt='wt.exe -w 0 wsl'
It means starting a new terminal (tab) in the same window (-w 0) , and run a command wsl with it.
When you encountered certificate issues when using node.js, there are some workaround that can be tried:
1) Add custom CA certs
$ export NODE_EXTRA_CA_CERTS=[your CA certificate file path]
2) Disable certificate checking
NODE_TLS_REJECT_UNAUTHORIZED
When using logrotate in Linux, you might encounter a situation where your log file gone when the log rotated. One of the flag that you may need to notice is the copytruncate flag. It did not remove the current log file, instead it copy the log file and then truncate it:
File name: /etc/logrotate.d/your-application
/var/log/your-application/output.log {
copytruncate
rotate 5
daily
compress
delaycompress
notifempty
missingok
}
When failed to proxy pass with https in Quasar framework, it is very likely that the target-host HTTPS are configured incorrectly. As a workaround, you can modify the quasar.conf.js with secure:false as following:
"/context/path1/": {
target: "https://target-host/path1/",
secure: false,
changeOrigin: true,
pathRewrite: {
"^/context/path1/": "",
},
},
The Linux Slack consumes a lot of CPU and memory in Linux environment. To limit its resource usages, you can apply a quote via the snap command:
sudo snap set-quota slacklimit --memory=2GB --cpu=20% slack
2 nice " tail -f " replacement: lnav tspin Both available in Linux with text highlighting. Beautiful.