Pinter Computing

The default MSSQL server installation only enables the Shared Memory network protocol for connection.

Node.js can only connect using TCP/IP protocol. The error message is

Failed to connect to localhost/…. Error: Failed to connect to localhost:1433 – Could not connect (sequence) Failed to connect to localhost:1433 – Could not connect (sequence) ConnectionError: Failed to connect to localhost:1433 – Could not connect (sequence)

Enable the TCP/IP protocol

To be able to connect to a local MSSQL Server from a Node.js application, we need to enable the TCP/IP protocol.

• Open the SQL Server Configuration Manager as administrator
  Right-click the SQL Server Configuration Manager item in the start menu, select More, and click the Run as administrator option
  
• In the SQL Server Network Configuration select Protocols for MSSQL SERVER, and double-click the TCP/IP option. Set the Enabled value to Yes
  
• The dialog box reminds us to restart the MSSQL Server for the change to take effect
  

Restart the MSSQL Server

• On the left side select SQL Server Services, right-click MSSQL Server and select Restart
  

You may apply these configuration settings to enable useful features. Always read the documentation to see if these are safe and beneficial to you.

Copilot Memory

You can use Copilot Memory to remember repository context across Copilot agent interactions.

• On the https://github.com/settings/copilot/features page enable Copilot Memory

To store a memory start the prompt with “Remember: …”

More information on GitHub Copilot memories are at https://docs.github.com/en/copilot/how-tos/use-copilot-agents/copilot-memory

Checkpoint file changes

chat.checkpoints.showFileChanges set to ON

Explain button

chat.editing.explainChanges.enabled set to ON

Inline Chat Enable V2

If you want to experiment with the new inline chat feature enable

inlineChat.enableV2

Usage suggestions

Hide Sessions

When the chat window is wide enough it displays the list of prior sessions. It is useful, but prevents us to widen the chat window for better reading experience. We can disable this behavior using the chat.viewSessions.enabled setting, or close the prior sessions with the Hide Agent Sessions Sidebar button

The development of Kerbal Space Program 2 was terminated prematurely, just at the time when the major bugs were removed, but before the application would provide significant benefits over version 1.

With mods, Kerbal Space Program 1 can provide the same visual quality with less bugs and better performance. As the development of version 1 was completed at a planned state, the application is stable, and will not change anymore. This simplifies the work of modders, who otherwise would need to constantly update their mods to keep up with the changes in the application code. This provides the ideal platform for the modding community to freely enhance the game for the benefit of everyone.

Visual Quality Improvements

Users recommend the following mods to improve visual quality

• Scatterer (Kabrams Diamond Sunflare or any other mod available)
• Parralax
• EVE (Or if you’re willing to pay, Blackrack’s Volumetric Clouds)
• PlanetShine
• Firefly
• Astronomer’s Visual Pack
• Better Kerbol
• ASET Props and Avionics packs
• Textures Unlimited
• TextureReplacer
• Waterfall
• WindowShine
• ShineFix
• TUFX

To determine how much memory the Azure Container App needs, we can use the Metrics feature. To monitor the resource usage

• Log into the Azure Portal at https://portal.azure.com
• Open the Container Apps page, and select the application
• On left in the Monitoring menu select Metrics
  
• Click the Add metric button and select the Memory Working Set Bytes and Max value
  

To pass secrets, configuration values to Azure Container Apps we can use the Azure CLI or the Azure Portal.

To pass an environment variable value to toe Azure Container App using the Azure CLI execute the command in a terminal

az containerapp update --name <app-name> --resource-group <rg> \
  --set-env-vars NODE_OPTIONS="--max-old-space-size=4096"

To use the Azure Portal web interface

• Log into the Azure Portal at https://portal.azure.com
• On the Container Apps page select the application
• In the Application, Containers, page open the Environment variables tab and add a new environment variable. Click the Save as a new revision button
  

Azure Container Apps (ACA) run containers in a serverless environment with zero environment maintenance requirement. To deploy a new application in Azure Container Apps follow the steps at Deploy a web application in Azure Container Apps (ACA)

To deploy a new version of the same app in Azure Container Apps

• Log in to the Azure Portal at https://portal.azure.com
• In the top search bar search for container apps and select Container Apps in the list
  
• In the application list click the name of the application
  
• In the Application menu select Revisions and Replicas
  
• Click the Create new revision button
  
• Select a prior revision as a base configuration, enter a name for the new provision, and select the container image. Click the Next: Scale button
  
• If you always want to have at least one replica running for immediate availability, select 1 for Min replicas. If volumes are needed for the app, click the Next: Volumes button, otherwise click the Create button
  
• Click the Notifications button to monitor the progress
  

To push a Docker container image to the Azure Container Registry

Build the Docker container image

• Navigate to https://www.docker.com/ and create a free Docker Hub account
• Install the Docker Desktop application
• Start the Docker Desktop application
• Open a terminal and navigate to the application root directory where the Dockerfile is located
• In the terminal execute the command
  docker build -t MY_IMAGE .
• Push the image to the registry

	az login
	az acr login --name MY_REGISTRY
	docker tag MY_IMAGE:latest MY_REGISTRY.azurecr.io/MY_REPOSITORY/MY_IMAGE:latest
	docker push MY_REGISTRY.azurecr.io/MY_REPOSITORY/MY_IMAGE:latest

Troubleshooting

Error message when building the image

docker build -t …:latest .
ERROR: error during connect: Head “http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/_ping”: open //./pipe/dockerDesktopLinuxEngine: The system cannot find the file specified.

Solution

Start the Docker Desktop application

Error message when pushing the image to Azure Container Registry

error from registry: authentication required, visit https://aka.ms/acr/authorization for more information. CorrelationId: 2a33d0ac-091c-4158-b927-397c6e5692cf

Solution

The Azure Container Registry hosts container images for deployment in any of the container hosting services.

Create a new Azure Container Registry

• Log into the Azure Portal at http://portal.azure.com
• In the search bar search for container registry and select Container registries
  
• Click the Create button to create a new Azure container registry
  
• Set the values and click the Next: Networking button
  
• You need a Premium subscription to set up private access for better security. Click the Next: Encryption button
  
• Encryption is also only available for Premium subscriptions. Click the Next: Tags button
  
• Set up tags for better cost reporting
  
• If you want to automate the registry creation in the future, click the Download a template for automation link. Click the Create button to create the registry.
  

If you have created an Azure Resource Group, and want to change the name, unfortunately you cannot rename it. To change the name create a new resource group and move all resources from the old group to the new one.

Create a new resource group

• In the main Azure page search for resource groups and select Resource groups from the list
  
• Click the Create button and select Create new resource group
  
• Enter the name of the resource group and click the Review + cerate button
  
• Click the Automation link to download the creation script
  
• Click the Cerate button to create the resource group
  

Move the resources from the old resource group to the new one

• Open the old resource group, and click the first resource
• Click the move link next to the old resource group name
  
• Select the new resource group from the list
  
• The validation status displays the current activity
  
• Some resources cannot be moved
  
  • Restore points
• If the resource can be moved, click the Next button at the bottom of the page
  
• Select the checkbox and click the Move button
  
• To monitor the progress of the move click the Notifications icon. The source and destination resource groups are locked during the move, so only one move can be processed at a time.
  
• As the resource has been moved, the refresh button cannot display the new parent information. Go back to the Resource Group list and select the old resource group again top move the rest of the resources.
  

To deploy an application to Azure Container Apps

• Log into the Azure Portal at http://portal.azure.com
• In the top search bar search for container apps and select Container Apps in the list
  
• Click the arrow next to Create and select Container App
  
• Create a new Resource Group if needed, enter the app name (all lower case characters), select the Region. Select the environment, or click the Create new environment link. The West US 3 is the newest region in the west, located in Phoenix, Arizona, and provides Availability Zone support. Although West US is located in California, but does not provide availability zone support. Availability zone support offers very important redundancy within the same region in case of network and power outage, and natural disasters. The data transfer between availability zones within the same region is free, and many services can utilize the redundancy.
  
• Enter the environment name, and select the zone redundancy, and click the Create button. For non mission critical apps the zone redundancy is usually not necessary, as it doubles the infrastructure cost.
  
• Click the Next: Container button
  
• Container
  • If there is no available container image to deploy, select Use quickstart image. This will deploy a temporary Hello World web application.
    
  • If you already have a container image to deploy, select the image location and resource requirements. Click the Next: Ingress button
    
    
    
• For web applications enable ingress and traffic from anywhere, set the port to 80. Click the Next: Tags button
  
• Add a name tag to the application for cost tracking, and click the Next: Review + create button
  
• When the validation Passed
  
  Click the Download a template for automation link at the bottom of the page
  
• On the next page click the Download button
  
• In the upper right corner click the X to close the Template page
  
• At the bottom of the page click the Create button
  
• When the deployment is complete, click the Go to resource button
  
• In the upper right of the page click the application URL link to open it in the browser.