• lxd and adjusting size of root device

    , , ,
    kayama

    That’s normal. With LXD 2.9 and the storage pool changes, LXD stopped generating automatic «root» devices for the containers, instead relying on inheritance from the default profile.

    So in LXD < 2.9, every container had a local «root» device which you could then set properties directly on. With those LXD versions, adding a «root» device to your default profile would be entirely ignored as all containers would override it.

    In LXD > 2.9, containers don’t have any devices by default, they instead rely on inheritance. Meaning that if you want to override it, you have to add a new device to the container with the same name so that it overrides the one coming from the profiles.

    «lxc config show NAME» vs ” lxc config show –expanded NAME ” is pretty useful to see how this all works.

    © https://discuss.linuxcontainers.org/u/stgraber

  • makepasswd console script

    ,
    kayama

    Add to the .bash_profile

    1
    alias makepasswd=”openssl rand -base64 $1″

  • nginx and letsencrypt locations

    ,
    kayama

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    server {
        listen 80;
        server_name example.com;
     
        location / {
           return 301 https://$server_name$request_uri;
        }
       
        location /.well-known/acme-challenge/ {
          root /var/www/html;
        }
     }

  • macOs / Linux ssh autocomplete hint

    , , ,
    kayama

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    _complete_ssh_hosts ()
    {
            COMPREPLY=()
            cur=”${COMP_WORDS[COMP_CWORD]}”
            comp_ssh_hosts=`cat ~/.ssh/known_hosts | \
                            cut -f 1 -d ‘ ‘ | \
                            sed -e s/,.*//g | \
                            grep -v ^# | \
                            uniq | \
                            grep -v “\[” ;
                    cat ~/.ssh/config | \
                            grep “^Host ” | \
                            awk ‘{print $2}’
                    `
            COMPREPLY=( $(compgen -W “${comp_ssh_hosts}” — $cur))
            return 0
    }
     
    complete -F _complete_ssh_hosts ssh

  • ubuntu git install and tips

    , ,
    kayama

    # update packages

    1
    sudo apt-get update

    # install gitolite server

    1
    sudo apt-get install gitolite3

    # rename (not necessary) user gitolite3 to git

    1
    sudo usermod gitolite3 –login git

    # clone git admin dir to your home account

    1
    2
    cd ~
    git clone [email protected]:gitolite-admin

    # make changes in gitolite.conf — add new repo

    1
    2
    3
    “`repo web-app
     
        RW+     =   admin“`

    # show status

    1
    git status

    # add files to repo

    1
    git add -A .

    # commit your changes

    1
    git commit -m ‘Added new repo’

    # for use simple git push

    1
    git config –global push.default simple

    # push changes to repo

    1
    git push

    All done, your repo is ready.

    Now go to dir with your app.

    1
    cd ~/web-app/

    # initialize dir for git

    1
    git init

    # add url of «remote» repo

    1
    git remote add origin ssh://[email protected]:8822/web-app

    # check it

    1
    git remote -v

    # commit and push your repo

    1
    2
    3
    4
    5
    6
    7
    git status
     
    git add -A .
     
    git commit -m ‘Initial commit’
     
    git push –set-upstream origin master

    # clone repo on desktop

    1
    git clone ssh://[email protected]:8822/web-app