Documentation

Nomirun initialization

Open up the PowerShell and type nomirun, or nomi for short. If you see the help screen, your CLI has installed successfully.

Next step is to run nomirun init command to initialize the Nomirun on your PC.

First latest versions of Nomirun Host are automatically downloaded:

Downloading Nomirun Host ------------------------- 100% 00:00:00
Downloading Nomirun Host for debugging ----------- 100% 00:00:00
               

Next AI capabilities are configured. Select [y] if you want to use the AI capabilities. This will download the model and other dependencies.

Install nomirun AI for advanced docs generation and swagger enrichment. Download the model (2.5GB)? [y/n] (y): y

Downloading AI model ------------------------------ 0% --:--:--
Downloading AI model runtimes --------------------- 0% --:--:--
               

Then an initialization process will detect if you have CUDA installed. If found, you can pick it from the list and hit enter.

Below CUDA toolkit versions are detected on your machine. Select which one you want to use with Nomirun AI capabilities?

Default CUDA
> CUDA 12.8
               

As a final step you need to specify Nuget server where you will host your Nomirun modules. When building a module, you specify the server name to which you want to publish the Nomirun module NuGet package (nupkg).

Welcome to Nomirun CLI initialization.
In order to build and run modules, you need to specify Which Nuget server you want to configure? You can configure one or more. For development we suggest you use `LocalFolder`.

[] Azure DevOps
[] GitHub<
[] Baget
[] Feedz.io
[] Local Folder
               

Currently, we support five options for Nuget server, you can select 1 or more:

  1. Azure DevOps
  2. GitHub
  3. Baget—if you run your own instance of Baget NuGet server, you can select it.
  4. Feedz.io - is an alternative feed that is very flexible.
  5. Local Folder - is advised to use it for local development for debug and standalone Nomirun Hosts. Do not use for containerized hosts as in containers the nuget server needs to be accessible from HTTP in the container.

Once you select Nuget server(s), wizard will navigate you to configure it. In the end, the configuration is stored.

You can also rerun the initialization, overwriting the configuration file previously created.