Open stevenhaddox opened 11 years ago
+1 to myself. Each deployed instance will have different known rubies available and hard coding this requires conflicting with the git repo currently when you go to upgrade.
+1
I've managed to implement making the listing of Rubies on the RVM::FW instance dynamic as well as calculating the MD5 sums on the fly before rendering the /rubies
view. This tackles a portion of this that has been irritating me forever where configs weren't matching rubies actually on the filesystem.
Now I just need to write a script / task that will generate the db
and known
files dynamically based upon the configuration file's latest rubies... #someday
The rendering of /db and /known should all happen dynamically based upon the configuration.