When I build a new Linux host\/Raspberry to play around, there are four basic things I always do first. No fancy automation, just quick and dirty manual labor:<\/p>\n\n\n\n
Without vim I am lost.<\/p>\n\n\n\n
# accept to enter the password for sudo once more:\nsudo apt-get install vim\n\n# make vim the default editor (optional)\nsudo update-alternatives --set editor \/usr\/bin\/vim.basic<\/code><\/pre>\n\n\n\nssh-key<\/h2>\n\n\n\n
I usually login with my password to accomplish the task. If there is a default password I change it.<\/p>\n\n\n\n
cd ~\nmkdir .ssh\ntouch .ssh\/authorized_keys && chmod 640 .ssh\/authorized_keys\n# copy + paste id.pub > .ssh\/authorized_keys\n# I do this with vim, any editor will do ;-)\nvim .ssh\/authorized_keys<\/code><\/pre>\n\n\n\nMake sure your ssh-key is loaded (e.g. with putty pageant) and login to verify it works.<\/p>\n\n\n\n
Now I disable logins with passwords via SSH.<\/p>\n\n\n\n
sudo vim \/etc\/ssh\/sshd_config\n\n# make sure there is a line with\nPasswordAuthentication no\n\n# restart ssh\nsudo systemctl restart ssh<\/code><\/pre>\n\n\n\nDo not logout. Check if everything works as expected first. This way your SSH session remains available to fix things if necessary.<\/p>\n\n\n\n
sudo<\/h2>\n\n\n\n
On my hosts I want to use sudo without password prompts.<\/p>\n\n\n\n
sudo visudo\n\n# add the following line, replace 'username' with your login:\nusername ALL=(ALL) NOPASSWD: ALL<\/code><\/pre>\n\n\n\ndotfiles<\/h2>\n\n\n\n
This is where the magic comes in \ud83d\ude09<\/p>\n\n\n\n
Managing your dotfiles with git is quite a popular topic for Mac and Linux users. You will find a lot of resources out there. A helpful starting point is https:\/\/dotfiles.github.io\/<\/a> or https:\/\/github.com\/webpro\/awesome-dotfiles<\/a><\/p>\n\n\n\nWhen I started to organize my personal dotfiles I based my repository<\/a> on the work of Zach Holman<\/a>. <\/p>\n\n\n\nWhat are dotfiles good for?<\/h3>\n\n\n\n
In Unix-like systems files and directories starting with a dot in its name are “hidden” and don’t show by default. That is where the name comes from. Dotfiles store per-user configuration for applications like bash, git, vim and many others.<\/p>\n\n\n\n
I prefer to have a consistent configuration across my hosts for the fundamental tools I mentioned above. <\/p>\n\n\n\n
Make them rock. Just clone the repo and initialize the environment:<\/p>\n\n\n\n
# install git first\nsudo apt-get install git\n\ngit clone https:\/\/github.com\/tbaecker\/dotfiles.git ~\/.dotfiles\n~\/.dotfiles\/bin\/dotfiles<\/code><\/pre>\n\n\n\nLog out and in again. You’re setup.<\/p>\n\n\n\n
Dotfiles are a very personal thing. You tweak them the way you want. Check out the various approaches and setups and choose one that fits your expectations. You will have to take some time but once setup it will begin to pay off.<\/p>\n","protected":false},"excerpt":{"rendered":"
When I build a new Linux host\/Raspberry to play around, there are four basic things I always do first. No fancy automation, just quick and dirty manual labor: install my favorite editor vim, make vim the default editor (optional) add my ssh-key to authorized_keys for passwordless logins via SSH configure sudo to avoid the password prompt when doing superuser stuff clone my dotfiles git repo to setup my environment for convenient terminal usage vim Without vim I am lost. ssh-key…<\/p>\n