These instructions allow you to intall psql, pg_dump & pg_restore without a full installation of postgresql.
First, install libpq via homebrew
brew doctor
brew update
brew install libpq
These instructions allow you to intall psql, pg_dump & pg_restore without a full installation of postgresql.
First, install libpq via homebrew
brew doctor
brew update
brew install libpq
| package main | |
| import ( | |
| "errors" | |
| "fmt" | |
| "strconv" | |
| "gonum.org/v1/gonum/graph" | |
| "gonum.org/v1/gonum/graph/multi" | |
| ) |
(1) FEATURE EXPECTATIONS [5 min]
(1) Use cases
(2) Scenarios that will not be covered
(3) Who will use
(4) How many will use
(5) Usage patterns
| version: '2' | |
| services: | |
| dozzle: | |
| image: amir20/dozzle:latest | |
| container_name: dozzle | |
| ports: | |
| - 8888:8080 | |
| volumes: | |
| - /var/run/docker.sock:/var/run/docker.sock |
| { | |
| "Command": "skin", | |
| "Skins": [ | |
| { | |
| "Item Shortname": "fun.guitar", | |
| "Skins": [ | |
| 1287805625, | |
| 814874910, | |
| 1186248895, | |
| 1196457681, |
If you're wondering what Gateway Intents are, what Privileged Intents are, why your bot can't see statuses, or why your bot can't see member joins anymore, then this page should explain it to you!
if you do not know what intents are, please read this entire page
First, a short explanation of how bots work: bots can make requests over the REST (HTTP) API to retreive information and do actions, and they get real-time updates from Discord in the form of websocket gateway events. They can also fetch server members via the gateway.
Examples of gateway events you are probably familiar with are Message Create (a message was sent) and Guild Member Add (a user joined a server).
| import apiProvider from './provider'; | |
| export class ApiCore { | |
| constructor(options) { | |
| if (options.getAll) { | |
| this.getAll = () => { | |
| return apiProvider.getAll(options.url); | |
| }; | |
| } |
| #!/usr/bin/env python3 | |
| # | |
| # Nokia/Alcatel-Lucent router backup configuration tool | |
| # | |
| # Features: | |
| # - Unpack/repack .cfg files generated from the backup and restore functionnality | |
| # in order to modify the full router configuration | |
| # - Decrypt/encrypt the passwords/secret values present in the configuration |
Note on sizes: a lot of those might be inaccurate as there might be many microservices required aside from the core release/docker image. I haven't tested these recently so I'm not sure
In /usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf and /usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf:
[Element Internal Mic Boost] set volume to zero.[Element Int Mic Boost] set volume to zero.[Element Mic Boost] set volume to zeroFind your source name from the following command; mine is alsa_input.pci-0000_00_1f.3.analog-stereo
$ pacmd list-sources | grep 'name:.*input'
Edit /etc/pulse/default.pa and add the following lines, where INPUT_NAME is name of the input source from above step: