Profiles 101

Adding a profile

Add or Replace: For all this examples it’s possible to replace add with replace and it will replace all previous content of the chosen profile with the new one.

Add new profile from a file

You can store routing as a separate file and add it to the global hosts file when you need. For example, if you have this routing file on any of your projects:

# Sample stored in /path/of/some/project/repo/.etchosts
127.0.0.1 web.my-awesome-project.local 
127.0.0.1 api.my-awesome-project.local 

Command:

hostctl replace awesome --from /path/to/some/project/.etchosts

Output:

+---------+--------+----------------+------------------------------+
| PROFILE | STATUS |       IP       |            DOMAIN            |
+---------+--------+----------------+------------------------------+
| default | on     | 127.0.0.1      | localhost                    |
| default | on     | 127.0.1.1      | some-existing.local          |
| default | on     | ::1            | ip6-localhost                |
+---------+--------+----------------+------------------------------+
| another | on     | 192.168.1.51   | jupyter.toolkit-lite.local   |
+---------+--------+----------------+------------------------------+
| awesome | on     | 127.0.0.1      | web.my-awesome-project.local |
| awesome | on     | 127.0.0.1      | api.my-awesome-project.local |
+---------+--------+----------------+------------------------------+

Add domains from args

You can add a new profile or add new domain to a specific profile directly from the cli:

You can add that content as a profile with this command:

hostctl add domains test one.loc another.loc --ip 123.123.123.123

// Output:
+---------+--------+-----------------+------------------------------+
| PROFILE | STATUS |       IP        |            DOMAIN            |
+---------+--------+-----------------+------------------------------+
| default | on     | 127.0.0.1       | localhost                    |
| default | on     | 127.0.1.1       | some-existing.local          |
| default | on     | ::1             | ip6-localhost                |
+---------+--------+-----------------+------------------------------+
| another | on     | 192.168.1.51    | jupyter.toolkit-lite.local   |
+---------+--------+-----------------+------------------------------+
| test    | on     | 123.123.123.123 | one.loc                      |
| test    | on     | 123.123.123.123 | another.loc                  |
+---------+--------+-----------------+------------------------------+

Add new profile from stdin

Similar to the previous option, you can pipe from a previous command or redirect output to it.

Commands (both work similarly):

  • cat /path/to/some/project/.etchosts | hostctl add awesome
  • hostctl add awesome < /path/to/some/project/.etchosts

Output:

+---------+--------+----------------+------------------------------+
| PROFILE | STATUS |       IP       |            DOMAIN            |
+---------+--------+----------------+------------------------------+
| default | on     | 127.0.0.1      | localhost                    |
| default | on     | 127.0.1.1      | some-existing.local          |
| default | on     | ::1            | ip6-localhost                |
+---------+--------+----------------+------------------------------+
| another | on     | 192.168.1.51   | jupyter.toolkit-lite.local   |
+---------+--------+----------------+------------------------------+
| awesome | on     | 127.0.0.1      | web.my-awesome-project.local |
| awesome | on     | 127.0.0.1      | api.my-awesome-project.local |
+---------+--------+----------------+------------------------------+

Removing a profile

If you want to completely remove a profile from the hosts file you can run:

hostctl remove awesome

// Output:
+---------+--------+----------------+------------------------------+
| PROFILE | STATUS |       IP       |            DOMAIN            |
+---------+--------+----------------+------------------------------+
| default | on     | 127.0.0.1      | localhost                    |
| default | on     | 127.0.1.1      | some-existing.local          |
| default | on     | ::1            | ip6-localhost                |
+---------+--------+----------------+------------------------------+
| another | off    | 192.168.1.51   | jupyter.toolkit-lite.local   |
+---------+--------+----------------+------------------------------+
This action cannot be undone. If you need to enable the profile later, use disable instead.

Last updated by guumaster on July 20, 2020 at 20:50 +0200