Silver Light and Blue Sky

C# and Infrastructure. Code is everything.

Running a NuGet server on OpenShift

This post was originally published on Red Hat Developers, the community to learn, code, and share faster. To read the original post, click here.

When you build your .NET Core project, NuGet packages are retrieved from by default. Sometimes, however, you might want to use a local NuGet repository. For example, you may want to:

  • use private NuGet packages, but you don’t want anyone except your associates to see them.
  • cache a NuGet repository at a server near your build servers
  • leave your build server disconnected from the Internet.

I’ll explain how to set up a private NuGet server on OpenShift and how you can use this NuGet server when building your .NET Core project in OpenShift using s2i-dotnetcore.

Read more

Thank you for hearing my presentation at London OpenShift meetup

Today I have a chance to make a presentation at London OpenShift meetup. I have been in England with my family on vacation.

Here is my slide.

Here is a GitHub repository for my demo projects.

Actually, I was surprised at .NET Core 2.0 release at this timing, two hours before the presentation. So I’ll update my demo OpenShift cluster to OCP 3.6 and .NET Core 2.0 RTM.

Thanks again for coming today.

Creating demo cluster for OpenShift Container Platform 3.5 on Azure

Here is what I did for creating my demo cluster for OpenShift Container Platform 3.5 on Azure.

  • Three masters with etcd (same hosts). These masters are also infra nodes.
  • One node (We can add more nodes later if we need)
  • One Azure Load Balancer with two public IP (master endpoint and router endpoint) We can’t separate these endpoints into two ALB because Azure doesn’t allow creating two or more ALBs with one backend pools.
Read more

resource file naming in ASP.NET Core localization

While I'm reading the document, I found difficulty in resource file naming.

Globalization and localization | Microsoft Docs

To summarize first:

  • "name" property of the project.json uses as the assembly name of the .NET Core project. The top level folder name is used if this property is not specified.
  • We must abbreviate the assembly name from the resource class FQDN if the FQDN starts with the assembly name.
  • We must use full FQDN if the FQDN doesn't start with the assembly name.
Read more