iamdbc

# file location: /etc/logrotate.d

/home/deploy/app/your-app/shared/log/*.log {
  daily
  missingok
  rotate 14
  compress
  delaycompress
  dateext
  notifempty

giannisp

After automatically updating Postgres to 10.0 via Homebrew, the pg_ctl start command didn't work.
The error was "The data directory was initialized by PostgreSQL version 9.6, which is not compatible with this version 10.0."

Database files have to be updated before starting the server, here are the steps that had to be followed:

# need to have both 9.6.x and latest 10.0 installed, and keep 10.0 as default
brew unlink postgresql
brew install postgresql@9.6
brew unlink postgresql@9.6
brew link postgresql

waffleau

  def self.extract_dominant_colors(image_path, quantity=5, threshold=0.01)
    image = MiniMagick::Image.open(image_path)

    # Get image histogram
    result = image.run_command('convert', image_path, '-format', '%c', '-colors', quantity, '-depth', 8, 'histogram:info:')
    
    # Extract colors and frequencies from result
    frequencies = result.scan(/([0-9]+)\:/).flatten.map { |m| m.to_f }
    hex_values = result.scan(/(\#[0-9ABCDEF]{6,8})/).flatten
    total_frequencies = frequencies.reduce(:+).to_f

trnila

#!/bin/sh
container=$1
pass=$2

if [ -z "$container" ] || [ -z "$pass" ]; then
        echo "usage: $0 container newRootPassword"
        exit
fi

mysql_image=$(docker inspect $container --format "{{ .Config.Image }}")

bszwej

const http = require('http');
const server = http.createServer();

server.on('request', (request, response) => {
    let body = [];
    request.on('data', (chunk) => {
        body.push(chunk);
    }).on('end', () => {
        body = Buffer.concat(body).toString();

soultech67

Preamble

On OS/X Sierra, after recently running a brew update I started receiving the error message Sorry, you can't use byebug without Readline when trying to run some rake tasks in my ruby project folder. I observed this in projects and gems that include byebug or pry in their Gemfile or gem.spec. I've found in my googling that many begin encountering this error message after running a brew update but there are other triggering conditions as well.

>> rake aws:show_config
WARN: Unresolved specs during Gem::Specification.reset:
      mime-types (>= 0)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
 Sorry, you can't use byebug without Readline. To solve this, you need to

cschiewek

To forward X11 from inside a docker container to a host running macOS

1. Install XQuartz: https://www.xquartz.org/
2. Launch XQuartz. Under the XQuartz menu, select Preferences
3. Go to the security tab and ensure "Allow connections from network clients" is checked.
4. Run xhost + ${hostname} to allow connections to the macOS host *
5. Setup a HOSTNAME env var export HOSTNAME=`hostname`*
6. Add the following to your docker-compose:

 environment:

tekei

---
- hosts: localhost
  connection: local
  become: yes
  tasks:
  - name: remove ipv6 hosts entry
    shell: sed -i -e '/::/d' -e '/IPv6/d' /etc/hosts
  - name: find ipv6 kernel parameter
    shell: sysctl --all | egrep '^net.ipv6\..*disable' | awk '{print $1}'
    register: ipv6_sysctl_list

rashivkp

{% if site.linkedin_username %}
<li>
  <a href="https://www.linkedin.com/in/{{ site.linkedin_username }}">
    <span class="icon  icon--linkedin">
      <svg viewBox="0 50 512 512" >
        <path fill="#828282" d="M150.65,100.682c0,27.992-22.508,50.683-50.273,50.683c-27.765,0-50.273-22.691-50.273-50.683
        C50.104,72.691,72.612,50,100.377,50C128.143,50,150.65,72.691,150.65,100.682z M143.294,187.333H58.277V462h85.017V187.333z
        M279.195,187.333h-81.541V462h81.541c0,0,0-101.877,0-144.181c0-38.624,17.779-61.615,51.807-61.615
        c31.268,0,46.289,22.071,46.289,61.615c0,39.545,0,144.181,0,144.181h84.605c0,0,0-100.344,0-173.915
        s-41.689-109.131-99.934-109.131s-82.768,45.369-82.768,45.369V187.333z"/>

drkarl

Linux Backup Solutions

I've been looking for the best Linux backup system, and also reading lots of HN comments.

Instead of putting pros and cons of every backup system I'll just list some deal-breakers which would disqualify them.

Also I would like that you, the HN community, would add more deal breakers for these or other backup systems if you know some more and at the same time, if you have data to disprove some of the deal-breakers listed here (benchmarks, info about something being true for older releases but is fixed on newer releases), please share it so that I can edit this list accordingly.

Amanda (comments by sammcj)

• It has a lot of management overhead and that's a problem if you don't have time for a full time backup administrator.