Rick Cogley RickCogley

Background

Deno Deploy is an excellent, performant and cost-effective service geared toward hosting Deno apps at the edge. It can easily host a folder of static HTML files, if you provide an index.ts to launch something like "oak" to serve them (example index.ts below).

(It's important to note that it's still officially considered beta as of May 2023, and there have been some surprising periods of downtime over the past few months... just be sure to keep that in mind)

Hugo is a phenomenally fast-building and mature SSG, which can produce a folder of static files, but requires a build step like hugo --gc --minify --verbose --baseURL=$HUGOBASEURL --ignoreCache to generate them.

Below is a yaml file you would place in your project's .github/workflows folder. If you link your Deno Deploy project using Github Actions instead of specifying an index file, it will defer to what's in this. In this case, the Hugo files generated into public are being serv

This set of "low-hanging fruit" security headers can be set for most websites to cover a range or potential problems and get a better ranking on https://securityheaders.com/. You should not that this does not cover CORS/CSP headers, because they are not "one size fits all" and require trial and error to set. Among these standard headers, the "Permissions-Policy" (previously "Feature-Policy") header requires a bit of thought, and trial and error, so be sure to review and edit as appropriate.

Generally speaking, although you can set some of these directly in HTML, you usually set security headers on the server side, for example in a .htaccess file on Apache, in a file like vercel.json in the root of your site if you're hosting on Vercel (similar for Netlify and can be done in their config file, see below), or under "web rules, header rules" UI if you're hosting on WP Engine (see screenshot).

It's also super simple to implement a static HTML site deployed on Deno Deploy, and served via Deno Oak. See th

MacOS Big Sur 11.2
Composer version 2.0.9 2021-01-27 16:09:27, installed via brew

Methods of Signing with GPG

There are now two ways to approach this:

Using gpg and generating keys
Using Kryptonite by krypt.co

This Gist explains how to do this using gpg in a step-by-step fashion. Kryptonite is actually wickedly easy to use-but you will still need to follow the instructions

For using a GUI-based GIT tool such as Tower or Github Desktop, follow the steps here for signing with either GPG or Krypt.co.

The current MailMate EagleFiler archive script works with the top-most open library, but we'd like it to work with a specific library.

add Bash Shell Script

Add line 10, env var to specify path to the .eflibrary file.
Add on line 14, an arg 3, using that var.

EagleFilerImport.scpt v2

Add a third _argv on line 3.

	<details>
	<summary>Click me...</summary>
	I just opened without css or javascript.
	</details>

	name: 'Apex Up'
	description: 'Deploy & manage Up applications'
	inputs:
	stage:
	description: 'Up stage to deploy'
	required: true
	verbose:
	description: 'Produce verbose output'
	required: false
	runs:

	# FORGE CONFIG (DOT NOT REMOVE!)
	include forge-conf/mydomain.com/before/*;

	server {
	listen 443 ssl;
	listen [::]:443 ssl;
	server_name mydomain.com;
	root /home/forge/mydomain.com/;

	# FORGE SSL (DO NOT REMOVE!)

	hs.hotkey.bind(ctrl_opt_cmd, "Left", function()
	local win = hs.window.focusedWindow()
	local f = win:frame()
	local screen = win:screen()
	local max = screen:frame()

	f.x = max.x
	f.y = max.y
	f.w = max.w / 2
	f.h = max.h