how to configure MinimalNugetServer on Linux?

[andryua]

Hi!
I tried to setup MinimalNugetServer on Linux, but i can't did it...
Ubuntu Server 16.04
dotnet sdk 1.0.0-rc4

No executable found matching command "dotnet-git-commit-info"
/home/andriy/MinimalNugetServer/MinimalNugetServer/MinimalNugetServer.csproj(39,5): error MSB3073: The command "dotnet git-commit-info" exited with code 1.

Build FAILED.

/home/andriy/MinimalNugetServer/MinimalNugetServer/MinimalNugetServer.csproj(39,5): error MSB3073: The command "dotnet git-commit-info" exited with code 1.
0 Warning(s)
1 Error(s)

Maybe i do something wrong? Can You help me?
Thanks!

[TanukiSharp]

Hi, does it work if you build a second time ?

There is was a bug (or a feature) in the old .NET Core that a file generated before compilation was not taken into account for the build. The second time you build, the file already exists and it should build properly.

If the problem persists, you can simply remove all references to the GitCommitInfo, it is not absolutely necessary to run but just to display the git commit hash to easily retrieve the reference if necessary.

I think I will update MinimalNugetServer to .NET Core 2.0 soon anyway.

Let me know if you still encounter issues.

[TanukiSharp]

I pushed 2 new commits, one with the new way to use GitCommitInfo (tagged v1.0.5) and another one with updated SDK and target runtime to use .NET Core 2.0 (tagged v1.1.0), both should solve your build issue, now chose either one depending if you want to keep targeting .NET Core 1.x or 2.0, but i recommend you to target 2.0.

[andryua]

Thanks!
I tried with new commit with .Net Core SDK - 2.0.0.
but...
first - edit, please, sh files (if user dotnet 2.0)
second - all works!
Thanks!
Now - trying configure server.

[TanukiSharp]

Sorry about that, I updated the scripts.

However, for the exception you have at runtime, this is because you must set a correct path in your configuration file, as stated in the documentation (readme.md file, or project home page on github)

The path /absolute/path/to/packages/folder you can see in the exception message is just a placeholder for you to set the path to your internally hosted NuGet packages.

[andryua]

Hi!
I did everything like You sad in readme. But, when i try to check list of files - chocolatey sad - o packages found.
What i do wrong?

p.s. I added few .nupkg files in /srv/repo folder and write src in configuration.json

[TanukiSharp]

This server works the same as if it were a samba storage, meaning will have files at the root folder, named ..nupkg. If you have all you packages stored like for CHocolatey, they are probably in a folder hierarchy, which is not supported by MinimalNugetServer.

I'm sorry about that.

[andryua]

Which folder hierarchy supported by MinimalNugetServer?

[TanukiSharp]

It supports no folder hierarchy, all the NuGet packages (.nupkg) files have to be in the same folder, the one configured in the configuration file.

[andryua]

chocolatey repo supports same hierarchy - all .nupkg files are in same folder...
maybe i set wrong /absolute/path/to/packages/folder -?

[TanukiSharp]

For example, if you store packages in the folder packages of the home folder of the user alice, them you have to configure the packages path like `"/home/alice/packages". Remember that Linux file system is case sensitive.

To make sure you have the proper path set, go to the folder where your packages are located, and type the command pwd, then simply copy/paste the output value, this will be the correct path.

[andryua]

I know about sensitive. I create /srv/repo and copy .nupkg files here. What kind of URL i must enter for testing?

[TanukiSharp]

In your NuGet.config file, located in %APPDATA%\NuGet on Windows and in ${HOME}/.nuget on Linux, you should add a source to your NuGet server, as follow:

<configuration>
    <packageSources>
        ...
        <add key="AnyValueYouLike"
             value="http://<address-of-your-server>:<port-or-your-server>/v2/" />
    </packageSources>
    ...
</configuration>

The / character at the end of the URL is very important, do not omit it.

Then from any project, you should be able to restore packages located on your NuGet server.

[andryua]

I tried to push .nupkg files into server, but after choco push -s http://address:port/v2/ (or v3) - did this without errors, but real do nothing... file not downloaded on server. I down't know how about other nuget services, but chocolatey doesn't work with this server :(

[TanukiSharp]

MinimalNugetServer does not support push / upload. You have to copy the .nupkg manually to the machine that runs MinimalNugetServer, in the folder described by the configuration file.