lindleyw

Given an accounting database where:

• All changes to the database must be performed by a job posting process
• The database at the end of each posting will be marked with a GUID
• Each job posting will be performed through a job queue (e.g., Minion)
• Each job queue entry will be marked with the starting ("before") and ending ("after") GUID, and optionally, a log of all database modifications (e.g., SQL commands) performed

The following should be true:

• There will exist an audit trail of postings and modifications to the database in the job queue log

lindleyw

#!/usr/bin/env perl

use Mojolicious::Lite;

get '/' => sub {
    my $self = shift;
    $self->render(template => 'index');
};

app->start;

lindleyw

plugin 'Yancy' => {
    backend     => 'sqlite:' . app->config->{dbname},
    collections => {
        minion_jobs => {
            type       => 'object',
            properties => {
                id => {
                    type     => 'integer',
                    readOnly => 1,
                },

lindleyw

diff --git a/lib/Mojo/UserAgent.pm b/lib/Mojo/UserAgent.pm
index ebe9537..25f2160 100644
--- a/lib/Mojo/UserAgent.pm
+++ b/lib/Mojo/UserAgent.pm
@@ -84,18 +84,19 @@ sub _connect {
   if (my $local = $self->local_address) { $options{local_address} = $local }
   $options{handle} = $handle if $handle;
 
-  # SOCKS
-  if ($proto eq 'socks') {

lindleyw

Mojolicious::Lite;
use Mojo::URL;

# Template with browser-side code
get '/' => 'index';
 
# WebSocket echo service
websocket '/echo' => sub {
  my $c = shift;
 

lindleyw

#!/usr/env/perl

use Pod::Simple::SimpleTree;

use warnings;
use strict;

use v5.20;
use feature 'signatures';
no warnings 'experimental::signatures';

lindleyw

Hacking (in the original, good sense) for fun and profit since 1977