Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding Racket to Netlify Build Image #41

Open
smizell opened this issue Mar 28, 2020 · 2 comments
Open

Adding Racket to Netlify Build Image #41

smizell opened this issue Mar 28, 2020 · 2 comments

Comments

@smizell
Copy link

smizell commented Mar 28, 2020

This isn't an issue, just informational :)

I've been playing with Pollen lately and wanted to automate deployments to Netlify. Unfortunately, Netlify doesn't support Racket out of the box. I borrowed some of the Dockerfile from here to open a PR to see if they'll add it.

netlify/build-image#381

Thanks for putting this Docker stuff together! I appreciate it.

@jackfirth
Copy link
Collaborator

Oh cool! I hadn't heard of Netlify, I'm glad you were able to get Racket working for it. And thanks for the appreciation 🙂.

Skimming the Netlify docs, do they maintain a single shared Docker image with every common frontend toolchain installed? That's interesting, I would have expected them to let you specify an arbitrary custom image that you want to build your site with.

@smizell
Copy link
Author

smizell commented Apr 2, 2020

Yeah, they have a single image here. It installs Ruby, Python, Node, and a few others along with Hugo as a static site tool. They then have a build script they run that will do various things out of the box on build. It will look for Gemfiles for Ruby or Python files and install all dependencies.

This lets you drop your static site tool into dependencies and give them a run command. They'll install dependencies on build and run your command afterwards.

No telling how big the image is though!

I would have expected them to let you specify an arbitrary custom image that you want to build your site with.

Agreed. I'd be curious why. Maybe they feel that CI/CD services can already do that, and you can use the Netlify command to push up the build afterwards. I've actually been tinkering with this myself since they don't have Racket support. I'm not a Docker expert so it's definitely a journey. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants