Clojurians Log v2

@cgrand: I now get a different error git pull; lein install // this works fine restart boot repl (require 'portkey.core) ==>

2. Unhandled clojure.lang.Compiler$CompilerException
   Error compiling cheshire/core.clj at (1:1)

1. Caused by java.lang.Exception
   namespace 'cheshire.factory' not found

                  core.clj:  659  clojure.core/apply
                  core.clj: 5889  clojure.core/load-libs
                  core.clj: 5873  clojure.core/load-libs
               RestFn.java:  137  clojure.lang.RestFn/applyTo
                  core.clj:  659  clojure.core/apply
                  core.clj: 5911  clojure.core/require
                  core.clj: 5911  clojure.core/require
               RestFn.java:  457  clojure.lang.RestFn/invoke
                  core.clj:    1  cheshire.core/eval12329/loading--auto--
                  core.clj:    1  cheshire.core/eval12329
                  core.clj:    1  cheshire.core/eval12329
             Compiler.java: 7005  clojure.lang.Compiler/eval
             Compiler.java: 6994  clojure.lang.Compiler/eval
             Compiler.java: 7457  clojure.lang.Compiler/load
                   RT.java:  374  clojure.lang.RT/loadResourceScript
                   RT.java:  365  clojure.lang.RT/loadResourceScript
                   RT.java:  455  clojure.lang.RT/load
                   RT.java:  421  clojure.lang.RT/load
                  core.clj: 6008  clojure.core/load/fn
                  core.clj: 6007  clojure.core/load
                  core.clj: 5991  clojure.core/load
               RestFn.java:  408  clojure.lang.RestFn/invoke
                  core.clj: 5812  clojure.core/load-one
                  core.clj: 5807  clojure.core/load-one
                  core.clj: 5852  clojure.core/load-lib/fn
                  core.clj: 5851  clojure.core/load-lib
                  core.clj: 5832  clojure.core/load-lib
               RestFn.java:  142  clojure.lang.RestFn/applyTo
                  core.clj:  659  clojure.core/apply
                  core.clj: 5889  clojure.core/load-libs
                  core.clj: 5873  clojure.core/load-libs
               RestFn.java:  137  clojure.lang.RestFn/applyTo
                  core.clj:  659  clojure.core/apply
                  core.clj: 5911  clojure.core/require
                  core.clj: 5911  clojure.core/require
               RestFn.java:  805  clojure.lang.RestFn/invoke
                  core.clj:    1  portkey.core/eval12321/loading--auto--
                  core.clj:    1  portkey.core/eval12321
                  core.clj:    1  portkey.core/eval12321
             Compiler.java: 7005  clojure.lang.Compiler/eval
             Compiler.java: 6994  clojure.lang.Compiler/eval
             Compiler.java: 7457  clojure.lang.Compiler/load
                   RT.java:  374  clojure.lang.RT/loadResourceScript
                   RT.java:  365  clojure.lang.RT/loadResourceScript
                   RT.java:  455  clojure.lang.RT/load
                   RT.java:  421  clojure.lang.RT/load
                  core.clj: 6008  clojure.core/load/fn
                  core.clj: 6007  clojure.core/load
                  core.clj: 5991  clojure.core/load
               RestFn.java:  408  clojure.lang.RestFn/invoke
                  core.clj: 5812  clojure.core/load-one
                  core.clj: 5807  clojure.core/load-one

@baptiste-from-paris: ping

any idea how to help with

Unable to find a region via the region provider chain. Must provide
   an explicit region in the builder or setup environment to supply a
   region.

this is from running pk/mount!

so I believe porkey installed find under boot, and my problem is now AWS AMI issues

@cgrand: please ignore my last 2 bug reports -- they were all resolved with "update to the latest version of whatever package you're using"

@qqq I am only in one region, I don’t why it can’t find your region

actually, that's not the issue

my problem is: I don't know how to setup AMI, I don't have any config at all

how do I learn how to setup this up for lambda ?

I only used my account with a lot of instances in europe

so pre-configured

lol, I may have to solve https://github.com/portkey-cloud/portkey/issues/30 then

lol, yes

aws is great and there are a lots of resources

in ~/.aws/config there should be region = xxxx under the profile you use (the section [default] is used if not explicitly selected with say AWS_PROFILE environment variable)

oh right

forgot that

[default]
region = eu-west-1

for me

but yeah, a script that checks to necessary config on creates say a IAM user with suitable inline policy for repl use would be neat

script == (pk/install)

so I'm readinga book on aws lambda

is it just me, or is lambda about to completely shake up startup land?

seems like it's going to cut down # engineers required by atleast 90%

how do you figure that?

and if that is the case, that would be very good news indeed… there is currently a shortage of software engineering talent

the 90% is not a researched number; I'm the Founder of a tiny webapp, and I'm just amazed at the amount of things I don't have to do:

manage ubuntu installs, manage mysql, manage networking, manage ssl, manage nginx, manage devops, manage backups, scripts for automating jvm deploy, etc ...

it's basically "treat auroradb / dynamodb as state; write stateless functions [which manip db] in aws lambda", aws takes care of the rest

this is insane, it basically says: if you can reduce your server side into a bunch of db transactions, aws will auto scale everything for you

oh, you mean we can drop the “ops” part from devops and just focus on developing our solutions

but in the long run, with more complex applications, I doubt the ops part is 90% or anywhere near that

you're right, I should clarify the narrow context I was considering:

namely, things that would take 10 engineers to do pre-AWS can probably be bootstrapped by a solo engineer in 2017

I completely agree that "in the limiting case, there may not be much savings", but for founders, this can be the difference between tgettinga company off the ground or not

that makes sense, it certainly is a lot faster to get something started

there's some amount of ops work, configuration of the things in AWS but people get better at that

what's interesting is that there is a corporate story as well, since AWS can delegate auth with say SAML

is there a good logging story that does not require going to the cloudwatch page in the aws console?

perhaps not specific to portkey, but for jvm on the aws

something like https://github.com/jorgebastida/awslogs for tailing while making calls

The good side of CloudWatch and related services is that they are there from get go, although some of them are a bit arcane

Just made a commit to powderkeg that should be backported to portkey. Generally I’m leaning towards putting a warning every time a sun.* class is serialized