I use Gitlab CI at work for source and all the pipeline work, it’s a really good solution. I feel you having it and github adds unwelcome overhead. Knowing what I know now about gcp app engine and where this project ended up, I too would have gone with Gigalixir to help remove a lot of the complexity around create, scale, and destroy. I just came realize I have to manually destroy old instances of app engine, maybe?
jtomchak
jtomchak
I would absolutely take another look at Elm. It’s giving me wider exposure to static types, type theory, functional programming, and really the got me to branch out from a full stack in JavaScript. It’s a great community that I really enjoy. 
0
jtomchak
Making life a little easier with ecto migrations on prod release with distillery. 
release :postit do
set version: current_version(:postit)
set applications: [
:runtime_tools
]
set commands: [
"migrate": "rel/commands/migrate.sh"
]
end
1
jean
jtomchak
We started out with plans to add some routes and additional models, but fell down the rabbit hole trying to answer this question: How do i reuse a function in multiple controllers? In this specific instance, we’ll want to secure multiple routes, but don’t want to copy / paste the secure function we have to every controller, that will get out of hand fast!
2
jtomchak
Turns out, this works as advertised. Doesn’t need the ‘handlers’ on the app.yaml config for App Engine on GCP.
0
jtomchak
Finally migrations in prod working. 
A 2019-07-28T23:28:17Z Running migrations for postit
A 2019-07-28T23:28:17Z 2019/07/28 23:28:17 New connection for "post-it-243617:us-central1:postitdb-beta"
A 2019-07-28T23:28:17Z 2019/07/28 23:28:17 New connection for "post-it-243617:us-central1:postitdb-beta"
A 2019-07-28T23:28:18Z 23:28:18.294 [info] == Running 20190717045929 Postit.Repo.Migrations.CreatePosts.change/0 forward
A 2019-07-28T23:28:18Z 23:28:18.298 [info] create table posts
A 2019-07-28T23:28:18Z 23:28:18.371 [info] == Migrated 20190717045929 in 0.0s
2
jtomchak
We’ve moved on from the default Phoenix page. It served us well, the project is starting to take on some real personality. We’re just getting into the good stuff!!
2
jtomchak
Tackle a little bit of devs ops to start, getting Ecto migrations working on ‘post_boot’ hook on release from Distillery. With that in place we can start to dig into the domain of our application and start making some meaningful changes. Also, checkout the new styling!!!1 
2
jtomchak
However, in most contexts that expect a boolean expression, Elixir is more lax. The values
nilandfalseare considered falsy; all other values are truthy.
Now I’m starting to feel at home. 
1