Release: Prepare for v0.1.0

* Update configuration guide and readme

Author: ByteOtter

Cargo.toml

@@ -1,7 +1,7 @@
 [package]
 name = "nazara"
 authors = ["Tiara Hock <tiara.dev@proton.me>", "Marvin Friedrich <me@mrvn.sh>"]
-version = "0.1.0-beta.3"
+version = "0.1.0"
 edition = "2024"
 description = "A CLI application to create and update machines and VMs in NetBox."
 readme = "README.md"

Nazara.changes

@@ -1,3 +1,12 @@
+-------------------------------------------------------------------
+Sat Nov 13 16:58:02 UTC 2025 - Tiara Hock <tiara.dev@proton.me>
+
+- 0.1.0
+    * Allow specifying of primary IPs for VMs and devices
+    * Prepare code structure for dedicated testsuite
+    * Fix a bug with auto mode
+    * Create a VM testing guide for developers
+
 -------------------------------------------------------------------
 Sat Oct 25 12:58:02 UTC 2025 - Tiara Hock <tiara.dev@proton.me>
 

Nazara.spec

@@ -15,7 +15,7 @@
 # Please submit bugfixes or comments via https://bugs.opensuse.org/
 
 Name:           Nazara
-Version:        0.1.0_beta.3
+Version:        0.1.0
 Release:        0.1
 Summary:        Automated registration and update of machines and VMs in NetBox
 License:        GPL-3.0

README.md

@@ -7,13 +7,6 @@ new machines in NetBox or population of information fields for existing ones.
 **Nazara is in the early stages of its development. Please note that the
 information listed below is subject to change.**
 
-> [!Note] Nazara is currently in a beta state. Bugs are bound to happen. If you
-> encounter any, please
-> [report them](https://github.com/The-Nazara-Project/Nazara/issues).
->
-> Furthermore, **Nazara currently does not support custom fields for any NetBox
-> object**. Though, this is the next item on our agenda.
-
 - [Compatibility](#compatibility)
 - [Installation](#installation)
   - [Building from source](#building-from-source)
@@ -35,12 +28,13 @@ NetBox. When major ports to newer NetBox versions happen - which usually include
 breaking changes - the old version of Nazara will be moved to its own branch and
 tagged accordingly.
 
-| Nazara Version   | NetBox Version    | Branch            | maintained?        |
-| ---------------- | ----------------- | ----------------- | ------------------ |
-| `v0.1.0_beta.3`  | `v4.3.x`, `v4.4.x`| `main`            | :white_check_mark: |
-| `v0.1.0_beta.2`  | `v4.3.x`, `v4.4.x`| `version/beta-2`  | :x:                |
-| `v0.1.0_beta.1`  | `v4.3.x`          | `version/beta-1`  | :x:                |
-| `v0.1.0_alpha.2` | `v3.6.x`          | `version/alpha-2` | :x:                |
+| Nazara Version   | NetBox Version     | Branch            | maintained?        |
+| ---------------- | ------------------ | ----------------- | ------------------ |
+| `v0.1.0`         | `v4.3.x`, `v4.4.x` | `main`            | :white_check_mark: |
+| `v0.1.0_beta.3`  | `v4.3.x`, `v4.4.x` | `version/beta-3`  | :x:                |
+| `v0.1.0_beta.2`  | `v4.3.x`, `v4.4.x` | `version/beta-2`  | :x:                |
+| `v0.1.0_beta.1`  | `v4.3.x`           | `version/beta-1`  | :x:                |
+| `v0.1.0_alpha.2` | `v3.6.x`           | `version/alpha-2` | :x:                |
 
 Maintenance work on these older versions is not planned.
 
@@ -155,11 +149,12 @@ When launching Nazara for the first time, it will write a stock config file to
 that path. Certain parameters are required to be configured there manually. You
 recognize them by their line not being commented out.
 
-Aside from the NetBox system parameters,
-configuration via the `config.toml`also allows you to add certain
-custom fields to your system information that cannot be automatically selected. A great example would be the`System
-Location`entry. To specify that, simply add the parameter under the`[system]`
-block in your configuration file.
+Aside from the NetBox system parameters, configuration via the `config.toml`also
+allows you to add certain custom fields to your system information that cannot
+be automatically selected. A great example would be the`System
+Location`entry.
+To specify that, simply add the parameter under the`[system]` block in your
+configuration file.
 
 > [!Note] Currently, configuration by config file is the proper way to use
 > Nazara given the amount of data required to register a machine. We are

docs/src/intro.md

@@ -24,8 +24,9 @@ to its own branch and tagged accordingly.
 
 |Nazara Version  |NetBox Version               |Branch           |maintained?|
 |----------------|-----------------------------|-----------------|---|
-|`v0.1.0_beta.3` |`v4.3.x`, `v4.4.x` and newer |`main`           |yes|
-|`v0.1.0_beta.2` |`v4.3.x`, `v4.4.x` and newer |`version/beta-2` |no |
+|`v0.1.0`        |`v4.3.x`, `v4.4.x` and newer |`main`           |yes|
+|`v0.1.0_beta.3` |`v4.3.x`, `v4.4.x` and newer |`version/beta-3` |no |
+|`v0.1.0_beta.2` |`v4.3.x`, `v4.4.x`           |`version/beta-2` |no |
 |`v0.1.0_beta.1` |`v4.3.x`                     |`version/beta-1` |no |
 |`v0.1.0_alpha.2`|`v3.6.x`                     |`version/alpha-2`|no |
 

docs/src/users/configuration.md

@@ -51,6 +51,28 @@ config between machines of the same type and function.
 {{#include ../../../src/configuration/config_template.toml}}
 ```
 
+For VMs, the `name` parameter **is required** to be able to distinguish them cleanly.
+
+~~~ admonish tip
+The `name` parameter is optional for devices. If left empty, Nazara will assume the system's hostname as the name
+value for the entry. You can combine both your custom name and the machine's hostname by fixing a `@`
+symbol to the end of the name value. This works on both VMs and devices.
+
+This way a config entry like this:
+
+```toml
+[common]
+name = "aurora@"
+```
+
+turns into:
+
+```toml
+aurora@linux.fritz.box
+```
+in the final entry.
+~~~
+
 ### The `config` commands
 
 Nazara provides you with several commands to manage your configuration files: