| import { config } from 'dotenv' | |
| import Shopify from 'shopify-api-node' | |
| import cryptographer from '@brixtol/cryptographer' | |
| config() | |
| export const crypto = cryptographer(process.env.SHOPIFY_AUTH_SECRET) | |
| /** | |
| * Request Headers |
| daemon off; | |
| worker_processes 1; | |
| error_log logs/error.log; | |
| events { | |
| worker_connections 1024; | |
| } | |
| http { | |
| include mime.types; |
This is a Hashicorp Terraform module that provisions an AWS EC2 instance
for the purpose of running a given docker-compose.yml file.
# ===== OUR MAGIC DOCKER-COMPOSE.YML FILE HERE =====
# It is also possible to get Terraform to read an external `docker-compose.yml`
# file and load it into this variable.
# We'll be showing off a demo nginx page.
| // roughish AMP attribute types for JSX/TypeScript | |
| // Source: https://playground.amp.dev/amphtml-hint.json | |
| // https://github.com/Microsoft/TypeScript/issues/15449 | |
| // https://stackoverflow.com/questions/50585952/typescript-and-google-amp-property-amp-img-does-not-exist-on-type-jsx-intrin | |
| import * as React from 'react'; | |
| // why null ? | |
| type _ANY = any; | |
| type _ANYS = any; | |
| declare module 'react' { | |
| interface HTMLAttributes<T> { |
Vertical decomposition. Creating cohesive services
One of the biggest misconceptions about services is that a service is an independent deployable unit, i.e., service equals process. With this view, we are defining services according to how components are physically deployed. In our example, since it’s clear that the backend admin runs in its own process/container, we consider it to be a service.
But this definition of a service is wrong. Rather you need to define your services in terms of business capabilities. The deployment aspect of the system doesn’t have to be correlated to how the system has been divided into logical services. For example, a single service might run in different components/processes, and a single component might contain parts of multiple services. Once you start thinking of services in terms of business capabilities rather than deployment units, a whole world of options open.
What are the Admin UI
This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.
While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Web Components</title> | |
| <style> | |
| body { | |
| font-family: 'Helvetica Neue'; | |
| } | |
| </style> |
