Depending on the operating system, calls to Dir#[] and Dir.glob will return the order of the directory in different order for the same directory.
So given the following directory structure:
app
└── admin
├── a.rb
├── concerns
│ ├── hd.rb
│ └── hu.rb
├── d.rb
├── f.rb
├── g.rb
└── v.rb
The order of the following command:
# Note, this current example is taken from the `activeadmin` project
#
# https://github.com/NickLaMuro/activeadmin/blob/4101263/lib/active_admin/application.rb#L219-L221
#
puts %w[app/admin].flatten.compact.uniq.flat_map {|path| Dir[\"#{path}/**/*.rb\"] }Will be different for each OS, regardless of the ruby version.
The Vagrantfile and vagrant_test.sh files are examples of how this inconsistency can be shown in practice. Simply put both of these files in the same directory, make the vagrant_test.sh file executable, and run:
$ ./vagrant_test.sh
This basically run the following three commands for each vm defined in the Vagrantfile:
$ vagrant up [VM_NAME]
$ vagrant ssh -c /opt/rubies/[RUBY_VERSION]/bin/ruby -e 'puts %w[/home/vagrant/app/admin].flatten.compact.uniq.flat_map {|path| Dir[\"#{path}/**/*.rb\"] }'
$ vagrant halt [VM_NAME]
Replacing [VM_NAME] and [RUBY_VERSION] with those specific for the vm being run against. The script just modifies the output so the differences are easier to be noticed.
To test a possible fix for this script, you can run ./vagrant_test.sh corrected to use a slightly modified version of the ruby script that then sorts the files properly in ruby across all OS's.
The above script is meant for unix based systems (OSX and Linux), so to run this on Windows, you will have to use the seperated ssh commands provided above with an ssh client installed. I would recommend cmder as a possible console emulator that has a great ssh client built in.