Fork me on GitHub
#boot
<
2017-05-19
>
qqq12:05:03

https://github.com/adzerk-oss/boot-beanstalk <-- is this state of the art for using beanstalk with boot ?

dave16:05:41

@qqq as far as i'm aware. at adzerk we've moved away from using beanstalk

dave16:05:57

when we were using it more, i tended to use the aws eb tool to do beanstalk deployments

dave16:05:03

it's pretty good

burbma17:05:34

I’ve got some sql migration files in resources/migrations and I want them to be included in the the uberjar so I can run the migrations in -main of my core ns. I’ve included :resource-paths #{"resources/migrations"} in set-env! but the migration files are not added to the jar. What don’t I understand?

ag18:05:28

has anyone built yarn task yet?

ag18:05:38

npm is telling me to eat shit (I’m trying to use it with a private repo hosted on github)

dave18:05:49

@mmb90 that seems right so far. how are you accessing the files in your source code?

burbma18:05:41

I’m passing the string “resources/migrations” to ragtime.jdbc/load-resources which then calls resauce/resource-dir which is supposed to “return a list of resource URLs on the classpath that have the supplied path prefix.”

mobileink19:05:15

should my boot deps always pick up snapshots from the local repo? i'm modifying my snapshot, but me test app seems to always use the snapshot from clojars. is there some trick to this? something i've inadvertently added to cause this?

qqq21:05:25

@dave: did you guys write a blog post about moving away from beanstalk?

qqq21:05:43

I am considering moving FROM gae TO beanstalk and would love to read about your experiences with clojure

dave21:05:24

no, but that's a really good idea -- we should do that

dave21:05:39

we ended up writing our own automated deployment system

dave21:05:51

i think we intend to open-source it at some point

qqq21:05:50

@dave: what were the primary issues with clojure + boot-beanstalk ?

dave21:05:04

for us, it was slowness and randomly failing deploys that were very difficult to debug

dave21:05:27

the AWS elastic beanstalk UI is not great

dave21:05:41

just pulling logs to figure out why a deploy failed is a frustrating ordeal

dave21:05:05

granted, this was our experience as of probably a year or two ago now

dave21:05:11

things might be substantially better at this point

dave21:05:31

what we're doing now is basically scripting around using the aws cli tool to manage all of an application's resources

dave21:05:43

packaged into an easy to use tool called ah

dave21:05:00

actually, talking to micha here in the office, we have actually open-sourced ah: https://github.com/adzerk/ah

dave21:05:24

the documentation is probably not great, but maybe it's worth exploring

dave21:05:10

we've been using it in production for a long time now and we're big fans of it