Explore >> Select a destination
|
You are here 
|
vlad.website | ||
| | | | |
hjr265.me
|
|
| | | | | I have lines like these in my /etc/hosts file: 127.0.0.1 toph.local 127.0.0.1 drafts.toph.local 127.0.0.1 quiz.toph.local I can run development servers locally and access them over .local hostnames (e.g. toph.local) instead of the loopback IP addresses (e.g. 127.0.0.1). It works fine. But every time I start working on a new project, I needed to add a new line to the /etc/hosts file. It didn't sit right with me. I should be able to point all *. | |
| | | | |
zwischenzugs.com
|
|
| | | | | InAnatomy of a Linux DNS Lookup - Part II covered: nsswitch /etc/hosts /etc/resolv.conf pingvshoststyle lookups and inAnatomy of a Linux DNS Lookup - Part III covered: systemdand itsnetworkingservice ifupandifdown dhclient resolvconf and ended up here: A (roughly) accurate map of what's going on Unfortunately, that's not the end of the story. There's still more things... | |
| | | | |
blogops.mixinet.net
|
|
| | | | | This entry explains how I have configured a linux bridge, dnsmasq and iptables to be able to run and communicate different virtualization systems and containers on laptops running Debian GNU/Linux. I've used different variations of this setup for a long time with VirtualBox and KVM for the Virtual Machines and Linux-VServer, OpenVZ, LXC and lately Docker or Podman for the Containers. Required packagesI'm running Debian Sid with systemd and network-manager to configure the WiFi and Ethernet interfaces, bu... | |
| | | | |
www.styra.com
|
|
| | | Build a solid understanding of how to secure Kubernetes along with some best practices. Learn how to secure nodes, clusters and pods. | ||
