Hi everyone, quick question here!
We are trying to install Open Ondemand v4 in a Debian 12 machine. As we saw in the official guide OOD4 supports Debian 12 but I have a couple of questions.
The first one is related with dependences on Ruby and NodeJS, as far as I know OOD4 needs Ruby3.3 and NodeJS 20, but searching for instruccions for Debian 12 we don’t see any of this. Also regarding debian 12 repos only give us Ruby3.1 and NodeJS 18. We made the installation using this basic ones for testing.
Now the problems seems to be this, when we try to loggin in the portal we face this error:
I’m searching in the /opt/ood/ondemand/ folder (where in other installations we have a /root folder, and in this machine we only have this :
So I’m wondering if we are missing something, or if we have any special conditions as we are dealing with Debian12.
Thank you in advice as always!
Christian.
I just tried to replicate in a Debian 12 container and couldn’t.
Different operating systems require different packages, but for me I got Ruby 3.1 and node 20 on Debian 12. Which is to say, we just need whatever gets installed at least on this OS.
I’m not sure what could have happened, do you have automation that would remove that directory or similar?
Hi @jeff.ohrstrom, a little update here!
You are right seems to be working fine with Ruby3.1 in Debian12, we guide ourself by experience and documentation hahaha, is interesting to know that Debian12 doesn’t need the ruby 3.3.
In other hand we had found a weird error related with our installation, for this one (as always) I’m using an Ansible-playbook to automatize the deploy. We found that when we try to install ondemand and ondemand-dex packages via the ansible the nginx executable was not installed:
but if we do it manually "apt install ondemand ondemand-dex”, then we don’t have this problem.
Is a bit weird because we if we try to replicate that in other of our local VM we are not able to do it 
.
My guess here is something related with how the file system is managed and how the ansible-playbook try to generate this files.
The final solution was to execute the installation manually and using the version of Ruby and NodeJS that are available in the repositories of Debian12.
I guess I’d have to see what’s in the role/playbook to see more. /opt may be read only but it seems like the package install would fail in that case…
