lleyton

Open Source Business Challenges and Reality

Original Japanese note here.

Original Author: Rui Ueyama (creator of the mold linker)

Translated by @windowsboy111

Minimally edited by @lleyton

mamiu

k3d exec as root user into pod / container

Let's assume we have a pod called nginx running in the namespace nginx-test.

kubectl create namespace nginx-test
kubectl run nginx --image=nginx -n nginx-test

1. Check if the current cluster is a k3d cluster

den-crane

$ cat /etc/clickhouse-server/conf.d/clusters.xml
<?xml version="1.0" ?>
<yandex>
    <remote_servers>
        <xxx>
            <shard>
                <replica> <host>h1</host> <port>9000</port></replica>
            </shard>
....
        </xxx>

RollingStar

# don't copy paste this into your config. It's tailored to me and I haven't really stress-tested it outside of my own use. Also, I was mostly using this in 2017-2019 and features may have changed.

# Some plugins have been retired and I haven't migrated yet. copyartifacts is the best example of this.

# Just use this as a starting point to learn about advanced, undocumented/poorly-documented features of beets.

directory: e:\Music\
library: e:\Music\beetslibrary.bib

#copyartifactspy3 chroma scrub

danieldogeanu

You should not use the Open SSH client that comes with Git for Windows. Instead, Windows 10 has its own implementation of Open SSH that is integrated with the system. To achieve this:

1. Start the ssh-agent from Windows Services:

• Type Services in the Start Menu or Win+R and then type services.msc to launch the Services window;
• Find the OpenSSH Authentication Agent in the list and double click on it;
• In the OpenSSH Authentication Agent Properties window that appears, choose Automatic from the Startup type: dropdown and click Start from Service status:. Make sure it now says Service status: Running.

2. Configure Git to use the Windows 10 implementation of OpenSSH by issuing the following command in Powershell:

git config --global core.sshCommand C:/Windows/System32/OpenSSH/ssh.exe

omissis

package shorturl_test

import (
	"fmt"
	"github.com/omissis/ristretto/internal/domain/shorturl"
	"github.com/omissis/ristretto/internal/test/mock"
	"reflect"
	"testing"
)

tkrotoff

Charts are from different sources and thus colors are inconsistent, please carefully read the chart's legends.

Like this? Check React Native vs Flutter: https://gist.github.com/tkrotoff/93f5278a4e8df7e5f6928eff98684979

Stack Overflow trends

https://insights.stackoverflow.com/trends?tags=reactjs%2Cvue.js%2Cangular%2Csvelte%2Cangularjs%2Cvuejs3

park-brian

/**
 * Advanced Window Snap
 * Snaps the active window to a position within a user-defined grid.
 *
 * @author Andrew Moore <[email protected]>
 * @contributor jballi
 * @contributor park-brian
 * @contributor shinywong
 * @version 1.2
 */

whoisryosuke

import React, {Component} from 'react'
import Router from 'next/router'
import AuthService from './AuthService'

export default function withAuth(AuthComponent) {
    const Auth = new AuthService('http://localhost')
    return class Authenticated extends Component {

      static async getInitialProps(ctx) {
        // Ensures material-ui renders the correct css prefixes server-side

ravibhure

In your local clone of your forked repository, you can add the original GitHub repository as a "remote". ("Remotes" are like nicknames for the URLs of repositories - origin is one, for example.) Then you can fetch all the branches from that upstream repository, and rebase your work to continue working on the upstream version. In terms of commands that might look like:

Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

Fetch all the branches of that remote into remote-tracking branches, such as upstream/master:

git fetch upstream