Dockerfile current? still references ruby 2.6

[misilot]

Hello,

We are looking to test out heliotrope / fulcrum and I noticed that the Dockerfile is referencing Ruby 2.6, but other code has been updated to Ruby 3.3.5, and I just wanted to check in to see if it should work in it's current state, or if we should just stand up a new system and not try and run this in a container.

Thanks!

[misilot]

Kind of answered by #3822

[sethaj]

Hi @misilot yes you are correct that the Dockerfile is out of date. As you know, I've put in a PR for an update, but there are problems with it and I don't have a time table for when it will be fixed. I am personally invested in containerizing this application, but it's something I do in my free time, it's not on the Fulcrum product roadmap right now so it could take some time to get everything working.

If you're committed to trying things out, probably the best way to do that is to follow the "local development" instructions in the readme, not using any containerization, which I know is not ideal but will hopefully work.

I think too I should say that over the years the heliotrope/fulcrum code base has become more and more entrenched with University of Michigan infrastructure to the point where I can't really recommend using it in other contexts. If you still want to try I think that's great, but you'll probably want to fork the project because I think a lot of changes would be needed and we can't really offer much in the way of support. I plan on updating the readme to reflect that reality better.

If you're just evaluating different repository software, I can recommend trying out Samvera's Hyrax (or Hyku too). Fulcrum is built on (or kind of adjacent to) Hyrax so there's a lot of commonality. Fulcrum uses Hyrax 4, but Hyrax 5 is the current version and I think their Docker instructions are much more likely to be actually working.

I'll leave this issue open, eventually I'd love to see a containerized Fulcrum so I do plan on addressing it, but as I said I can't offer any concrete progress since it's something I work on "in the margins". I'll bring it up at our next Sprint Planning meeting, but we've got a full roadmap so I'm not sure what kind of priority will be assigned to this, if any.

[misilot]

Thanks @sethaj I will try the local development instructions. I ran into issues trying to figure out the first part of getting Hyrax prerequisites, since this is really the first major ruby app I have ever tried to get working, so it's been a learning curve with that and was optimistic for the Docker version to test this out!

[misilot]

I just want to say we are looking to evaluate Fulcrum specifically, and not Hyrax directly. It was the feature sets that are there, as we considering our options for what we currently are running. I look forward to trying to get this going to test.