[Development/GettingStarted] Docker compose workflow #738
Conversation
| @@ -0,0 +1,36 @@ | |||
| FROM crystallang/crystal:1.1.1 | |||
There was a problem hiding this comment.
This needs to be updated, but later versions of the crystal dockerfile don't play well with my computer yet. If someone is willing to test this on an AMD64 architecture with this line updated to 1.3.2, I'll be happy to update it.
| # | ||
| # Use this script to test if a given TCP host/port are available | ||
|
|
||
| WAITFORIT_cmdname=${0##*/} |
| RUN wget https://github.com/DarthSim/overmind/releases/download/v2.2.2/overmind-v2.2.2-linux-amd64.gz && \ | ||
| gunzip overmind-v2.2.2-linux-amd64.gz && \ | ||
| mv overmind-v2.2.2-linux-amd64 /usr/bin/overmind && \ | ||
| chmod +x /usr/bin/overmind |
There was a problem hiding this comment.
Should we be using Nox for this? It comes with Lucky CLI which gets installed in the next run.
There was a problem hiding this comment.
Yep. This provides overmind in the system, but if lucky-cli doesn't need it, it won't hurt anything. I needed this because I developed it against lucky-cli release rather than main.
There was a problem hiding this comment.
Ah. I forgot Nox integration hasn't been released yet. Yeah, the next release won't need a process runner!
There was a problem hiding this comment.
Since this will ship with Nox, when the cli is revised, I'm happy to pull it now or leave it in. I don't think it hurts and it might help someone get a compose going for an app that doesn't yet have the newest version of lucky on their system.
when the container crashes, this file doesn't get cleaned up and it won't boot again
This is a series of contributions aimed at making getting started writing a Lucky app easier.
This allows an app generated with lucky_cli to play well in a
docker composebased development environment. There are some benefits and drawbacks to this, but primarily it means that crystal, libssl, postgres, and other libraries/tools don't need to be installed in order to get started.This does not provide a Dockerfile for production use, which would be very different from a development environment. After this is merged, I or someone else can tackle that, perhaps with a lot of inspiration from Lucky Jumpstart or my own lucky template.
In order to get started with this, a generated app need only run
docker compose upordocker-compose up. It will download images, create the database, install npm modules, install shard dependencies, and even migrate the database (just on the first boot).