configuration-files

in HOME/path_test/ I have: load_test.rb: require 'yaml' cnf = YAML::load(File.open('config.yml')) puts cnf['Hello'] config.yml: Hello: world!!! when in HOME/path_test/ I get as expected: -bash-3.2$ ruby load_test.rb world!!! when in HOME/ (cd ..) I get -bash-3.2$ ruby path_test/load_test.rb path_test/load_test.rb:3:in `initialize': No such file or directory - config.yml (Errno::ENOENT) from path_test/load_test.rb:3:in `open' from path_test/load_test.rb:3:in `<main>' Which is correct behavior, but not what I had wished for :) Is there a way to load the .yml file relative to the source file, and

I'm getting back into Spring (currently v4). It's all wonderful now with @SpringBootApplication and the other annotations but all the documentation seems to forget to mention how I define other beans in XML! For example I'd like to create an "SFTP Session Factory" as defined at: http://docs.spring.io/spring-integration/reference/html/sftp.html There is a nice bit of XML to define the bean but where on earth do I put it and how do I link it in? Previously I did a: ApplicationContext context = new ClassPathXmlApplicationContext( "classpath:applicationContext.xml"); to specify the file name and

for configuration as following <MyCollection default="one"> <entry name="one" ... other attrubutes /> ... other entries </MyCollection> when implement a MyCollection, what should i do for the "default" attribute? Let's suppose you have this .config file: <configuration> <configSections> <section name="mySection" type="ConsoleApplication1.MySection, ConsoleApplication1" /> // update type & assembly names accordingly </configSections> <mySection> <MyCollection default="one"> <entry name="one" /> <entry name="two" /> </MyCollection> </mySection> </configuration> Then, with this code: public class

I have a Python application which needs quite a few (~30) configuration parameters. Up to now, I used the OptionParser class to define default values in the app itself, with the possibility to change individual parameters at the command line when invoking the application. Now I would like to use 'proper' configuration files, for example from the ConfigParser class. At the same time, users should still be able to change individual parameters at the command line. I was wondering if there is any way to combine the two steps, e.g. use optparse (or the newer argparse) to handle command line options

Is there a command in the vim editor to find the .vimrc file location? manojlds Just try doing the following: :version You will get an output which includes something like: system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" user exrc file: "$HOME/.exrc" system gvimrc file: "$VIM/gvimrc" user gvimrc file: "$HOME/.gvimrc" system menu file: "$VIMRUNTIME/menu.vim" As noted by Herbert in comments, this is where vim looks for vimrc s, it doesn't mean they exist. You can check the full path of your vimrc with :echo $MYVIMRC If the output is empty, then your vim doesn't use a user vimrc

How do I set global configuration for RSpec in Ubuntu. Specifically so, --color and --format specdoc stay turned on, across all my projects (ie every time I run rspec anywhere). abyx As you can see in the docs here , the intended use is creating ~/.rspec and in it putting your options, such as --color . To quickly create an ~/.rspec file with the --color option, just run: echo '--color' >> ~/.rspec One can also use a spec_helper.rb file in all projects. The file should include the following: RSpec.configure do |config| # Use color in STDOUT config.color = true # Use color not only in STDOUT

I faced with problem in configuring nginx server for yii2 basic app. Here is my service block file : server { listen 80 ; access_log /var/log/nginx/access-server.log; error_log /var/log/nginx/error-server.log; charset utf-8; location /fetch { root /usr/share/nginx/html/another_folder/web/; try_files $uri $uri/ /index.php$is_args$args; } location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; fastcgi_pass 127.0.0.1:9000; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; include fastcgi_params; } } My project located in another folder "another