leandro
2016-10-2 13:07:11

Hello again!


leandro
2016-10-2 13:09:17

I managed to get the image up and running in alpine:3.4 thanks to this: https://github.com/m4burns/racket-docker/blob/master/Dockerfile

And after dealing with compiled documentation problems on #irc, I’ve been able to build an executable, but it seems I can’t run the code with racket -t main.rkt

explode-path: contract violation
  expected: (or/c path-for-some-system? path-string?)
  given: #f

can’t seem to get why it’s failling?


leandro
2016-10-2 13:12:48

it seems to also be failing for every other file – maybe something fucked up during the installation of racket itself


lexi.lambda
2016-10-2 17:12:44

@leandro: I am not sure I would agree with @notjack that Docker is an easy way to deploy anything if you are not already familiar with Docker


leandro
2016-10-2 17:13:19

What I lack familiarity with is Racket :stuck_out_tongue:


lexi.lambda
2016-10-2 17:13:49

I think the best way to deploy Racket probably depends on where you’re looking to deploy it to


lexi.lambda
2016-10-2 17:17:08

I maintain a Heroku buildpack for Racket applications, which is probably pretty straightforward to use if you want to use Heroku, for example


lexi.lambda
2016-10-2 17:17:33

if you want to deploy to a server you manage, though, then there are probably a couple of options depending on your needs


leandro
2016-10-2 17:32:53

absolutely


leandro
2016-10-2 17:33:35

I like to develop in as close to the same environment things will run when in production


leandro
2016-10-2 17:33:50

so docker was the natural way to go for me at first


leandro
2016-10-2 17:34:15

that way I can take that container anywhere and drop it like it’s hot


lexi.lambda
2016-10-2 17:34:50

ok, if you are already comfortable with docker then docker is not an unreasonable choice


lexi.lambda
2016-10-2 17:35:27

I’m not sure how supported the alpine-based racket docker images are, though