Add systemd hidden_wifi_connect.service
vim /etc/systemd/system/hidden_wifi_connect.service
[Unit]
Description=Connect to hidden wifi network on start
Before=network.target
[Service]
sudo systemctl list-unit-files |
- With software, and even hardware, everything is under an ecosystem | |
- Getting the latest Intel doesn't mean you get all the bells and whistles. Not all software will harness all the power and features it may introduce | |
- Getting the latest wordpress doesn't mean smooth sailing. Not all themes and plugins will be ready for it. Do you believe all those plugins and theme you got for free can dedicate manpower to update their code every time there's a change? Have you done anything in your life for free? That's what open-source is at the core. But all that relies on it will move things for free. | |
- Getting latest PHP doesn't mean you're moving forward. Not all tools will be ready for it including your primary analysis tools, etc. | |
- Getting the recent released games doesn't mean all pleasant experience all the time. There are bugs to be caught. | |
So before you look at changing versions, focus on what matters. | |
Are you testing your code? | |
Are you using reliable plugins? | |
Have you focused on your page SEO? |
Add systemd hidden_wifi_connect.service
vim /etc/systemd/system/hidden_wifi_connect.service
[Unit]
Description=Connect to hidden wifi network on start
Before=network.target
[Service]
- sudo update-alternatives --config editor | |
- set to vim.basic, i.e. vanilla vim | |
- sudo visudo | |
- stop password req for root things | |
- `umask 002` added in .bashrc | |
- set primary group as www-data | |
- created ~/sites folder | |
- chgrp www-data ~/sites | |
- chmod g+s ~/sites | |
- installed |
HTTP caching is a scheme of showing same resource unless content needs to be regenerated by fetching it again from the web server. | |
HTTP objects may be a static resource or a dynamic page built by some backend language like PHP. | |
Tools used are (1) HTTP Reverse Proxy, e.g. Varnish and HAProxy. Cache server is hit first before web server. All fetch resource will be cached locally first by the proxy before sending it to the client. If cache is hit, web server won't be touched at all, i.e. no access log entry will be appended. Only the first request is slow. | |
Another tool used is HTTP Browser cache. It relies on headers ETag and Cache-Control | |
Apache Cache-Control | |
FileETag None |
# enable ssh-server | |
ssh-keygen | |
sudo update-alternatives --config editor | |
# Choose vim.tiny | |
sudo apt install git | |
# Add dotfiles | |
git clone git@github.com:paoloumali/.files.git $HOME/.files |
I was noticing errors like
Command 'check' not found whenever I start a new bash shell.
I turned out I uncommented a line in .bashrc which starts with check.
I was able to figure it out by setting:
set -x
at the top
Add in .bashrc below, then refresh session | |
``` | |
set -o vi | |
bind '"jk":"\e"', do only if in control of all systems, stick with ESC for consistency | |
``` | |
It defaults to insert mode, ESC/jk to go command mode. | |
## Benefits |
php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php -r "if (hash_file('sha384', 'composer-setup.php') === 'e0012edf3e80b6978849f5eff0d4b4e4c79ff1609dd1e613307e16318854d24ae64f26d17af3ef0bf7cfb710ca74755a') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
sudo php composer-setup.php --install-dir=/usr/local/bin --filename=composer