These are NOT product / license keys that are valid for Windows activation.
These keys only select the edition of Windows to install during setup, but they do not activate or license the installation.
CentOS, Ubuntu, Slackware, etc. Whatever Linux-based OS it is, you can create a bootable USB for it by using a Mac.
Download it, copy it, whatever it takes to prepare that Linux-based OS .iso file
import 'dart:math'; | |
import 'dart:ui'; | |
import 'package:flutter/material.dart'; | |
import 'package:google_maps_flutter/google_maps_flutter.dart'; | |
class MarkerGenerator { | |
final _markerSize; | |
double _circleStrokeWidth; | |
double _circleOffset; |
#!/bin/bash | |
if [ -z "$1" ]; then | |
echo "Usage: git pr [clean] [<remote>] <id-or-url>" | |
echo "" | |
echo "Examples:" | |
echo "git pr 42 --> git fetch origin pull/42/head:pr/origin/42" | |
echo "git pr upstream 42 --> git fetch upstream pull/42/head:pr/upstream/42" | |
echo "git pr https://github.com/peerigon/phridge/pull/1 --> git fetch https://github.com/peerigon/phridge.git pull/1/head:pr/peerigon/phridge/1" | |
# echo "git pr clean --> Deletes all branches that match pr/*/* and pr/*/*/*" |
This API uses POST
request to communicate and HTTP response codes to indenticate status and errors. All responses come in standard JSON. All requests must include a content-type
of application/json
and the body must be valid JSON.
200: Success
400: Bad request
401: Unauthorized
404: Cannot be found
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
#encoding: utf-8 | |
require "fileutils" | |
namespace :my_db do desc "Backup project database. Options: DIR=backups RAILS_ENV=production MAX=7" | |
desc "usage - bundle exec rake my_db:backup RAILS_ENV=production MAX=15 DIR=db/db.bak" | |
task :backup => [:environment] do | |
# config base dir | |
datestamp = Time.now.strftime("%Y%m%d%H%M") | |
base_path = Rails.root | |
backup_folder = File.join(base_path, ENV["DIR"] || "backups") | |
FileUtils.mkdir_p(backup_folder) unless File.exist?(backup_folder) |
namespace :db do desc "Backup project database. Options: DIR=backups RAILS_ENV=production MAX=7" | |
task :backup => [:environment] do | |
datestamp = Time.now.strftime("%Y-%m-%d_%H-%M-%S") | |
base_path = Rails.root | |
base_path = File.join(base_path, ENV["DIR"] || "backups") | |
backup_base = File.join(base_path, 'db_backups') | |
backup_folder = File.join(backup_base, datestamp) | |
backup_file = File.join(backup_folder, "#{RAILS_ENV}_dump.sql") | |
FileUtils.mkdir_p(backup_folder) | |
db_config = ActiveRecord::Base.configurations[RAILS_ENV] |
usage: | |
letsencrypt [SUBCOMMAND] [options] [-d domain] [-d domain] ... | |
The Let's Encrypt agent can obtain and install HTTPS/TLS/SSL certificates. By | |
default, it will attempt to use a webserver both for obtaining and installing | |
the cert. Major SUBCOMMANDS are: | |
(default) run Obtain & install a cert in your current webserver | |
certonly Obtain cert, but do not install it (aka "auth") | |
install Install a previously obtained cert in a server |