I have this abstraction in my application code called a "CloudFile". This is where I store in the database information about
files on S3 and it gives me a resource for other resources to own. For example, a user would have an avatar_cloud_file_id.
On the front-end, I would load this relationship and display the avatar with user.avatar_cloud_file.download_url
defmodule RL.CloudFile do
use Ecto.Schema
import Ecto.Changeset
@timestamps_opts type: :utc_datetime_usec
| <video id="player" autoplay muted playsinline> </video> | |
| <button id="capture">Capture</button> | |
| <canvas id="canvas" width=320 height=240></canvas> | |
| <script> | |
| const player = document.getElementById('player'); | |
| const canvas = document.getElementById('canvas'); | |
| const context = canvas.getContext('2d'); | |
| const captureButton = document.getElementById('capture'); | |
| const constraints = { |
<video… tag.body tag and click Edit as HTML<body>
<a href="url-you-copied">download</a>
...
| javascript:(function() {document.querySelectorAll('.js-inline-annotations').forEach(function(annotation) {if (annotation.innerText.includes('coverbot')) {annotation.remove();}});})(); |
| (.*(\n|$)){3} |
From April 10 to May 2, 2024, I did all the work myself to get SOC 2 Type II certified. I'm now half way through the observation period to get Type II. The observation period is easy, you just have to babysit the controls. Getting to Type I is much harder. It took me somewhere around 100 hours.
SOC 2 is a security framework that, for many customers, eliminates the need to have you, as a vendor, fill out a lengthy security questionnaire. The SOC 2 controls and audits ask pretty much all the questions you'd get from a customer's security team. In fact, that is a great way to think about SOC 2. It's essentially a very thorough questionnaire you fill out once, an independent auditor forms an opinion of it in a report, and you share with all your customers.
There are two parts to SOC 2. The initial audit, where an auditor writes a Type I report sharing their opinion of your current setup. Then there's a 3 month observ
| locals { | |
| function_name = "${var.space}-webhook-receiver" | |
| } | |
| resource "google_pubsub_topic" "webhook_events" { | |
| name = "${var.space}-webhook-events" | |
| message_retention_duration = "432000s" | |
| } |
Here's an ecto changeset validation for urls:
@doc """
validates field is a valid url
## Examples
iex> Ecto.Changeset.cast(%ZB.Account{}, %{"website" => "https://www.zipbooks.com"}, [:website])
...> |> Utils.Changeset.validate_url(:website)
...> |> Map.get(:valid?)
I will often run this command to make sure all my docker containers are stopped and removed before running docker-compose up. Sometimes when you restart your system, old containers will start back up automatically in the background.
docker stop $(docker ps -aq) && docker rm $(docker ps -aq)
| import UIKit | |
| // All you do is assign this class to a segue in your storyboard and you're done | |
| class BottomCardSegue: UIStoryboardSegue { | |
| private var selfRetainer: BottomCardSegue? = nil | |
| override func perform() { | |
| destination.transitioningDelegate = self |