kyptov

Общие упрощенные понятия. Возможно существуют способы задать другое поведение нежели данное упощенное.

Понятия

• producer - отправитель, программный код, который отправляет сообщение.
• consumer - получатель, программный код, который должен получить сообшение.
• exchange - обменник, функционал RabbitMQ, получает сообщение с заданными параметрами от отправителя и:
  • может сбросить(удалить) сообщение или вернуть отправителю (зависит от атрибутов сообщения),
  • может отправить сообщение в очередь,
  • может отправить сообщение в несколько очередей (сообщение будет скопировано для каждой очереди)
• queue - очередь, функционал RabbitMQ, хранит все сообщения и раздает их получателям.
• message - сообщение, содержит атрибуты необходимые RabbitMQ, а также данные для передачи от отправителя к получателю

AtulKsol

psql: FATAL: Peer authentication failed for user “postgres” (or any user)

The connection failed because by default psql connects over UNIX sockets using peer authentication, that requires the current UNIX user to have the same user name as psql. So you will have to create the UNIX user postgres and then login as postgres or use sudo -u postgres psql database-name for accessing the database (and psql should not ask for a password).

If you cannot or do not want to create the UNIX user, like if you just want to connect to your database for ad hoc queries, forcing a socket connection using psql --host=localhost --dbname=database-name --username=postgres (as pointed out by @meyerson answer) will solve your immediate problem.

But if you intend to force password authentication over Unix sockets instead of the peer method, try changing the following pg_hba.conf* line:

from

joshbuchea

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example

hearimm

SELECT LOWER(SUBSTR(COLUMN_NAME,0,1)) || SUBSTR(REPLACE(INITCAP(COLUMN_NAME),'_',''),2) 
FROM  ALL_TAB_COLS
WHERE TABLE_NAME = 'ADC_DL_MODEL'
;

--from : HELLO_WORLD
--to : helloWorld

existme

import com.intellij.database.model.DasTable
import com.intellij.database.model.ObjectKind
import com.intellij.database.util.Case
import com.intellij.database.util.DasUtil

SEPARATOR = ","
QUOTE     = "\""
NEWLINE = System.getProperty("line.separator")
SEPARATOR = File.separator
SPACING = "    "

dennisobrien

/*
* DataGrip extension to export results to markdown.
* The markdown table format is supported by Github and Jira.  I haven't tested others.
* 
* Tested on DataGrip 2016.2.2
* - Open the File view.  View -> Tool Windows -> Files
* - Activate the "Scratches" tab.  You should see "Files", "Scopes", and "Scratches".
* - Copy this file to Extensions/Database Tools and SQL/data/extractors/Markdown.JavaScript.md.js
* - Run a query with some results.
* - Change the export format to Markdown.JavaScript.md.js and click "To Clipboard".

amihaiemil

This file contains the review of the codebase as it was on 01.10.2017:

Project: https://github.com/mgramin/sql-boot

Language: Java

Main Contributor: https://www.github.com/mgramin

CLOC (cloc . on the root directory):

yonglai

---
- name: Install docker
  gather_facts: No
  hosts: default

  tasks:
    - name: Install yum utils
      yum:
        name: yum-utils
        state: latest

berkayunal

Loading variables from .env files in Ansible

Ansible has various ways of looking up data from outside sources, including plain text password files, CSV files and INI files. But it doesn't seem to have a lookup for .env files, as used in Laravel projects, also available for PHP, Ruby, Node.js, Python and others.

One option is to launch Ansible with the Ruby dotenv command line script... But that requires Ruby, which seems like overkill to me.

So here is a simpler solution that I use. It consists of:

1. The .env file itself
2. A small shell script that loads the .env file into environment variables - ansible-playbook.sh

leon-sleepinglion

from flask import Flask
from flask_restful import Api, Resource, reqparse

app = Flask(__name__)
api = Api(app)

users = [
    {
        "name": "Nicholas",
        "age": 42,