Hans Petter Wilhelmsen HP

Assigning an object to a belongs_to association does not automatically save the object. It does not save the associated object either.

When you assign an object to a has_one association, that object is automatically saved (in order to update its foreign key).
In addition, any object being replaced is also automatically saved, because its foreign key will change too
If either of these saves fails due to validation errors, then the assignment statement returns false and the assignment itself is cancelled.
If the parent object (the one declaring the has_one association) is unsaved (that is, new_record? returns true) then the child objects are not saved. They will automatically when the parent object is saved.

How to setup Let's Encrypt for Nginx on Ubuntu 18.04 (including IPv6, HTTP/2 and A+ SLL rating)

Let's say you want to host domains first.com and second.com.

Create folders for their files:

Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)

First one found from of

	# See: https://github.com/mongoid/mongoid/blob/identity-map/spec/unit/mongoid/identity_map_spec.rb#L367

	# In order for the identity map to work when using fibers the
	# entire unit of work must happen on the same fiber since it's using
	# thread locals for storage.

	# The following example is correct:
	fiber = Fiber.new do
	Person.find(id)
	Person.find(id) # This query hits the identity map.

	class ArticleImageUploader < ImageUploader

	process :fix_exif_rotation
	process :strip
	process :convert => 'jpg'
	process :quality => 85 # Percentage from 0 - 100

	version :gallery_thumb do
	process :resize_to_fill => Settings.images.article_images.processing.gallery_thumb #44x44
	end

	require 'net/http'

	# WARNING do not use this; it works but is very limited
	def resolve url
	res = Net::HTTP.get_response URI(url)
	if res.code == '301' then res['location']
	else url.to_s
	end
	end

	#!/usr/bin/env ruby -wKU

	# Comments added 6 March 2014.
	# Implementation of the MetaWeblog API for my personal Ruby static blog generator.
	# This is not even nearly idiomatic Ruby. There are all kinds of issues.
	# (What's with the method interiors all being mushed-up together?)
	# But -- it's also worked flawlessly for five years without my having to edit it.
	# It won't work for anyone else as-is — but if it helps anyone
	# to do a MetaWeblog API implementation, then cool.

	DKIM is DomainKeys Identified Mail and is used in mail servers, such as Postfix or Sendmail to sign e-mails and thus authenticating the sender so that a forgery can be detected. It also reduces the possibility of an e-mail being flagged as spam, but it's not a definite prevention.

	A much simpler method is using SPF (Sender Policy Framework) which, in a nutshell, verifies the sender IP address.

	According to the internet, using both should result to ????, PROFIT !!!.

	SPF does not need a specific configuration. Whitelisted servers are listed in a DNS record, TXT or SPF, and an example record is:

	example.com. IN TXT "v=spf1 a mx ~all"