Notice to git users regarding the upcoming 0.5 / rails 3 migration

Support
#1

Hi,

As some of you know, we've been working of upgrading our ruby on rails
framework (which foreman is built on) to a more updated version,
mainly due to security concerns and the ability to integrate foreman
into existing distributions.

If you are not a git user (e.g. you have installed foreman from a
package rpm/deb), feel free to skip the mail, as we'll try to ensure a
smooth upgrade.

I'll merge the rails3 modifications into the develop branch shortly,
this would mean a few things:

  1. I've created a 0.4-stable branch, this would be a maintenance
    branch and only critical bug fixes would be applied, probably 0.4.1
    release would come up in a couple of weeks or so, if you are running
    git for your stable environment, please switch to this branch for the
    time being.
  2. The develop branch require ruby 1.87+.
  3. No more git sub modules, we have been migrating to use bundler*[1].
    this probably mean that's its best to checkout foreman to a new
    directory, and migrate the config files
    (config/{database.yml,foreman.yaml}).
  4. I'll remove the settings.yml file from the repo, the original file
    is misleading (with its values) and overriding for everyone is going
    to create problems, please simply copy the sample file
    (config/settings.yaml.example and update accordingly).
  5. there are no packages yet, bundler [1] introduces a bit of a
    challenge, and would most likely we would require additional cycles,
    if anyone got some spares, please let us know!

Since this is a major change, please open new issues on anything you
find out of the ordinary.
Thanks for your support,

Ohad

[1] - http://gembundler.com/

#2

What challenges are introduced with bundler in regards to packages?
Does "packages" refer to things like RPMs or something specific to
bundler?

Thanks

  • Trey
ยทยทยท On Nov 28, 2:33 am, Ohad Levy wrote: > Hi, > > As some of you know, we've been working of upgrading our ruby on rails > framework (which foreman is built on) to a more updated version, > mainly due to security concerns and the ability to integrate foreman > into existing distributions. > > If you are not a git user (e.g. you have installed foreman from a > package rpm/deb), feel free to skip the mail, as we'll try to ensure a > smooth upgrade. > > I'll merge the rails3 modifications into the develop branch shortly, > this would mean a few things: > > 1. I've created a 0.4-stable branch, this would be a maintenance > branch and only critical bug fixes would be applied, probably 0.4.1 > release would come up in a couple of weeks or so, if you are running > git for your stable environment, please switch to this branch for the > time being. > 2. The develop branch require ruby 1.87+. > 3. No more git sub modules, we have been migrating to use bundler*[1]. > this probably mean that's its best to checkout foreman to a new > directory, and migrate the config files > (config/{database.yml,foreman.yaml}). > 4. I'll remove the settings.yml file from the repo, the original file > is misleading (with its values) and overriding for everyone is going > to create problems, please simply copy the sample file > (config/settings.yaml.example and update accordingly). > 5. there are no packages yet, bundler [1] introduces a bit of a > challenge, and would most likely we would require additional cycles, > if anyone got some spares, please let us know! > > Since this is a major change, please open new issues on anything you > find out of the ordinary. > Thanks for your support, > > Ohad > > [1] -http://gembundler.com/