glob
glob(p1, p2 = v2)Expands pattern, which is an Array of patterns or a pattern String, and returns the results as matches or as arguments given to the block.
Note that this pattern is not a regexp, it’s closer to a shell glob. See File::fnmatch for the meaning of the flags parameter. Note that case sensitivity depends on your system (so File::FNM_CASEFOLD is ignored), as does the order in which the results are returned.
* |
Matches any file. Can be restricted by other values in the glob. Equivalent to / .* /x in regexp.
Note, this will not match Unix-like hidden files (dotfiles). In order to include those in the match results, you must use the File::FNM_DOTMATCH flag or something like “{*,.*}”. | ||||||||
** |
Matches directories recursively. | ||||||||
? |
Matches any one character. Equivalent to /.{1}/ in regexp. | ||||||||
[set] |
Matches any one character in set. Behaves exactly like character sets in Regexp, including set negation ([^a-z]). | ||||||||
{p,q} |
Matches either literal p or literal q. Equivalent to pattern alternation in regexp. Matching literals may be more than one character in length. More than two literals may be specified. | ||||||||
\ |
Escapes the next metacharacter. Note that this means you cannot use backslash on windows as part of a glob, i.e. Dir[“c:\foo*”] will not work, use Dir[“c:/foo*”] instead. |
Examples:
Dir["config.?"] #=> ["config.h"] Dir.glob("config.?") #=> ["config.h"] Dir.glob("*.[a-z][a-z]") #=> ["main.rb"] Dir.glob("*.[^r]*") #=> ["config.h"] Dir.glob("*.{rb,h}") #=> ["main.rb", "config.h"] Dir.glob("*") #=> ["config.h", "main.rb"] Dir.glob("*", File::FNM_DOTMATCH) #=> [".", "..", "config.h", "main.rb"] rbfiles = File.join("**", "*.rb") Dir.glob(rbfiles) #=> ["main.rb", # "lib/song.rb", # "lib/song/karaoke.rb"] libdirs = File.join("**", "lib") Dir.glob(libdirs) #=> ["lib"] librbfiles = File.join("**", "lib", "**", "*.rb") Dir.glob(librbfiles) #=> ["lib/song.rb", # "lib/song/karaoke.rb"] librbfiles = File.join("**", "lib", "*.rb") Dir.glob(librbfiles) #=> ["lib/song.rb"]
4Notes
Getting relative path from absolute globbing
Say you want to scan for files in directory +base_dir+ and you want to use the relative path from this base dir, you could do it like this:
base_dir = '/path/to/dir'
files = Dir[File.join(base_dir, '**', '*.yml')]
# files now contain absolute paths:
files.first # => "/path/to/dir/foo/bar.yml"
# let's make them relative
base_pathname = Pathname.new(base_dir)
files = files.collect do |file|
Pathname.new(file).relative_path_from(base_pathname)
end
files.first # => "foo/bar.yml"
Of course, a more common use-case could be the following:
def scan_for_documents!
base_path = Pathname.new(self.base_path)
self.contained_files = []
Dir[File.join(self.base_path, '**', '*.pdf')].each do |full_path|
path = Pathname.new(full_path).relative_path_from(base_path)
self.contained_files << path
end
end
Alternative way to show relative paths from absolute globbing
An alternative to show relative paths is using the well known String#sub! method
base_dir = File.expand_path("my_dir") << "/" # don't miss adding "/"
files = Dir[File.join(base_dir, '**', '*.html.gz')]
p files.map {|f| f.sub!(base_dir,"")}
And yet another way to get relative path from absolute globbing
If you execute glob within a block passed to Dir.chdir, you get the paths relative to the directory specified by Dir.chdir... like this... base_dir = '/path/to/dir' files = Dir.chdir(base_dir) do Dir.glob("**/*.yml") end files.first # => 'foo/bar.yml'
Faker Gem: Fake Data Generation in Ruby
Gems are libraries in Rails that generally enable you to write the application code faster and thereby making a great product in far lesser time. Usually, whenever we start developing any application, there comes a point when we need data which we can use to see how the application will behave while doing some load testing or how it would look when we deploy it to the production. The manual process of creating the data can be daunting. Faker gem serves to take this pain away by generating the fake data just as needed and saving us all the time and effort otherwise wasted in the manual process of data-generation.
It can generate almost any kind of data suitable for our application. For example, it can generate the fake data for fields such as name, email, passwords, phone-numbers, paragraphs, etc. It is therefore, an awesome way of populating the model (which is a database layer in Rails)
Let’s take a look at this gem by creating a sample project. Read More: http://www.railscarma.com/blog/technical-articles/faker-gem-fake-data-generation-ruby/