Fork me on GitHub
#babashka
<
2021-07-18
>
Cora (she/her)04:07:55

huh, so the babashka timbre doesn't support merge-config?

borkdude07:07:42

swap-config is there. I’ll add merge config for next release

bubblebobble 3
borkdude09:07:00

Added on master

rafaeldelboni14:07:32

Is there an official babashka setup github action? I found some in the internet, just curious if there is a recommended one

borkdude14:07:16

That's probably the most active one

Cora (she/her)17:07:47

I feel like babashka might be a good place to have a sql migrations library

borkdude17:07:58

One of the problems with this is that you should then have a sql driver for each popular lib inside bb?

Cora (she/her)17:07:39

I'd think we could get away with this with pods, maybe?

Cora (she/her)17:07:58

oooooh I was thinking of this specifically for migratus

borkdude17:07:00

Yes, in that case the migration lib could probably be written just using source code, not as a built-in one

Cora (she/her)17:07:03

so ummm, guess that solves that

Cora (she/her)17:07:59

oh, I didn't mean a built-in-to-babashka lib, just as a pod or something

borkdude17:07:41

not a bad idea

borkdude17:07:56

but yeah if you're using postgres, then pgmig already solves your problem

borkdude17:07:59

you could also modify migratus a bit so it can run using bb pods

Cora (she/her)18:07:41

or make pgmin a pod? although I'd like to use it with sqlite in babashka mostly

borkdude18:07:40

yes, pgmig could be a pod, but it's specific to postgres (hence pg). it's probably best to roll your own or fork migratus

Cora (she/her)18:07:49

it hat sounds right to me :)