index

image

Today I added those subdomains to https.

I really must back up that server somewhere. I have it set up rather well.

Also with static directory installed nvm and node 

curl https://raw.githubusercontent.com/creationix/nvm/master/install.sh | bash


source ~/.profile


nvm ls-remote | grep -i 'latest'
or all versions starting with v12

nvm ls-remote | grep -i 'v12'

I have been quite a long time living with files with 777 permission being displayed in blue over green background whenever I do ls, which makes text quite illegible. 

dircolors --print-database &> ~/.dircolors

It will create a .dircolors file with the color specification vim .dircolors. Now we edit this file and change this line:

If you open the file up in vim you get a live update of the colors. We are looking to change

OTHER_WRITABLE 34;42 # dir that is other-writable (o+w) and not sticky

eval $(dircolors ~/.dircolors)

source ~/.bashrc

The color scheme is stored in the LS_COLORS variable. To view your current color scheme, you can tell the Bash to print the contents of the variable:

echo $LS_COLORS

Before playing around with this, we recommend saving the current contents of the LS_COLORS variable to another variable. This will allow you to quickly restore the default settings without signing out of the shell and signing back in, or closing and reopening the terminal window. To save the current content of the LS_COLORS variable to a new variable named ORIGINAL, run:

ORIGINAL=$LS_COLORS

At any time, you can run the following command to undo your changes and restore the default colors:

LS_COLORS=$ORIGINAL

Here’s the list of background color codes:

And this is how you would set it in ~/.bashrc:

LS_COLORS="di=1;35:ex=4;31:*.mp3=1;32;41"

Last line.

Date Modified: 2022-02-14