Skip to content

Conversation

@ibnesayeed
Copy link
Contributor

This will enable building Docker images locally or setting up an automatic build on DockerHub. The documentation assumes that an automatic build is setup at jekyll/classifier-reborn as discussed in #101.

@Ch4s3 Ch4s3 merged commit 0744b6e into jekyll:master Jan 8, 2017
@ibnesayeed ibnesayeed deleted the docker branch January 8, 2017 17:28
mkasberg added a commit to mkasberg/classifier-reborn that referenced this pull request Oct 2, 2022
While working on Ruby 3 support several months ago, I noticed the
[Dockerfile](https://github.com/jekyll/classifier-reborn/blob/c3e5a84c3e0915d20ab52f2b783703575584d4a2/Dockerfile)
was really stale. I didn't immediately fix this at the time, but made a
mental note to come back to it sometime.

This Dockerfile is intended to be used for development. It was added in
jekyll#104 (discussed in
detail at jekyll#101). The
documentation for using this is still available (and accurate) at
https://jekyll.github.io/classifier-reborn/development#development-using-docker.

classifier-reborn currently supports ruby 2.7, 3.0, and 3.1 (as you can
see in `ci.yml`). Since we can only (easily) put one ruby version in the
Dockerfile, using the most recent version made sense to me. Doing so
means we have to use Numo instead of GSL since GSL isn't currently
supported on Ruby 3.x.
mkasberg added a commit to mkasberg/classifier-reborn that referenced this pull request Oct 2, 2022
While working on Ruby 3 support several months ago, I noticed the
[Dockerfile](https://github.com/jekyll/classifier-reborn/blob/c3e5a84c3e0915d20ab52f2b783703575584d4a2/Dockerfile)
was really stale. I didn't immediately fix this at the time, but made a
mental note to come back to it sometime.

This Dockerfile is intended to be used for development. It was added in
jekyll#104 (discussed in
detail at jekyll#101). The
documentation for using this is still available (and accurate) at
https://jekyll.github.io/classifier-reborn/development#development-using-docker.

classifier-reborn currently supports ruby 2.7, 3.0, and 3.1 (as you can
see in `ci.yml`). Since we can only (easily) put one ruby version in the
Dockerfile, using the most recent version made sense to me. Doing so
means we have to use Numo instead of GSL since GSL isn't currently
supported on Ruby 3.x.
mkasberg added a commit to mkasberg/classifier-reborn that referenced this pull request Oct 2, 2022
While working on Ruby 3 support several months ago, I noticed the
[Dockerfile](https://github.com/jekyll/classifier-reborn/blob/c3e5a84c3e0915d20ab52f2b783703575584d4a2/Dockerfile)
was really stale. I didn't immediately fix this at the time, but made a
mental note to come back to it sometime.

This Dockerfile is intended to be used for development. It was added in
jekyll#104 (discussed in
detail at jekyll#101). The
documentation for using this is still available (and accurate) at
https://jekyll.github.io/classifier-reborn/development#development-using-docker.

classifier-reborn currently supports ruby 2.7, 3.0, and 3.1 (as you can
see in `ci.yml`). Since we can only (easily) put one ruby version in the
Dockerfile, using the most recent version made sense to me. Doing so
means we have to use Numo instead of GSL since GSL isn't currently
supported on Ruby 3.x.

The `MAINTAINER` dockerfile instruction is deprecated, so I removed it.
(It isn't necessary anyway on a Dockerfile that doesn't publish a
build.)
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

Successfully merging this pull request may close these issues.

2 participants