Manjunath Reddy manjufy

Docker issue in Fedora

If you bump into running Docker engine in Fedora, remember to uninstall Docker Desktop as it conflicts with docker service.

Error

Cannot connect to the Docker daemon at unix:///home/{username}/.docker/desktop/docker.sock

The error "Cannot connect to the Docker daemon at unix:///home/{username}/.docker/desktop/docker.sock" typically indicates that Docker is trying to use an incorrect or non-standard socket path (/home/xxx/.docker/desktop/docker.sock), instead of the default path (/var/run/docker.sock). This is especially common if Docker Desktop for Linux was attempted but is not supported on Fedora or if there's a misconfiguration in Docker’s settings.

I'm OK; The Bull Is Dead

By Gopal K. Kapur
Published at Computerworld • JUN 21, 2004 6:00 AM PST

Early in my career, when I worked as an engineer, my boss had a process by which the engineering team was expected to report project status. He insisted that we use the following steps, in the specified order:

Punch line: The facts; no adjectives, adverbs or modifiers. "Milestone 4 wasn't hit on time, and we didn't start Task 8 as planned." Or, "Received charter approval as planned."
Current status: How the punch-line statement affects the project. "Because of the missed milestone, the critical path has been delayed five days."

[20XX-XX-XX] Service Name downtime

This is a blameless Post-mortem.
We will not focus on the past events as they pertain to "could've", "should've", etc.
All follow up action items will be assigned to a team/individual before the end of the meeting.
If the item is not going to be top priority leaving the meeting, don't make it a follow up item.

| | |

Reason for Pull Request

Quality Assurance?

Did we implement test, if so, did it pass?
Did the change add/remove tests? why?
Did the commit decrease quality measurably?
Did the commit introduce possible future technical debt? is it acceptable? → Its always good to get teams opinion and come to conclusion
Did any of the tooling indicate a decrease in maintainability or compliance?

In terms of Operation

Simple NodeJS Cache

Reference:

https://github.com/expressjs/session/blob/master/session/memory.js

https://slynova.io/create-a-simple-cache-system/

Managing gitignores

if you are using multiple languages and would like to ignore default files or folders, just add those files to global gitignore.

Example

.gitignore.global look like this

.DS_Store

	var elastic = require('elasticsearch');

	var client = new elastic.Client({ host: 'localhost:9200' });
	var index = 'myindex';
	var type = 'document';

	(function init() {

	Promise.resolve()
	.then(deleteIndex, handleError)

	"use strict";

	const _ = require("lodash");
	const chalk = require("chalk");
	const Promise = require("bluebird");
	const ServiceBroker = require("../src/service-broker");
	const { MoleculerError } = require("../src/errors");

	// --- SAGA MIDDLEWARE ---
	const SagaMiddleware = function() {

	"use strict";

	const _ = require("lodash");
	const chalk = require("chalk");
	const Promise = require("bluebird");
	const ServiceBroker = require("../src/service-broker");
	const { MoleculerError } = require("../src/errors");

	// --- SAGA MIDDLEWARE ---
	const SagaMiddleware = function() {

	const getDrivers = () => {
	return new Promise((resolve, reject) => {
	setTimeout(() => {
	resolve([
	{
	id: 1,
	name: 'Hamilton'
	},
	{
	id: 1,