Configuring Rails Applications
This guide covers the configuration and initialization features available to Rails applications.
After reading this guide, you will know:
- How to adjust the behavior of your Rails applications.
- How to add additional code to be run at application start time.
Locations for Initialization Code
Rails offers four standard spots to place initialization code:
config/application.rb
- Environment-specific configuration files
- Initializers
- After-initializers
Running Code Before Rails
In the rare event that your application needs to run some code before Rails itself is loaded, put it above the call to require 'rails/all'
in config/application.rb
.
Configuring Rails Components
In general, the work of configuring Rails means configuring the components of Rails, as well as configuring Rails itself. The configuration file config/application.rb
and environment-specific configuration files (such as config/environments/production.rb
) allow you to specify the various settings that you want to pass down to all of the components.
For example, the config/application.rb
file includes this setting:
config.time_zone = 'Central Time (US & Canada)'
This is a setting for Rails itself. If you want to pass settings to individual Rails components, you can do so via the same config
object in config/application.rb
:
config.active_record.schema_format = :ruby
Rails will use that particular setting to configure Active Record.
Rails General Configuration
These configuration methods are to be called on a ::Rails::Railtie object, such as a subclass of ::Rails::Engine or ::Rails::Application.
-
config.after_initialize
takes a block which will be run after Rails has finished initializing the application. That includes the initialization of the framework itself, engines, and all the application's initializers inconfig/initializers
. Note that this block will be run for rake tasks. Useful for configuring values set up by other initializers:config.after_initialize do ActionView::Base. .delete 'div' end
-
config.asset_host
sets the host for the assets. Useful when CDNs are used for hosting assets, or when you want to work around the concurrency constraints built-in in browsers using different domain aliases. Shorter version ofconfig.action_controller.asset_host
. -
config.autoload_once_paths
accepts an array of paths from which Rails will autoload constants that won't be wiped per request. Relevant ifconfig.cache_classes
is false, which is the case in development mode by default. Otherwise, all autoloading happens only once. All elements of this array must also be inautoload_paths
. Default is an empty array. -
config.autoload_paths
accepts an array of paths from which Rails will autoload constants. Default is all directories underapp
. -
config.cache_classes
controls whether or not application classes and modules should be reloaded on each request. Defaults to false in development mode, and true in test and production modes. -
config.action_view.cache_template_loading
controls whether or not templates should be reloaded on each request. Defaults to whatever is set forconfig.cache_classes
. -
config.beginning_of_week
sets the default beginning of week for the application. Accepts a valid week day symbol (e.g.:monday
). -
config.cache_store
configures which cache store to use for Rails caching. Options include one of the symbols:memory_store
,:file_store
,:mem_cache_store
,:null_store
, or an object that implements the cache API. Defaults to:file_store
if the directorytmp/cache
exists, and to:memory_store
otherwise. -
config.colorize_logging
specifies whether or not to use ANSI color codes when logging information. Defaults to true. -
config.consider_all_requests_local
is a flag. If true then any error will cause detailed debugging information to be dumped in the HTTP response, and the ::Rails::Info controller will show the application runtime context in/rails/info/properties
. True by default in development and test environments, and false in production mode. For finer-grained control, set this to false and implementlocal_request?
in controllers to specify which requests should provide debugging information on errors. -
config.console
allows you to set class that will be used as console you runrails console
. It's best to run it inconsole
block:console do # this block is called only when running console, # so we can safely require pry here require "pry" config.console = Pry end
-
config.dependency_loading
is a flag that allows you to disable constant autoloading setting it to false. It only has effect ifconfig.cache_classes
is true, which it is by default in production mode. -
config.eager_load
when true, eager loads all registeredconfig.eager_load_namespaces
. This includes your application, engines, Rails frameworks and any other registered namespace. -
config.eager_load_namespaces
registers namespaces that are eager loaded whenconfig.eager_load
is true. All namespaces in the list must respond to theeager_load!
method. -
config.eager_load_paths
accepts an array of paths from which Rails will eager load on boot if cache classes is enabled. Defaults to every folder in theapp
directory of the application. -
config.encoding
sets up the application-wide encoding. Defaults to UTF-8. -
config.exceptions_app
sets the exceptions application invoked by the ShowException middleware when an exception happens. Defaults toActionDispatch::PublicExceptions.new(Rails.public_path)
. -
config.file_watcher
the class used to detect file updates in the filesystem whenconfig.reload_classes_only_on_change
is true. Must conform to ::ActiveSupport::FileUpdateChecker API. -
config.filter_parameters
used for filtering out the parameters that you don't want shown in the logs, such as passwords or credit card numbers. New applications filter out passwords by adding the followingconfig.filter_parameters+=[:password]
inconfig/initializers/filter_parameter_logging.rb
. -
config.force_ssl
forces all requests to be under HTTPS protocol by using ::ActionDispatch::SSL middleware. -
config.log_formatter
defines the formatter of the Rails logger. This option defaults to an instance of ::ActiveSupport::Logger::SimpleFormatter for all modes except production, where it defaults toLogger::Formatter
. -
config.log_level
defines the verbosity of the Rails logger. This option defaults to:debug
for all environments. -
config.log_tags
accepts a list of methods that therequest
object responds to. This makes it easy to tag log lines with debug information like subdomain and request id - both very helpful in debugging multi-user production applications. -
config.logger
accepts a logger conforming to the interface of Log4r or the default RubyLogger
class. Defaults to an instance of ::ActiveSupport::Logger. -
config.middleware
allows you to configure the application's middleware. This is covered in depth in the Configuring Middleware section below. -
config.reload_classes_only_on_change
enables or disables reloading of classes only when tracked files change. By default tracks everything on autoload paths and is set to true. Ifconfig.cache_classes
is true, this option is ignored. -
secrets.secret_key_base
is used for specifying a key which allows sessions for the application to be verified against a known secure key to prevent tampering. Applications getsecrets.secret_key_base
initialized to a random key present inconfig/secrets.yml
. -
config.serve_static_files
configures Rails itself to serve static files. Defaults to true, but in the production environment is turned off as the server software (e.g. NGINX or Apache) used to run the application should serve static assets instead. Unlike the default setting set this to true when running (absolutely not recommended!) or testing your app in production mode using WEBrick. Otherwise you won't be able use page caching and requests for files that exist regularly under the public directory will anyway hit your Rails app. -
config.session_store
is usually set up inconfig/initializers/session_store.rb
and specifies what class to use to store the session. Possible values are:cookie_store
which is the default,:mem_cache_store
, and:disabled
. The last one tells Rails not to deal with sessions. Custom session stores can also be specified:config.session_store :my_custom_store
This custom store must be defined as
ActionDispatch::Session::MyCustomStore
. -
config.time_zone
sets the default time zone for the application and enables time zone awareness for Active Record.
Configuring Assets
-
config.assets.enabled
a flag that controls whether the asset pipeline is enabled. It is set to true by default. -
config.assets.raise_runtime_errors
Set this flag totrue
to enable additional runtime error checking. Recommended inconfig/environments/development.rb
to minimize unexpected behavior when deploying toproduction
. -
config.assets.css_compressor
defines the CSS compressor to use. It is set by default bysass-rails
. The unique alternative value at the moment is:yui
, which uses theyui-compressor
gem. -
config.assets.js_compressor
defines the JavaScript compressor to use. Possible values are:closure
,:uglifier
and:yui
which require the use of theclosure-compiler
,uglifier
oryui-compressor
gems respectively. -
config.assets.paths
contains the paths which are used to look for assets. Appending paths to this configuration option will cause those paths to be used in the search for assets. -
config.assets.precompile
allows you to specify additional assets (other thanapplication.css
andapplication.js
) which are to be precompiled whenrake assets:precompile
is run. -
config.assets.prefix
defines the prefix where assets are served from. Defaults to/assets
. -
config.assets.manifest
defines the full path to be used for the asset precompiler's manifest file. Defaults to a file namedmanifest-<random>.json
in theconfig.assets.prefix
directory within the public folder. -
config.assets.digest
enables the use of MD5 fingerprints in asset names. Set totrue
by default inproduction.rb
anddevelopment.rb
. -
config.assets.debug
disables the concatenation and compression of assets. Set totrue
by default indevelopment.rb
. -
config.assets.cache_store
defines the cache store that Sprockets will use. The default is the Rails file store. -
config.assets.version
is an option string that is used in MD5 hash generation. This can be changed to force all files to be recompiled. -
config.assets.compile
is a boolean that can be used to turn on live Sprockets compilation in production. -
config.assets.logger
accepts a logger conforming to the interface of Log4r or the default RubyLogger
class. Defaults to the same configured atconfig.logger
. Settingconfig.assets.logger
to false will turn off served assets logging.
Configuring Generators
Rails allows you to alter what generators are used with the config.generators
method. This method takes a block:
config.generators do |g|
g.orm :active_record
g.test_framework :test_unit
end
The full set of methods that can be used in this block are as follows:
assets
allows to create assets on generating a scaffold. Defaults totrue
.force_plural
allows pluralized model names. Defaults tofalse
.helper
defines whether or not to generate helpers. Defaults totrue
.integration_tool
defines which integration tool to use. Defaults tonil
.javascripts
turns on the hook for JavaScript files in generators. Used in Rails for when thescaffold
generator is run. Defaults totrue
.javascript_engine
configures the engine to be used (for eg. coffee) when generating assets. Defaults tonil
.orm
defines which orm to use. Defaults tofalse
and will use Active Record by default.resource_controller
defines which generator to use for generating a controller when usingrails generate resource
. Defaults to:controller
.scaffold_controller
different fromresource_controller
, defines which generator to use for generating a scaffolded controller when usingrails generate scaffold
. Defaults to:scaffold_controller
.stylesheets
turns on the hook for stylesheets in generators. Used in Rails for when thescaffold
generator is run, but this hook can be used in other generates as well. Defaults totrue
.stylesheet_engine
configures the stylesheet engine (for eg. sass) to be used when generating assets. Defaults to:css
.test_framework
defines which test framework to use. Defaults tofalse
and will use Test::Unit by default.template_engine
defines which template engine to use, such as ERB or Haml. Defaults to:erb
.
Configuring Middleware
Every Rails application comes with a standard set of middleware which it uses in this order in the development environment:
- ::ActionDispatch::SSL forces every request to be under HTTPS protocol. Will be available if
config.force_ssl
is set totrue
. Options passed to this can be configured by usingconfig.ssl_options
. - ::ActionDispatch::Static is used to serve static assets. Disabled if
config.serve_static_files
isfalse
. Rack::Lock
wraps the app in mutex so it can only be called by a single thread at a time. Only enabled whenconfig.cache_classes
isfalse
.- ::ActiveSupport::Cache::Strategy::LocalCache serves as a basic memory backed cache. This cache is not thread safe and is intended only for serving as a temporary memory cache for a single thread.
Rack::Runtime
sets anX-Runtime
header, containing the time (in seconds) taken to execute the request.- ::Rails::Rack::Logger notifies the logs that the request has begun. After request is complete, flushes all the logs.
- ::ActionDispatch::ShowExceptions rescues any exception returned by the application and renders nice exception pages if the request is local or if
config.consider_all_requests_local
is set totrue
. Ifconfig.action_dispatch.show_exceptions
is set tofalse
, exceptions will be raised regardless. - ::ActionDispatch::RequestId makes a unique X-Request-Id header available to the response and enables the ActionDispatch::Request#uuid method.
- ::ActionDispatch::RemoteIp checks for IP spoofing attacks and gets valid
client_ip
from request headers. Configurable with theconfig.action_dispatch.ip_spoofing_check
, andconfig.action_dispatch.trusted_proxies
options. Rack::Sendfile
intercepts responses whose body is being served from a file and replaces it with a server specific X-Sendfile header. Configurable withconfig.action_dispatch.x_sendfile_header
.- ::ActionDispatch::Callbacks runs the prepare callbacks before serving the request.
- ::ActiveRecord::ConnectionAdapters::ConnectionManagement cleans active connections after each request, unless the
rack.test
key in the request environment is set totrue
. - ::ActiveRecord::QueryCache caches all SELECT queries generated in a request. If any INSERT or UPDATE takes place then the cache is cleaned.
- ::ActionDispatch::Cookies sets cookies for the request.
- ::ActionDispatch::Session::CookieStore is responsible for storing the session in cookies. An alternate middleware can be used for this by changing the
config.action_controller.session_store
to an alternate value. Additionally, options passed to this can be configured by usingconfig.action_controller.session_options
. - ::ActionDispatch::Flash sets up the
flash
keys. Only available ifconfig.action_controller.session_store
is set to a value. - ::ActionDispatch::ParamsParser parses out parameters from the request into
params
. Rack::MethodOverride
allows the method to be overridden ifparams[:_method]
is set. This is the middleware which supports the PATCH, PUT, and DELETE HTTP method types.Rack::Head
converts HEAD requests to GET requests and serves them as so.
Besides these usual middleware, you can add your own by using the config.middleware.use
method:
config.middleware.use Magical::Unicorns
This will put the Magical::Unicorns
middleware on the end of the stack. You can use insert_before
if you wish to add a middleware before another.
config.middleware.insert_before Rack::Head, Magical::Unicorns
There's also insert_after
which will insert a middleware after another:
config.middleware.insert_after Rack::Head, Magical::Unicorns
Middlewares can also be completely swapped out and replaced with others:
config.middleware.swap ActionController::Failsafe, Lifo::Failsafe
They can also be removed from the stack completely:
config.middleware.delete "Rack::MethodOverride"
Configuring i18n
All these configuration options are delegated to the I18n library.
-
config.i18n.available_locales
whitelists the available locales for the app. Defaults to all locale keys found in locale files, usually only:en
on a new application. -
config.i18n.default_locale
sets the default locale of an application used for i18n. Defaults to:en
. -
config.i18n.enforce_available_locales
ensures that all locales passed through i18n must be declared in theavailable_locales
list, raising anI18n::InvalidLocale
exception when setting an unavailable locale. Defaults totrue
. It is recommended not to disable this option unless strongly required, since this works as a security measure against setting any invalid locale from user input. -
config.i18n.load_path
sets the path Rails uses to look for locale files. Defaults toconfig/locales/*.{yml,rb}
.
Configuring Active Record
config.active_record
includes a variety of configuration options:
-
config.active_record.logger
accepts a logger conforming to the interface of Log4r or the default Ruby Logger class, which is then passed on to any new database connections made. You can retrieve this logger by callinglogger
on either an Active Record model class or an Active Record model instance. Set tonil
to disable logging. -
config.active_record.primary_key_prefix_type
lets you adjust the naming for primary key columns. By default, Rails assumes that primary key columns are namedid
(and this configuration option doesn't need to be set.) There are two other choices: **:table_name
would make the primary key for the Customer classcustomerid
**:table_name_with_underscore
would make the primary key for the Customer classcustomer_id
-
config.active_record.table_name_prefix
lets you set a global string to be prepended to table names. If you set this tonorthwest_
, then the Customer class will look fornorthwest_customers
as its table. The default is an empty string. -
config.active_record.table_name_suffix
lets you set a global string to be appended to table names. If you set this to_northwest
, then the Customer class will look forcustomers_northwest
as its table. The default is an empty string. -
config.active_record.schema_migrations_table_name
lets you set a string to be used as the name of the schema migrations table. -
config.active_record.pluralize_table_names
specifies whether Rails will look for singular or plural table names in the database. If set to true (the default), then the Customer class will use thecustomers
table. If set to false, then the Customer class will use thecustomer
table. -
config.active_record.default_timezone
determines whether to useTime.local
(if set to:local
) orTime.utc
(if set to:utc
) when pulling dates and times from the database. The default is:utc
. -
config.active_record.schema_format
controls the format for dumping the database schema to a file. The options are:ruby
(the default) for a database-independent version that depends on migrations, or:sql
for a set of (potentially database-dependent) SQL statements. -
config.active_record.timestamped_migrations
controls whether migrations are numbered with serial integers or with timestamps. The default is true, to use timestamps, which are preferred if there are multiple developers working on the same application. -
config.active_record.lock_optimistically
controls whether Active Record will use optimistic locking and is true by default. -
config.active_record.cache_timestamp_format
controls the format of the timestamp value in the cache key. Default is:number
. -
config.active_record.record_timestamps
is a boolean value which controls whether or not timestamping ofcreate
andupdate
operations on a model occur. The default value istrue
. -
config.active_record.partial_writes
is a boolean value and controls whether or not partial writes are used (i.e. whether updates only set attributes that are dirty). Note that when using partial writes, you should also use optimistic lockingconfig.active_record.lock_optimistically
since concurrent updates may write attributes based on a possibly stale read state. The default value istrue
. -
config.active_record.maintain_test_schema
is a boolean value which controls whether Active Record should try to keep your test database schema up-to-date withdb/schema.rb
(ordb/structure.sql
) when you run your tests. The default is true. -
config.active_record.dump_schema_after_migration
is a flag which controls whether or not schema dump should happen (db/schema.rb
ordb/structure.sql
) when you run migrations. This is set to false inconfig/environments/production.rb
which is generated by Rails. The default value is true if this configuration is not set.
The MySQL adapter adds one additional configuration option:
ActiveRecord::ConnectionAdapters::MysqlAdapter.emulate_booleans
controls whether Active Record will consider alltinyint(1)
columns in a MySQL database to be booleans and is true by default.
The schema dumper adds one additional configuration option:
- ActiveRecord::SchemaDumper.ignore_tables accepts an array of tables that should not be included in any generated schema file. This setting is ignored unless
config.active_record.schema_format == :ruby
.
Configuring Action Controller
config.action_controller
includes a number of configuration settings:
-
config.action_controller.asset_host
sets the host for the assets. Useful when CDNs are used for hosting assets rather than the application server itself. -
config.action_controller.perform_caching
configures whether the application should perform caching or not. Set to false in development mode, true in production. -
config.action_controller.default_static_extension
configures the extension used for cached pages. Defaults to.html
. -
config.action_controller.default_charset
specifies the default character set for all renders. The default is "utf-8". -
config.action_controller.logger
accepts a logger conforming to the interface of Log4r or the default Ruby Logger class, which is then used to log information from Action Controller. Set tonil
to disable logging. -
config.action_controller.request_forgery_protection_token
sets the token parameter name for RequestForgery. Callingprotect_from_forgery
sets it to:authenticity_token
by default. -
config.action_controller.allow_forgery_protection
enables or disables CSRF protection. By default this isfalse
in test mode andtrue
in all other modes. -
config.action_controller.relative_url_root
can be used to tell Rails that you are deploying to a subdirectory. The default isENV['RAILS_RELATIVE_URL_ROOT']
. -
config.action_controller.permit_all_parameters
sets all the parameters for mass assignment to be permitted by default. The default value isfalse
. -
config.action_controller.action_on_unpermitted_parameters
enables logging or raising an exception if parameters that are not explicitly permitted are found. Set to:log
or:raise
to enable. The default value is:log
in development and test environments, andfalse
in all other environments. -
config.action_controller.always_permitted_parameters
sets a list of whitelisted parameters that are permitted by default. The default values are['controller', 'action']
.
Configuring Action Dispatch
-
config.action_dispatch.session_store
sets the name of the store for session data. The default is:cookie_store
; other valid options include:active_record_store
,:mem_cache_store
or the name of your own custom class. -
config.action_dispatch.default_headers
is a hash with HTTP headers that are set by default in each response. By default, this is defined as:config.action_dispatch.default_headers = { 'X-Frame-Options' => 'SAMEORIGIN', 'X-XSS-Protection' => '1; mode=block', 'X-Content-Type-Options' => 'nosniff' }
-
config.action_dispatch.tld_length
sets the TLD (top-level domain) length for the application. Defaults to1
. -
config.action_dispatch.http_auth_salt
sets the HTTP Auth salt value. Defaults to'http authentication'
. -
config.action_dispatch.signed_cookie_salt
sets the signed cookies salt value. Defaults to'signed cookie'
. -
config.action_dispatch.encrypted_cookie_salt
sets the encrypted cookies salt value. Defaults to'encrypted cookie'
. -
config.action_dispatch.encrypted_signed_cookie_salt
sets the signed encrypted cookies salt value. Defaults to'signed encrypted cookie'
. -
config.action_dispatch.perform_deep_munge
configures whetherdeep_munge
method should be performed on the parameters. See Security Guide for more information. It defaults to true. -
config.action_dispatch.rescue_responses
configures what exceptions are assigned to an HTTP status. It accepts a hash and you can specify pairs of exception/status. By default, this is defined as:config.action_dispatch.rescue_responses = { 'ActionController::RoutingError' => :not_found, 'AbstractController::ActionNotFound' => :not_found, 'ActionController::MethodNotAllowed' => :method_not_allowed, 'ActionController::UnknownHttpMethod' => :method_not_allowed, 'ActionController::NotImplemented' => :not_implemented, 'ActionController::UnknownFormat' => :not_acceptable, 'ActionController::InvalidAuthenticityToken' => :unprocessable_entity, 'ActionController::InvalidCrossOriginRequest' => :unprocessable_entity, 'ActionDispatch::ParamsParser::ParseError' => :bad_request, 'ActionController::BadRequest' => :bad_request, 'ActionController::ParameterMissing' => :bad_request, 'ActiveRecord::RecordNotFound' => :not_found, 'ActiveRecord::StaleObjectError' => :conflict, 'ActiveRecord::RecordInvalid' => :unprocessable_entity, 'ActiveRecord::RecordNotSaved' => :unprocessable_entity }
Any exceptions that are not configured will be mapped to 500 Internal Server Error.
-
ActionDispatch::Callbacks.before takes a block of code to run before the request.
-
ActionDispatch::Callbacks#to_prepare takes a block to run after ActionDispatch::Callbacks.before, but before the request. Runs for every request in
development
mode, but only once forproduction
or environments withcache_classes
set totrue
. -
ActionDispatch::Callbacks.after takes a block of code to run after the request.
Configuring Action View
config.action_view
includes a small number of configuration settings:
-
config.action_view.field_error_proc
provides an HTML generator for displaying errors that come from Active Record. The default isProc.new do |html_tag, instance| %Q(<div class="field_with_errors">#{html_tag}</div>).html_safe end
-
config.action_view.default_form_builder
tells Rails which form builder to use by default. The default is ::ActionView::Helpers::FormBuilder. If you want your form builder class to be loaded after initialization (so it's reloaded on each request in development), you can pass it as a String -
config.action_view.logger
accepts a logger conforming to the interface of Log4r or the default Ruby Logger class, which is then used to log information from Action View. Set tonil
to disable logging. -
config.action_view.erb_trim_mode
gives the trim mode to be used by ERB. It defaults to'-'
, which turns on trimming of tail spaces and newline when using<%= -%>
or<%= =%>
. See the Erubis documentation for more information. -
config.action_view.embed_authenticity_token_in_remote_forms
allows you to set the default behavior forauthenticity_token
in forms with:remote => true
. By default it's set to false, which means that remote forms will not includeauthenticity_token
, which is helpful when you're fragment-caching the form. Remote forms get the authenticity from themeta
tag, so embedding is unnecessary unless you support browsers without JavaScript. In such case you can either pass:authenticity_token => true
as a form option or set this config setting totrue
-
config.action_view.prefix_partial_path_with_controller_namespace
determines whether or not partials are looked up from a subdirectory in templates rendered from namespaced controllers. For example, consider a controller namedAdmin::ArticlesController
which renders this template:<%= render @article %>
The default setting is
true
, which uses the partial at/admin/articles/_article.erb
. Setting the value tofalse
would render/articles/_article.erb
, which is the same behavior as rendering from a non-namespaced controller such asArticlesController
. -
config.action_view.raise_on_missing_translations
determines whether an error should be raised for missing translations
Configuring Action Mailer
There are a number of settings available on config.action_mailer
:
-
config.action_mailer.logger
accepts a logger conforming to the interface of Log4r or the default Ruby Logger class, which is then used to log information from Action Mailer. Set tonil
to disable logging. -
config.action_mailer.smtp_settings
allows detailed configuration for the:smtp
delivery method. It accepts a hash of options, which can include any of these options::address
- Allows you to use a remote mail server. Just change it from its default "localhost" setting.:port
- On the off chance that your mail server doesn't run on port 25, you can change it.:domain
- If you need to specify a HELO domain, you can do it here.:user_name
- If your mail server requires authentication, set the username in this setting.:password
- If your mail server requires authentication, set the password in this setting.:authentication
- If your mail server requires authentication, you need to specify the authentication type here. This is a symbol and one of:plain
,:login
,:cram_md5
.
-
config.action_mailer.sendmail_settings
allows detailed configuration for thesendmail
delivery method. It accepts a hash of options, which can include any of these options::location
- The location of the sendmail executable. Defaults to/usr/sbin/sendmail
.:arguments
- The command line arguments. Defaults to-i -t
.
-
config.action_mailer.raise_delivery_errors
specifies whether to raise an error if email delivery cannot be completed. It defaults to true. -
config.action_mailer.delivery_method
defines the delivery method and defaults to:smtp
. See the configuration section in the Action Mailer guide for more info. -
config.action_mailer.perform_deliveries
specifies whether mail will actually be delivered and is true by default. It can be convenient to set it to false for testing. -
config.action_mailer.default_options
configures Action Mailer defaults. Use to set options likefrom
orreply_to
for every mailer. These default to:mime_version: "1.0", charset: "UTF-8", content_type: "text/plain", parts_order: ["text/plain", "text/enriched", "text/html"]
Assign a hash to set additional options:
config.action_mailer. = { from<EMAIL_ADDRESS>}
-
config.action_mailer.observers
registers observers which will be notified when mail is delivered.config.action_mailer.observers = ["MailObserver"]
-
config.action_mailer.interceptors
registers interceptors which will be called before mail is sent.config.action_mailer.interceptors = ["MailInterceptor"]
-
config.action_mailer.preview_path
specifies the location of mailer previews.config.action_mailer.preview_path = "#{Rails.root}/lib/mailer_previews"
-
config.action_mailer.show_previews
enable or disable mailer previews. By default this istrue
in development.config.action_mailer.show_previews = false
Configuring Active Support
There are a few configuration options available in Active Support:
-
config.active_support.bare
enables or disables the loading ofactive_support/all
when booting Rails. Defaults tonil
, which meansactive_support/all
is loaded. -
config.active_support.test_order
sets the order that test cases are executed. Possible values are:sorted
and:random
. Currently defaults to:sorted
. In Rails 5.0, the default will be changed to:random
instead. -
config.active_support.escape_html_entities_in_json
enables or disables the escaping of HTML entities in JSON serialization. Defaults tofalse
. -
config.active_support.use_standard_json_time_format
enables or disables serializing dates to ISO 8601 format. Defaults totrue
. -
config.active_support.time_precision
sets the precision of JSON encoded time values. Defaults to3
. -
ActiveSupport::Logger.silencer is set to
false
to disable the ability to silence logging in a block. The default istrue
. -
ActiveSupport::Cache::Store.logger specifies the logger to use within cache store operations.
-
ActiveSupport::Deprecation.behavior
alternative setter toconfig.active_support.deprecation
which configures the behavior of deprecation warnings for Rails. -
ActiveSupport::Deprecation.silence
takes a block in which all deprecation warnings are silenced. -
ActiveSupport::Deprecation.silenced
sets whether or not to display deprecation warnings.
Configuring a Database
Just about every Rails application will interact with a database. You can connect to the database by setting an environment variable ENV['DATABASE_URL']
or by using a configuration file called config/database.yml
.
Using the config/database.yml
file you can specify all the information needed to access your database:
development:
adapter: postgresql
database: blog_development
pool: 5
This will connect to the database named blog_development
using the postgresql
adapter. This same information can be stored in a URL and provided via an environment variable like this:
> puts ENV['DATABASE_URL']
postgresql://localhost/blog_development?pool=5
The config/database.yml
file contains sections for three different environments in which Rails can run by default:
- The
development
environment is used on your development/local computer as you interact manually with the application. - The
test
environment is used when running automated tests. - The
production
environment is used when you deploy your application for the world to use.
If you wish, you can manually specify a URL inside of your config/database.yml
development:
url: postgresql://localhost/blog_development?pool=5
The config/database.yml
file can contain ERB tags <%= %>
. Anything in the tags will be evaluated as Ruby code. You can use this to pull out data from an environment variable or to perform calculations to generate the needed connection information.
TIP: You don't have to update the database configurations manually. If you look at the options of the application generator, you will see that one of the options is named --database
. This option allows you to choose an adapter from a list of the most used relational databases. You can even run the generator repeatedly: cd .. && rails new blog --database=mysql
. When you confirm the overwriting of the config/database.yml
file, your application will be configured for MySQL instead of SQLite. Detailed examples of the common database connections are below.
Connection Preference
Since there are two ways to set your connection, via environment variable it is important to understand how the two can interact.
If you have an empty config/database.yml
file but your ENV['DATABASE_URL']
is present, then Rails will connect to the database via your environment variable:
$ cat config/database.yml
$ echo $DATABASE_URL
postgresql://localhost/my_database
If you have a config/database.yml
but no ENV['DATABASE_URL']
then this file will be used to connect to your database:
$ cat config/database.yml
development:
adapter: postgresql
database: my_database
host: localhost
$ echo $DATABASE_URL
If you have both config/database.yml
and ENV['DATABASE_URL']
set then Rails will merge the configuration together. To better understand this we must see some examples.
When duplicate connection information is provided the environment variable will take precedence:
$ cat config/database.yml
development:
adapter: sqlite3
database: NOT_my_database
host: localhost
$ echo $DATABASE_URL
postgresql://localhost/my_database
$ bin/rails runner 'puts ActiveRecord::Base.configurations'
{"development"=>{"adapter"=>"postgresql", "host"=>"localhost", "database"=>"my_database"}}
Here the adapter, host, and database match the information in ENV['DATABASE_URL']
.
If non-duplicate information is provided you will get all unique values, environment variable still takes precedence in cases of any conflicts.
$ cat config/database.yml
development:
adapter: sqlite3
pool: 5
$ echo $DATABASE_URL
postgresql://localhost/my_database
$ bin/rails runner 'puts ActiveRecord::Base.configurations'
{"development"=>{"adapter"=>"postgresql", "host"=>"localhost", "database"=>"my_database", "pool"=>5}}
Since pool is not in the ENV['DATABASE_URL']
provided connection information its information is merged in. Since adapter
is duplicate, the ENV['DATABASE_URL']
connection information wins.
The only way to explicitly not use the connection information in ENV['DATABASE_URL']
is to specify an explicit URL connection using the "url"
sub key:
$ cat config/database.yml
development:
url: sqlite3:NOT_my_database
$ echo $DATABASE_URL
postgresql://localhost/my_database
$ bin/rails runner 'puts ActiveRecord::Base.configurations'
{"development"=>{"adapter"=>"sqlite3", "database"=>"NOT_my_database"}}
Here the connection information in ENV['DATABASE_URL']
is ignored, note the different adapter and database name.
Since it is possible to embed ERB in your config/database.yml
it is best practice to explicitly show you are using the ENV['DATABASE_URL']
to connect to your database. This is especially useful in production since you should not commit secrets like your database password into your source control (such as Git).
$ cat config/database.yml
production:
url: <%= ENV['DATABASE_URL'] %>
Now the behavior is clear, that we are only using the connection information in ENV['DATABASE_URL']
.
Configuring an SQLite3 Database
Rails comes with built-in support for SQLite3, which is a lightweight serverless database application. While a busy production environment may overload SQLite, it works well for development and testing. Rails defaults to using an SQLite database when creating a new project, but you can always change it later.
Here's the section of the default configuration file (config/database.yml
) with connection information for the development environment:
development:
adapter: sqlite3
database: db/development.sqlite3
pool: 5
timeout: 5000
NOTE: Rails uses an SQLite3 database for data storage by default because it is a zero configuration database that just works. Rails also supports MySQL and PostgreSQL "out of the box", and has plugins for many database systems. If you are using a database in a production environment Rails most likely has an adapter for it.
Configuring a MySQL Database
If you choose to use MySQL instead of the shipped SQLite3 database, your config/database.yml
will look a little different. Here's the development section:
development:
adapter: mysql2
encoding: utf8
database: blog_development
pool: 5
username: root
password:
socket: /tmp/mysql.sock
If your development computer's MySQL installation includes a root user with an empty password, this configuration should work for you. Otherwise, change the username and password in the development
section as appropriate.
Configuring a PostgreSQL Database
If you choose to use PostgreSQL, your config/database.yml
will be customized to use PostgreSQL databases:
development:
adapter: postgresql
encoding: unicode
database: blog_development
pool: 5
Prepared Statements are enabled by default on PostgreSQL. You can be disable prepared statements by setting prepared_statements
to false
:
production:
adapter: postgresql
prepared_statements: false
If enabled, Active Record will create up to 1000
prepared statements per database connection by default. To modify this behavior you can set statement_limit
to a different value:
production:
adapter: postgresql
statement_limit: 200
The more prepared statements in use: the more memory your database will require. If your PostgreSQL database is hitting memory limits, try lowering statement_limit
or disabling prepared statements.
Configuring an SQLite3 Database for JRuby Platform
If you choose to use SQLite3 and are using JRuby, your config/database.yml
will look a little different. Here's the development section:
development:
adapter: jdbcsqlite3
database: db/development.sqlite3
Configuring a MySQL Database for JRuby Platform
If you choose to use MySQL and are using JRuby, your config/database.yml
will look a little different. Here's the development section:
development:
adapter: jdbcmysql
database: blog_development
username: root
password:
Configuring a PostgreSQL Database for JRuby Platform
If you choose to use PostgreSQL and are using JRuby, your config/database.yml
will look a little different. Here's the development section:
development:
adapter: jdbcpostgresql
encoding: unicode
database: blog_development
username: blog
password:
Change the username and password in the development
section as appropriate.
Creating Rails Environments
By default Rails ships with three environments: "development", "test", and "production". While these are sufficient for most use cases, there are circumstances when you want more environments.
Imagine you have a server which mirrors the production environment but is only used for testing. Such a server is commonly called a "staging server". To define an environment called "staging" for this server, just create a file called config/environments/staging.rb
. Please use the contents of any existing file in config/environments
as a starting point and make the necessary changes from there.
That environment is no different than the default ones, start a server with rails server -e staging
, a console with rails console staging
, Rails.env.staging?
works, etc.
Deploy to a subdirectory (relative url root)
By default Rails expects that your application is running at the root
(eg. /
). This section explains how to run your application inside a directory.
Let's assume we want to deploy our application to "/app1". Rails needs to know this directory to generate the appropriate routes:
config.relative_url_root = "/app1"
alternatively you can set the RAILS_RELATIVE_URL_ROOT
environment
variable.
Rails will now prepend "/app1" when generating links.
Using Passenger
Passenger makes it easy to run your application in a subdirectory. You can find the relevant configuration in the Passenger manual.
Using a Reverse Proxy
Deploying your application using a reverse proxy has definite advantages over traditional deploys. They allow you to have more control over your server by layering the components required by your application.
Many modern web servers can be used as a proxy server to balance third-party elements such as caching servers or application servers.
One such application server you can use is Unicorn to run behind a reverse proxy.
In this case, you would need to configure the proxy server (NGINX, Apache, etc) to accept connections from your application server (Unicorn). By default Unicorn will listen for TCP connections on port 8080, but you can change the port or configure it to use sockets instead.
You can find more information in the Unicorn readme and understand the philosophy behind it.
Once you've configured the application server, you must proxy requests to it by configuring your web server appropriately. For example your NGINX config may include:
upstream application_server {
server <IP_ADDRESS>:8080
}
server {
listen 80;
server_name localhost;
root /root/path/to/your_app/public;
try_files $uri/index.html $uri.html @app;
location @app {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_pass http://application_server;
}
# some other configuration
}
Be sure to read the NGINX documentation for the most up-to-date information.
Considerations when deploying to a subdirectory
Deploying to a subdirectory in production has implications on various parts of Rails.
- development environment:
- testing environment:
- serving static assets:
- asset pipeline:
Rails Environment Settings
Some parts of Rails can also be configured externally by supplying environment variables. The following environment variables are recognized by various parts of Rails:
-
ENV["RAILS_ENV"]
defines the Rails environment (production, development, test, and so on) that Rails will run under. -
ENV["RAILS_RELATIVE_URL_ROOT"]
is used by the routing code to recognize URLs when you deploy your application to a subdirectory. -
ENV["RAILS_CACHE_ID"]
andENV["RAILS_APP_VERSION"]
are used to generate expanded cache keys in Rails' caching code. This allows you to have multiple separate caches from the same application.
Using Initializer Files
After loading the framework and any gems in your application, Rails turns to loading initializers. An initializer is any Ruby file stored under config/initializers
in your application. You can use initializers to hold configuration settings that should be made after all of the frameworks and gems are loaded, such as options to configure settings for these parts.
NOTE: You can use subfolders to organize your initializers if you like, because Rails will look into the whole file hierarchy from the initializers folder on down.
TIP: If you have any ordering dependency in your initializers, you can control the load order through naming. Initializer files are loaded in alphabetical order by their path. For example, 01_critical.rb
will be loaded before 02_normal.rb
.
Initialization events
Rails has 5 initialization events which can be hooked into (listed in the order that they are run):
-
before_configuration
: This is run as soon as the application constant inherits from ::Rails::Application. Theconfig
calls are evaluated before this happens. -
before_initialize
: This is run directly before the initialization process of the application occurs with the:bootstrap_hook
initializer near the beginning of the Rails initialization process. -
to_prepare
: Run after the initializers are run for all Railties (including the application itself), but before eager loading and the middleware stack is built. More importantly, will run upon every request indevelopment
, but only once (during boot-up) inproduction
andtest
. -
before_eager_load
: This is run directly before eager loading occurs, which is the default behavior for theproduction
environment and not for thedevelopment
environment. -
after_initialize
: Run directly after the initialization of the application, after the application initializers inconfig/initializers
are run.
To define an event for these hooks, use the block syntax within a ::Rails::Application, ::Rails::Railtie or ::Rails::Engine subclass:
module YourApp
class Application < Rails::Application
config.before_initialize do
# initialization code goes here
end
end
end
Alternatively, you can also do it through the config
method on the Rails.application object:
Rails.application.config.before_initialize do
# initialization code goes here
end
WARNING: Some parts of your application, notably routing, are not yet set up at the point where the after_initialize
block is called.
Rails::Railtie#initializer
Rails has several initializers that run on startup that are all defined by using the initializer
method from ::Rails::Railtie. Here's an example of the set_helpers_path
initializer from Action Controller:
initializer "action_controller.set_helpers_path" do |app|
ActionController::Helpers.helpers_path = app.helpers_paths
end
The initializer
method takes three arguments with the first being the name for the initializer and the second being an options hash (not shown here) and the third being a block. The :before
key in the options hash can be specified to specify which initializer this new initializer must run before, and the :after
key will specify which initializer to run this initializer after.
Initializers defined using the initializer
method will be run in the order they are defined in, with the exception of ones that use the :before
or :after
methods.
WARNING: You may put your initializer before or after any other initializer in the chain, as long as it is logical. Say you have 4 initializers called "one" through "four" (defined in that order) and you define "four" to go before "four" but after "three", that just isn't logical and Rails will not be able to determine your initializer order.
The block argument of the initializer
method is the instance of the application itself, and so we can access the configuration on it by using the config
method as done in the example.
Because ::Rails::Application inherits from ::Rails::Railtie (indirectly), you can use the initializer
method in config/application.rb
to define initializers for the application.
Initializers
Below is a comprehensive list of all the initializers found in Rails in the order that they are defined (and therefore run in, unless otherwise stated).
-
load_environment_hook
Serves as a placeholder so that:load_environment_config
can be defined to run before it. -
load_active_support
Requiresactive_support/dependencies
which sets up the basis for Active Support. Optionally requiresactive_support/all
ifconfig.active_support.bare
is un-truthful, which is the default. -
initialize_logger
Initializes the logger (an ::ActiveSupport::Logger object) for the application and makes it accessible at Rails.logger, provided that no initializer inserted before this point has defined Rails.logger. -
initialize_cache
If Rails.cache isn't set yet, initializes the cache by referencing the value inconfig.cache_store
and stores the outcome as Rails.cache. If this object responds to themiddleware
method, its middleware is inserted beforeRack::Runtime
in the middleware stack. -
set_clear_dependencies_hook
Provides a hook foractive_record.set_dispatch_hooks
to use, which will run before this initializer. This initializer - which runs only ifcache_classes
is set tofalse
- uses ActionDispatch::Callbacks.after to remove the constants which have been referenced during the request from the object space so that they will be reloaded during the following request. -
initialize_dependency_mechanism
Ifconfig.cache_classes
is true, configures ActiveSupport::Dependencies.mechanism torequire
dependencies rather thanload
them. -
bootstrap_hook
Runs all configuredbefore_initialize
blocks. -
i18n.callbacks
In the development environment, sets up ato_prepare
callback which will callI18n.reload!
if any of the locales have changed since the last request. In production mode this callback will only run on the first request. -
active_support.deprecation_behavior
Sets up deprecation reporting for environments, defaulting to:log
for development,:notify
for production and:stderr
for test. If a value isn't set forconfig.active_support.deprecation
then this initializer will prompt the user to configure this line in the current environment'sconfig/environments
file. Can be set to an array of values. -
active_support.initialize_time_zone
Sets the default time zone for the application based on theconfig.time_zone
setting, which defaults to "UTC". -
active_support.initialize_beginning_of_week
Sets the default beginning of week for the application based onconfig.beginning_of_week
setting, which defaults to:monday
. -
action_dispatch.configure
Configures the ActionDispatch::Http::URL.tld_length to be set to the value ofconfig.action_dispatch.tld_length
. -
action_view.set_configs
Sets up Action View by using the settings inconfig.action_view
bysend
'ing the method names as setters to ::ActionView::Base and passing the values through. -
action_controller.logger
SetsActionController::Base.logger
- if it's not already set - to Rails.logger. -
action_controller.initialize_framework_caches
SetsActionController::Base.cache_store
- if it's not already set - to Rails.cache. -
action_controller.set_configs
Sets up Action Controller by using the settings inconfig.action_controller
bysend
'ing the method names as setters to ::ActionController::Base and passing the values through. -
action_controller.compile_config_methods
Initializes methods for the config settings specified so that they are quicker to access. -
active_record.initialize_timezone
SetsActiveRecord::Base.time_zone_aware_attributes
to true, as well as setting ActiveRecord::Base.default_timezone to UTC. When attributes are read from the database, they will be converted into the time zone specified by Time.zone. -
active_record.logger
Sets ActiveRecord::Base.logger - if it's not already set - to Rails.logger. -
active_record.set_configs
Sets up Active Record by using the settings inconfig.active_record
bysend
'ing the method names as setters to ::ActiveRecord::Base and passing the values through. -
active_record.initialize_database
Loads the database configuration (by default) fromconfig/database.yml
and establishes a connection for the current environment. -
active_record.log_runtime
Includes ::ActiveRecord::Railties::ControllerRuntime which is responsible for reporting the time taken by Active Record calls for the request back to the logger. -
active_record.set_dispatch_hooks
Resets all reloadable connections to the database ifconfig.cache_classes
is set tofalse
. -
action_mailer.logger
Sets ActionMailer::Base.logger - if it's not already set - to Rails.logger. -
action_mailer.set_configs
Sets up Action Mailer by using the settings inconfig.action_mailer
bysend
'ing the method names as setters to ::ActionMailer::Base and passing the values through. -
action_mailer.compile_config_methods
Initializes methods for the config settings specified so that they are quicker to access. -
set_load_path
This initializer runs beforebootstrap_hook
. Adds thevendor
,lib
, all directories ofapp
and any paths specified byconfig.load_paths
to$LOAD_PATH
. -
set_autoload_paths
This initializer runs beforebootstrap_hook
. Adds all sub-directories ofapp
and paths specified byconfig.autoload_paths
to ActiveSupport::Dependencies.autoload_paths. -
add_routing_paths
Loads (by default) allconfig/routes.rb
files (in the application and railties, including engines) and sets up the routes for the application. -
add_locales
Adds the files inconfig/locales
(from the application, railties and engines) toI18n.load_path
, making available the translations in these files. -
add_view_paths
Adds the directoryapp/views
from the application, railties and engines to the lookup path for view files for the application. -
load_environment_config
Loads theconfig/environments
file for the current environment. -
append_asset_paths
Finds asset paths for the application and all attached railties and keeps a track of the available directories inconfig.static_asset_paths
. -
prepend_helpers_path
Adds the directoryapp/helpers
from the application, railties and engines to the lookup path for helpers for the application. -
load_config_initializers
Loads all Ruby files fromconfig/initializers
in the application, railties and engines. The files in this directory can be used to hold configuration settings that should be made after all of the frameworks are loaded. -
engines_blank_point
Provides a point-in-initialization to hook into if you wish to do anything before engines are loaded. After this point, all railtie and engine initializers are run. -
add_generator_templates
Finds templates for generators atlib/templates
for the application, railties and engines and adds these to theconfig.generators.templates
setting, which will make the templates available for all generators to reference. -
ensure_autoload_once_paths_as_subset
Ensures that theconfig.autoload_once_paths
only contains paths fromconfig.autoload_paths
. If it contains extra paths, then an exception will be raised. -
add_to_prepare_blocks
The block for everyconfig.to_prepare
call in the application, a railtie or engine is added to theto_prepare
callbacks for Action Dispatch which will be run per request in development, or before the first request in production. -
add_builtin_route
If the application is running under the development environment then this will append the route forrails/info/properties
to the application routes. This route provides the detailed information such as Rails and Ruby version forpublic/index.html
in a default Rails application. -
build_middleware_stack
Builds the middleware stack for the application, returning an object which has acall
method which takes a Rack environment object for the request. -
eager_load!
Ifconfig.eager_load
is true, runs theconfig.before_eager_load
hooks and then callseager_load!
which will load allconfig.eager_load_namespaces
. -
finisher_hook
Provides a hook for after the initialization of process of the application is complete, as well as running all theconfig.after_initialize
blocks for the application, railties and engines. -
set_routes_reloader
Configures Action Dispatch to reload the routes file using ActionDispatch::Callbacks#to_prepare. -
disable_dependency_loading
Disables the automatic dependency loading if theconfig.eager_load
is set to true.
Database pooling
Active Record database connections are managed by ::ActiveRecord::ConnectionAdapters::ConnectionPool which ensures that a connection pool synchronizes the amount of thread access to a limited number of database connections. This limit defaults to 5 and can be configured in database.yml
.
development:
adapter: sqlite3
database: db/development.sqlite3
pool: 5
timeout: 5000
Since the connection pooling is handled inside of Active Record by default, all application servers (Thin, mongrel, Unicorn etc.) should behave the same. Initially, the database connection pool is empty and it will create additional connections as the demand for them increases, until it reaches the connection pool limit.
Any one request will check out a connection the first time it requires access to the database, after which it will check the connection back in, at the end of the request, meaning that the additional connection slot will be available again for the next request in the queue.
If you try to use more connections than are available, Active Record will block and wait for a connection from the pool. When it cannot get connection, a timeout error similar to given below will be thrown.
ActiveRecord::ConnectionTimeoutError - could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it:
If you get the above error, you might want to increase the size of connection
pool by incrementing the pool
option in database.yml
NOTE. If you are running in a multi-threaded environment, there could be a chance that several threads may be accessing multiple connections simultaneously. So depending on your current request load, you could very well have multiple threads contending for a limited amount of connections.
Custom configuration
You can configure your own code through the Rails configuration object with custom configuration under the config.x
property. It works like this:
config.x.payment_processing.schedule = :daily
config.x.payment_processing.retries = 3
config.x.super_debugger = true
These configuration points are then available through the configuration object:
Rails.configuration.x.payment_processing.schedule # => :daily
Rails.configuration.x.payment_processing.retries # => 3
Rails.configuration.x.super_debugger # => true
Rails.configuration.x.super_debugger.not_set # => nil
You can also use Rails::Application.config_for to load whole configuration files:
# config/payment.yml:
production:
environment: production
merchant_id: production_merchant_id
public_key: production_public_key
private_key: production_private_key
development:
environment: sandbox
merchant_id: development_merchant_id
public_key: development_public_key
private_key: development_private_key
# config/application.rb
module MyApp
class Application < Rails::Application
config.x.payment = config_for(:payment)
end
end
Rails.configuration.x.payment['merchant_id'] # => production_merchant_id or development_merchant_id


Custom Tooltips ::: qTip2
Chapter 5: Creating Custom Tooltips
Here's a list of links:
Home
About
Contact
Our Work


Alice, The Queen and an Egg.
Name
Occupation
Status
Humpty Dumpty
Sitting on walls
Broken
Alice of Wonderland
Hallucinating
Back home
Queen Grimhilde
Being evil
Not good
Colors
Shapes
Senses
Blue
Circle
Taste
I didn't think the theme through
Sight
Square
Smell


Email/Password Incorrect. Try again.
LoginJeffrey accounts are simple, fast, and elegant. It's how accounts were made to be.
While you create your account, this window will hide. Once you're done creating your account, this window will reappear for you to continue logging in.


| name | advantages | ingredients | the use | warnings |
|---|---|---|---|---|
| forever therme |
1.  Healthy metabolism 3. Regulating blood sugar levels |
Blackberries,greentea,vitamine b,green coffe seeds | Take two pills daily |
1. Do not exceed the dose
2. Not recommended for pregnant women and children |
| forever light Altra |
1. Feeling full
2.provide energy for the body |
Proteins,carbohydrate | 25 ml with 300 ml of milk |
1. Do not use the package if it is damaged or torn
2. Not recommended for pregnant women and children |
| forever fields of greens |
1. Rich source of antioxidants
2.  Not recommended for pregnant women and children |
| aloe blossom herbal tea |
1. It does not contain caffeine
2. Incredible flavor and aroma 3. Zero calories |
Aloe vera blossoms,Cinnamon,Ginger | One tea bag per cup let it brew for 5 minutes | ________ |
| forever fast break |
1. Contains pure protein
2. provide energy |
Milk chocolate and peanut butter,fiber,vitamine | Two tablets per day | ________ |
| forever lean |
1. Helps prevent calorie absorption from fats and carbohydrates
2. Control blood sugar level |
Indian fig extract,White Bean Extract | Take one capsule daily before a meal, four times a day | Not recommended for pregnant women and children |


{{merchant.address.addressLine1}}, {{merchant.address.addressLine2}}, {{merchant.address.city}}, {{merchant.address.state}} - {{merchant.address.pincode}}, {{merchant.address.country}}


Deleting a Sub-Album
Module Editors can delete a sub-album (child album) from the Gallery module.
- Navigate to the parent album of the sub-album to be deleted and open menu. See "Opening the Album Menu"
- Select Edit This Album from the album menu.
- Go to the Sub-Albums and Files Currently Contained In This Album section.
- Click the Delete button beside the album to be deleted. This displays the message "Are You Sure You Want To Delete The Album Named '[Album Name]'?
-
Click the OK button to confirm.
- Repeat Steps 4-5 to delete additional albums.


3D Flying Prey Simulator
Collaborating with a team of engineers and biologists, my colleagues and I designed, fabricated, and programmed a machine to aid in the investigation of the neuronal control of flying prey interception in dragonflies. The task involved constructing an apparatus to simulate the complex motions of a flying insect. In this fashion, the 3D motion device can mimic a flying insect by moving a small bead accurately up to speeds of 1 m/s in any direction.
Dragonflies are efficient aerial predators that can intercept and capture small insects in flight. The stimulus device is still in use to investigate the way in which dragonfly neurons encode information about object movement in 3D. In a broader context, this work could lead to the development of more effective guidance mechanisms for military or civilian use.


Ajax: Handling Server Data
Building HTML Table from Client Data
Getting XML Data from Server, Building HTML Table
City Type:
Largest Five US Cities
Second Five US Cities
US Cities Starting with 'S'
Most Recent Superbowl Hosts
Getting JSON Data from Server, Building HTML Table
City Type:
Largest Five US Cities
Second Five US Cities
US Cities Starting with 'S'
Most Recent Superbowl Hosts
Getting String Data from Server, Building HTML Table
City Type:
Largest Five US Cities
Second Five US Cities
US Cities Starting with 'S'
Most Recent Superbowl Hosts
Choosing Server Datatype, Building HTML Table
City Type:
Largest Five US Cities
Second Five US Cities
US Cities Starting with 'S'
Most Recent Superbowl Hosts
Server Data Type:
XML
JSON
String


Dialogue with consumers, re-developing products, performing risk analysis, keeping the data safe, creating new revenue streams, customizing user experience in real time, reducing maintenance costs, making our world smarter is why I am in love with data!


TouchCPLib
1.0.0
A touch-enabled GUI interface based on SDL and libTS. It provides a simple desktop-free UI for your embedded Raspberry projects.
XYPlot.cpp File Reference
#include "
TouchCP/XYPlot.h
"
Include dependency graph for XYPlot.cpp:
src
XYPlot.cpp
Generated by
1.8.13


Harlem Election Rematch: Money and Demographics in the 13th
03:00 PM - 03:30 PM on August 16, 2014, Room 704Haronil Estevez
- Audience level:
- novice
Description
Changing demographics in New York State's 13th Congressional District led to a close election that was decided by fewer than 1,100 votes two years ago. The contest between the long standing incumbent Representative Charles B. Rangel and State Senator Adriano D. Espaillat will be replayed this June. In this talk I will use Python Numpy and pandas to analyze campaign contribution data provided for each candidate provided by the US Federal Election Commission and the United State Census Bureau.
The talk will explain how to group campaign contributors by categories such as State and Occupation, and will show how to plot aggregated statistics as a bar plot and on map. It will also explore whether one candidate received many small contributions or a small number of big contributions. The talk will explore whether these donation distributions had a bigger impact on the election results versus endorsements from well known politicians. Finally, it will explore the effect of an increase in the Latino population and gentrification.
Abstract
American political contests are often dominated by incumbents. Such is the case in New York State's 13th Congressional District. The incumbent, Charles B. Rangel, was first elected to lead the district in 1970. Nicknamed The Lion Of Harlem, Rangel won his seat from another long winning incumbent, Adam Clayton Powell, Jr. aka King of the Cats.
Fast forward to the 21st century and a Latino seeking to unseat Mr. Rangel in 2012, State Senator Adriano D. Espaillat. came within a hair's breadth (1,100 votes). That election was replayed this June, 2014. With power of Python we can analyze campaign contribution data provided by the Federal Election Commission and the United State Census Bureau to find any patterns that might have given the eventual winner the upper hand.
Specifically Python Numpy and pandas give us the power to categorize the raw FEC data and apply various functions (eg. aggregation) to answer questions such as "If grouped by Occupation, which group donated the most to the winning candidate?" and "Did the more generous zip codes have higher voter turnout?"
We can also analyze the demographics of the electorate to figure out if there was a big difference in voter turnout by different racial groups.
In addition, we can plot and visualize our summarized data sets using the matplotlib and basemap toolkits.


This field is required.
Value is too small.
Value is too big.
Input is too short.
Input is too long.
Invalid email address.
Invalid date.
Invalid date time.
Invalid URL.
String contains invalid letter(s).
Used already.
Part Number already exist.
SKU already exist.
Units is invalid.
Not same.
Amount not equal total serials
Item existed.
Not valid format.
Not valid format.
Item existed.
Need input full address (Province, District, Ward and Street)
Price Invalid (greater than max value)
Number of serials greater than product quantity.


7th Heaven
Your Own Personal Heaven
Home
My Account
Gamers Unite
My Site
My Site
My Site
My Site
My Site
My Site
My Site
My Site
My Site
My Site
My Site


Click one of the buttons below to trigger an API call. The API result will be deocrated with the type of notification to show. The notification will be shown automatically.
{{result}}


Home
About Us
Packages
The Kid's Fly Crew
Jenny O'Bryant
Full-Stack Web UI Developer
Tammy Fisher
Full-Stack Web UI Developer
Benedict Schurwanz
Full-Stack Web REACT Developer


Tom Wayson :: Washington DC R&D Center
goo.gl/OYgA4q
@tomwayson/dev-summit-2017-ambitious-arcgis-workshop
Start with a google search
Start at emberobserver.com
A plugin system for ember-cli
ember install some-addon
ember addon my-new-addon


a command-line based blogging platform running on tilde.town
ttbp
stands for "tilde.town blogging platform", the original working name for
this project.
ttbp
runs from the command line, providing a hub for writing personal blog
posts and reading posts written by other users of tilde.town. it's a little bit
like livejournal or dreamwidth or tumblr. you can opt to publish your posts to
a public html file hosted on your tilde page, or keep all your entries private
to the tilde.town server.
to use, run feels
while logged in to tilde.town
(feels
is a tilde.town specific command; if you're running this locally, or on
a different server, run ttbp
from the command line)
no coding or html experience is necessary to get started. just log in to your tilde.town account and enter:
feels
ttbp will ask you a few questions to get you started. after that, writing and reading entries all happen within the program.
that's it!
if you're having trouble getting started, or run into program errors or strange behavior, please send internal tilde.town mail to ~endorphant and i'll try to sort things out!
entries are recorded as plaintext files in your ~/.ttbp/entries directory. you can edit them there directly, or fix old entries, or delete entries.
warning: changing old entries might cause strange things to happen with timestamps. the main program looks at the filename first for setting the date, then the last modified time to sort recent posts. it expects YYYMMDD.txt as the filename; anything else won't show up as a valid entry. yes, this means you can post things out of date order by creating files with any date you want.
<!-- comments -->
to have them show up
in the feed but not render in a browser (but people can still read
them with view-source)when you start your ttbp, you have the option of publishing or not publishing your blog.
if you opt to publish, the program creates a directory ~/.ttbp/www
where it stores all html files it generates, and symlinks this from your
~/public_html
with your chosen blog directory. your blog will also be listed
on the main ttbp page.
if you opt to not publish, your entires will never be accessible from outside
of the tilde.town network; other tilde.town users will still be able to read
your entries through the ttbp interface, or by directly accessing your
~/.ttbp/entries
directory.
if you want to further protect your entries, you can chmod 700
your entries
directory.
you can modify how your blog looks by editing the stylesheet or header and footer files. the program sets you up with basic default. if you break your page somehow, you can force the program to regenerate your configuration by deleting your ~/.ttbp directory entirely. you might want to back up your ~/.ttbp/entries directory before you do this.
alias ttbp="~endorphant/bin/ttbp"
to your .bash_aliases for fewer keystrokesalias ttbp-beta="~endorphant/bin/ttbp-beta"
)these are a few ideas being kicked around, or under active development:
(this section is only relevant if you plan on forking the repo and running an instance of this yourself)
please check out my contributor guidelines on github if you'd like to get involved with development!
if you find any bugs or strange behavior, please message me locally on tildemail or open a github issue and i'll get back to you as soon as i can.
if you're interested in helping with the code, please drop me some tildemail!


AP Top Business News at 10:02 a.m. EST
by EndPlaySaudi Arabia formally starts IPO of oil firm Saudi Aramco
Trump now has opening to pull US out of Paris climate pact
Merkel: 1 million car charging points in Germany by 2030
Trump absent, ASEAN charts path for trade bloc led by China
UAW president taking leave amid corruption probe
Airbnb CEO says company is banning "party houses"
Berkshire Hathaway's third-quarter profits decline 11%
Airbnb bans 'party houses' after California shooting kills 5
Fitbit buy is Google's latest step into gadgetry
Colorado to vote on sports betting, and water could benefit


Checkout Have a coupon? Click here to enter your code Billing Details First Name * Last Name * Company Name Email Address * Phone * Country * Select a country… Åland Islands Afghanistan Albania Algeria Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belau Belgium Belize Benin Bermuda Bhutan Bolivia Bonaire, Saint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory British Virgin Islands Brunei Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos (Keeling) Islands Colombia Comoros Congo (Brazzaville) Congo (Kinshasa) Cook Islands Costa Rica Croatia Cuba CuraÇao Cyprus Czech Republic Denmark Djibouti Dominica Dominican Republic Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island and McDonald Islands Honduras Hong Kong Hungary Iceland India Indonesia Iran Iraq Isle of Man Israel Italy Ivory Coast Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Kuwait Kyrgyzstan Laos Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macao S.A.R., China Macedonia Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands Netherlands Antilles New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Korea Norway Oman Pakistan Palestinian Territory Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Qatar Republic of Ireland Reunion Romania Russia Rwanda São Tomé and Príncipe Saint Barthélemy Saint Helena Saint Kitts and Nevis Saint Lucia Saint Martin (Dutch part) Saint Martin (French part) Saint Pierre and Miquelon Saint Vincent and the Grenadines San Marino Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia/Sandwich Islands South Korea South Sudan Spain Sri Lanka Sudan Suriname Svalbard and Jan Mayen Swaziland Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand Timor-Leste Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu Uganda Ukraine United Arab Emirates United Kingdom (UK) United States (US) Uruguay Uzbekistan Vanuatu Vatican Venezuela Vietnam Wallis and Futuna Western Sahara Western Samoa Yemen Zambia Zimbabwe Address * Town / City * State / County * Postcode / ZIP * Ship to a different address? First Name * Last Name * Company Name Country * Select a country… Åland Islands Afghanistan Albania Algeria Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belau Belgium Belize Benin Bermuda Bhutan Bolivia Bonaire, Saint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory British Virgin Islands Brunei Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos (Keeling) Islands Colombia Comoros Congo (Brazzaville) Congo (Kinshasa) Cook Islands Costa Rica Croatia Cuba CuraÇao Cyprus Czech Republic Denmark Djibouti Dominica Dominican Republic Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island and McDonald Islands Honduras Hong Kong Hungary Iceland India Indonesia Iran Iraq Isle of Man Israel Italy Ivory Coast Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Kuwait Kyrgyzstan Laos Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macao S.A.R., China Macedonia Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands Netherlands Antilles New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Korea Norway Oman Pakistan Palestinian Territory Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Qatar Republic of Ireland Reunion Romania Russia Rwanda São Tomé and Príncipe Saint Barthélemy Saint Helena Saint Kitts and Nevis Saint Lucia Saint Martin (Dutch part) Saint Martin (French part) Saint Pierre and Miquelon Saint Vincent and the Grenadines San Marino Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia/Sandwich Islands South Korea South Sudan Spain Sri Lanka Sudan Suriname Svalbard and Jan Mayen Swaziland Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand Timor-Leste Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu Uganda Ukraine United Arab Emirates United Kingdom (UK) United States (US) Uruguay Uzbekistan Vanuatu Vatican Venezuela Vietnam Wallis and Futuna Western Sahara Western Samoa Yemen Zambia Zimbabwe Address * Town / City * State / County * Postcode / ZIP * Order Notes Your order Product Total Barbell Set × 1 $245.00 Subtotal $245.00 Shipping Shipping costs will be calculated once you have provided your address. Total $245.00 Sorry, it seems that there are no available payment methods for your state. Please contact us if you require assistance or wish to make alternate arrangements. Since your browser does not support JavaScript, or it is disabled, please ensure you click the Update Totals button before placing your order. You may be charged more than the amount stated above if you fail to do so.


{{ partial "head" . }}
{{ partialCached "navigation" . }} {{ partial "header" . }}
{{ block "main" . }} {{ end }}
{{ partialCached "footer" .}} {{ partial "scripts" .}} {{ partial "service-worker" .}}


Recode variables into other variables with optional variable and value label generation and support for dates.
SPSSINC RECODEEX inputvarlist* = outputvarlist*
/RECODES “(input value(s) = recode)* …
(else=COPY** or SYSMIS})”
/OPTIONS STRINGSIZE=n
VALUELABELS=YES** or NO
USEINPUTVALLABELS=NO** or YES
COPYVARIABLELABELS=YES** or NO
SUFFIX=“value”
PREFIX=“value”
/HELP
* Required
** Default
SPSSINC RECODEEX /HELP displays this help and does nothing else.
RECODEEX fatherage motherage = fatheragerc motheragerc
/RECODES "(LO THRU 50=1) (51 thru 75=2) (ELSE=COPY)"
/OPTIONS SUFFIX="rc".
RECODEEX bdate = bdaterc
/RECODES "(LO THRU 1950-12-31=1)(1951-01-01 THRU 1990-12-31=2)".
RECODE duration = durationrc
/RECODES "(LO THRU 10 12:00:00=1)(10 12:00:00 THRU HIGH=2)".
This command extends the built-in RECODE command in several ways.
inputvarlist specifies the variables to be recoded.
They must all have the same type
(numeric, string, a date format, or a time format).
MOYR, WKYR and WKDAY formats are not supported.
outputvarlist specifies an equal number of variables for the results. If STRINGSIZE is specified, the output variables will all be made strings of that length. The type of any existing variables will be changed to match if necessary. If STRINGSIZE is not specified, no variable types will be changed, and any new variables will be numeric. A variable cannot be used as both an input and output variable.
Recode specifications have the same general form as for the RECODE command:
(input-values = output-value)
See the RECODE command for details. Unlike the RECODE commmand, the entire recode value specification must be enclosed in quotes. Input or output string values must also be quoted.
If the variables have a date format, recode values have the form yyyy-mm-dd.
If the values have a time format, recode values have the form hh:mm
, hh:mm:ss.ss
or these forms preceded by days, e.g., 10 08:03
.
STRINGSIZE specifies that the output variables should all be strings of that length (in bytes).
VALUELABELS specifies whether value labels should be created for the output values. They will consist of the input values that are mapped to each output with two caveats: An else specification does not contribute to the labels. If an input value is mapped to more than one output value, it will appear in each corresponding value label even though the RECODE command processes from left to right. If the generated label is too long, it is truncated and … is appended.
USEINPUTVALLABELS specifies whether the created value labels should contain the input values or their value labels. This keyword is ignored if VALUELABELS=NO. If the input value labels are used and a range specification appears, that specification is used as the value label.
If COPYVARIABLELABELS=YES, the variable label, if any, of each input variable will be copied to the output variable. PREFIX and SUFFIX can specify text to be prepended or appended to the label with a separating blank.
© Copyright IBM Corp. 1989, 2014


Wildfires in California
In 2020, California experienced a record number of wildfires, devastating families and destroying homes. Because of its detrimental impact, we decided to create WildfiresAI, a multi-faceted platform that utilizes Machine Learning to tackle the Wildfires.
- Supply government officials with a convenient, quick, and accurate app
- Provide key visualizations of predicted fires to improve resource allocation
- Utilize 4 different Machine Learning models to improve existing methods
With this app, government officials can be assured that wildfires can be easily contained. Our fire detector (object detection), magnitude predictor (fire size), and put-out time estimator (days) make wildfire management seem like a trivial task.
Wildfires in Numbers
Within the US in 2020 alone
Thousand Wildfires
Million Acres Burned
Thousand Structures Damaged
Billion Dollars Lost
Functions
Magnitude Prediction
Predicting the size of a fire in acres using a combined ensemble model with Elastic Net, SVM regressor, and XGBoost regressor
Put-Out Time Estimation
Predicting the time it takes to put out a fire in a given area using a Sequential Neural Network
Features
Localizing Fires
Using a custom-trained Tensorflow2 Object Detection Model, this feature accurately uses bounding boxes to surround a fire with a rectangle with the % chance of confidence.
- Clearly delineates the boundaries of the fire
- Can be integrated into video to show progression
- Provides a confidence estimator of the localization
Predicting Magnitude of Fires
Combining Elastic Net, SVM regressor, and XGB regressor into an ensemble model, this feature provides an accurate prediction of the fire size (burn area) in acres.
- Averages several models' outputs for a final prediction
- Uses GridSearch to tune the best hyperparameters
- Surpasses previous basic regression methods for wildfires
Predicting Fire Put-Out time
Using a Sequential Neural Network, we are able to accurately predict the time it takes to put out a fire in a given area.
- Uses a 3-layered densely connected neural network for predictions
- Model is compiled with the Adam optimizer and Mean-Squared-Error loss
- Makes it more covnenient for fire fighters to allocate resources
Visualizing Predicted Fires
In tandem with our ML models, our visualizations page displays predicted fires using Folium.
- Interactive map that can easily be sorted by various features
- Markers differ in size and color based on fire size
- Allows for accurate resource allocation


Welcome To My Code Quiz
Rules Of The Game
- Time starts as soon as you click on the start button
- You have a total of 75 seconds to answer 5 questions
- Each incorrect answer will subtract time from the timer
- Game is over when all questions have been answered
- Game over when timer reaches 0 secs
- When game is over, enter initials for highscore list


Epic Character Builders Guild
These are archives of the forums of the Epic Character Builders' Guild from BioWare's original NWN website.
| Forum | Description |
|---|---|
| General Discussion | General Discussion for everyone in the Guild |
| Epic Character Builds Also: by author |
Post your epic builds here. The builds must be legal! Look into the rule section. |
| PRC Epic Character Builds Also: by author |
Forums for PRC character builds only, the other one is for standard builds only. |
| Build Request Forum | UPDATE: Been changed to forum for build request. It will keep the information about other classes and remains open to that. |
Guild Description:
Place for all whom want to have their own thread for their own builds which would be indexed in a sense.
Which makes it easier for those who want to make one based on someone else's build to find particular one.
All are welcome to this guild.
Founded: Wednesday, 24 March 2004 01:34AM by
Anuis
Number of members: 2669


Source code for pyhpeimc.wsm.apinfo
#!/usr/bin/env python3
# author: @netmanchris
# -*- coding: utf-8 -*-
"""
This module contains functions for working with the access point information
capabilities of the HPE IMC WSM Module using the RESTful API
"""
# This section imports required libraries
import json
import requests
HEADERS = {'Accept': 'application/json', 'Content-Type':
'application/json', 'Accept-encoding': 'application/json'}
[docs]def get_ap_info_all(auth, url):
"""
function takes no input to RESTFUL call to HP IMC
:param auth: requests auth object #usually auth.creds from auth pyhpeimc.auth.class
:param url: base url of IMC RS interface #usually auth.url from pyhpeimc.auth.authclass
:return: list of dictionaries where each element of the list represents a single wireless access point which has been
discovered in the HPE IMC WSM module
:rtype: list
>>> from pyhpeimc.auth import *
>>> from pyhpeimc.wsm.apinfo import *
>>> auth = IMCAuth("http://", "<IP_ADDRESS>", "8080", "admin", "admin")
>>> all_ap_info = get_ap_info_all(auth.creds, auth.url)
>>> assert type(all_ap_info) is list
>>> assert len(all_ap_info[0]) == 19
>>> assert 'acDevId' in all_ap_info[0]
>>> assert 'acIpAddress' in all_ap_info[0]
>>> assert 'acLabel' in all_ap_info[0]
>>> assert 'apAlias' in all_ap_info[0]
>>> assert 'connectType' in all_ap_info[0]
>>> assert 'hardwareVersion' in all_ap_info[0]
>>> assert 'ipAddress' in all_ap_info[0]
>>> assert 'isFit' in all_ap_info[0]
>>> assert 'label' in all_ap_info[0]
>>> assert 'location' in all_ap_info[0]
>>> assert 'macAddress' in all_ap_info[0]
>>> assert 'onlineClientCount' in all_ap_info[0]
>>> assert 'onlineStatus' in all_ap_info[0]
>>> assert 'serialId' in all_ap_info[0]
>>> assert 'softwareVersion' in all_ap_info[0]
>>> assert 'ssids' in all_ap_info[0]
>>> assert 'status' in all_ap_info[0]
>>> assert 'type' in all_ap_info[0]
>>> assert 'sysName' in all_ap_info[0]
"""
get_ap_info_all_url = "/imcrs/wlan/apInfo/queryApBasicInfo"
f_url = url + get_ap_info_all_url
r = requests.get(f_url, auth=auth,
headers=HEADERS) # creates the URL using the payload variable as the contents
# print(r.status_code)
try:
if r.status_code == 200:
if len(r.text) > 0:
return json.loads(r.text)['apBasicInfo']
except requests.exceptions.RequestException as e:
return "Error:\n" + str(e) + " get_ap_info_all: An Error has occured"
[docs]def get_ap_info(ipaddress, auth, url):
"""
function takes input of ipaddress to RESTFUL call to HP IMC
:param ipaddress: The current IP address of the Access Point at time of query.
:param auth: requests auth object #usually auth.creds from auth pyhpeimc.auth.class
:param url: base url of IMC RS interface #usually auth.url from pyhpeimc.auth.authclass
:return: Dictionary object with the details of the target access point
:rtype: dict
>>> from pyhpeimc.auth import *
>>> from pyhpeimc.wsm.apinfo import *
>>> auth = IMCAuth("http://", "<IP_ADDRESS>", "8080", "admin", "admin")
>>> ap_info = get_ap_info('<IP_ADDRESS>',auth.creds, auth.url)
>>> assert type(ap_info) is dict
>>> assert len(ap_info) == 20
>>> assert 'acDevId' in ap_info
>>> assert 'acIpAddress' in ap_info
>>> assert 'acLabel' in ap_info
>>> assert 'apAlias' in ap_info
>>> assert 'connectType' in ap_info
>>> assert 'hardwareVersion' in ap_info
>>> assert 'ipAddress' in ap_info
>>> assert 'isFit' in ap_info
>>> assert 'label' in ap_info
>>> assert 'location' in ap_info
>>> assert 'locationList' in ap_info
>>> assert 'macAddress' in ap_info
>>> assert 'onlineClientCount' in ap_info
>>> assert 'serialId' in ap_info
>>> assert 'softwareVersion' in ap_info
>>> assert 'ssids' in ap_info
>>> assert 'status' in ap_info
>>> assert 'sysName' in ap_info
>>> assert 'type' in ap_info
"""
get_ap_info_url = "/imcrs/wlan/apInfo/queryApBasicInfoByCondition?ipAddress=" + str(ipaddress)
f_url = url + get_ap_info_url
r = requests.get(f_url, auth=auth,
headers=HEADERS) # creates the URL using the payload variable as the contents
# print(r.status_code)
try:
if r.status_code == 200:
if len(r.text) > 0:
return json.loads(r.text)['apBasicInfo']
except requests.exceptions.RequestException as e:
return "Error:\n" + str(e) + " get_ap_info_all: An Error has occured"


{% extends "base.html" %} {% block title %}
Medieval catalogues > SECULAR INSTITUTIONS: Secular Colleges > Eton College > Bequest by John French, 29 April 1457
{% endif %}3 identified entries found.
All data was derived from the List of Identifications by Professor Richard Sharpe.
{% if not printing %}
A key to codes used in the List is available (opens in new tab).{% endif %}


Testing relations between integer views
[Programming integer actors]
Enumerations | |
| enum | Gecode::Int::RelTest { Gecode::Int::RT_FALSE = 0, Gecode::Int::RT_MAYBE = 1, Gecode::Int::RT_TRUE = 2 } |
| Result of testing relation. More... | |
Functions | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_eq_bnd (View x, View y) |
| Test whether views x and y are equal (use bounds information). | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_eq_dom (View x, View y) |
| Test whether views x and y are equal (use full domain information). | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_eq_bnd (View x, int n) |
| Test whether view x and integer n are equal (use bounds information). | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_eq_dom (View x, int n) |
| Test whether view x and integer n are equal (use full domain information). | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_nq_bnd (View x, View y) |
| Test whether views x and y are different (use bounds information). | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_nq_dom (View x, View y) |
| Test whether views x and y are different (use full domain information). | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_nq_bnd (View x, int n) |
| Test whether view x and integer n are different (use bounds information). | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_nq_dom (View x, int n) |
| Test whether view x and integer n are different (use full domain information). | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_lq (View x, View y) |
| Test whether view x is less or equal than view y. | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_lq (View x, int n) |
| Test whether view x is less or equal than integer n. | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_le (View x, View y) |
| Test whether view x is less than view y. | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_le (View x, int n) |
| Test whether view x is less than integer n. | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_gq (View x, View y) |
| Test whether view x is greater or equal than view y. | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_gq (View x, int n) |
| Test whether view x is greater or equal than integer n. | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_gr (View x, View y) |
| Test whether view x is greater than view y. | |
| template<class View> | |
| RelTest | Gecode::Int::rtest_gr (View x, int n) |
| Test whether view x is greater than integer n. |
Enumeration Type Documentation
| enum Gecode::Int::RelTest |
Function Documentation
template<class View>
| RelTest Gecode::Int::rtest_eq_bnd | ( | View | x, | |
| View | y | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_eq_dom | ( | View | x, | |
| View | y | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_eq_bnd | ( | View | x, | |
| int | n | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_eq_dom | ( | View | x, | |
| int | n | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_nq_bnd | ( | View | x, | |
| View | y | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_nq_dom | ( | View | x, | |
| View | y | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_nq_bnd | ( | View | x, | |
| int | n | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_nq_dom | ( | View | x, | |
| int | n | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_lq | ( | View | x, | |
| View | y | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_lq | ( | View | x, | |
| int | n | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_le | ( | View | x, | |
| View | y | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_le | ( | View | x, | |
| int | n | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_gq | ( | View | x, | |
| View | y | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_gq | ( | View | x, | |
| int | n | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_gr | ( | View | x, | |
| View | y | |||
| ) | [inline] |
template<class View>
| RelTest Gecode::Int::rtest_gr | ( | View | x, | |
| int | n | |||
| ) | [inline] |


This application is designed to view violations in an easy and convenient way. It aggregates information on violations with same stacktraces and provides some basic statistics.
If you want to analyze StrictMode violations of your application you need to do some extra steps. Detailed step-by-step instructions can be found in this tutorial. You may want to consult wiki if you have more questions.
In case you want to quickly test what this application is capable of you can install StrictMode Violator application. You will be able to make as many violations as possible and view them using this application - StrictMove Viewer.


*** User 2017-05-05 22:11:00.048 ***
22:11:00.048 [info] Disabling blocking sync...
*** User 2017-05-05 22:11:00.054 ***
22:11:00.054 [info] Configured peer_service_manager partisan_default_peer_service_manager on node 'node-1@MacBook-Pro-de-Anne-France'
*** User 2017-05-05 22:11:01.800 ***
22:11:01.800 [info] Enabling membership...
*** User 2017-05-05 22:11:01.801 ***
22:11:01.801 [info] Disabling blocking sync...
*** User 2017-05-05 22:11:01.809 ***
22:11:01.809 [info] Configured peer_service_manager partisan_default_peer_service_manager on node 'node-2@MacBook-Pro-de-Anne-France'
*** User 2017-05-05 22:11:03.352 ***
22:11:03.352 [info] Enabling membership...
*** User 2017-05-05 22:11:03.353 ***
22:11:03.353 [info] Disabling blocking sync...
*** User 2017-05-05 22:11:03.359 ***
22:11:03.358 [info] Configured peer_service_manager partisan_default_peer_service_manager on node 'node-3@MacBook-Pro-de-Anne-France'
*** User 2017-05-05 22:11:03.751 ***
Joining node: 'node-3@MacBook-Pro-de-Anne-France' to 'runner@MacBook-Pro-de-Anne-France' at port 54026
*** User 2017-05-05 22:11:03.751 ***
Joining issued: 'node-3@MacBook-Pro-de-Anne-France' to 'runner@MacBook-Pro-de-Anne-France' at port 54026
*** User 2017-05-05 22:11:03.752 ***
Joining node: 'node-2@MacBook-Pro-de-Anne-France' to 'runner@MacBook-Pro-de-Anne-France' at port 54011
*** User 2017-05-05 22:11:03.753 ***
Joining issued: 'node-2@MacBook-Pro-de-Anne-France' to 'runner@MacBook-Pro-de-Anne-France' at port 54011
*** User 2017-05-05 22:11:03.753 ***
Joining node: 'node-1@MacBook-Pro-de-Anne-France' to 'runner@MacBook-Pro-de-Anne-France' at port 53999
*** User 2017-05-05 22:11:03.754 ***
Joining issued: 'node-1@MacBook-Pro-de-Anne-France' to 'runner@MacBook-Pro-de-Anne-France' at port 53999
*** User 2017-05-05 22:11:03.815 ***
Waiting for join to complete with manager: partisan_default_peer_service_manager
*** User 2017-05-05 22:11:03.816 ***
Finished.
*** CT 2017-05-05 22:11:03.816 *** COVER INFO
Adding nodes to cover test: ['runner@MacBook-Pro-de-Anne-France']
*** CT 2017-05-05 22:11:03.826 *** COVER INFO
Successfully added nodes to cover test: []
*** User 2017-05-05 22:11:03.826 ***
Case finished: sql_join_contracted_latency_test
*** User 2017-05-05 22:11:10.882 ***
22:11:10.882 [info] Application lasp exited with reason: stopped
*** User 2017-05-05 22:11:10.884 ***
22:11:10.884 [info] Application partisan exited with reason: stopped
=== Ended at 2017-05-05 22:11:10
=== successfully completed test case
=== Returned value: ok
Test run history
| Top level test index


There's going to be relevant info here about the app / developers / contact /etc.
Give us your email and we'll send you a message on how to retrieve your account.
Set Reminder Time:


« CSS « CSS Reference
The outline
CSS property is a shorthand property for setting one or more of the individual outline properties
outline-style
,
outline-width
and
outline-color
in a single rule. In most cases the use of this shortcut is preferable and more convenient.
Outlines differ from borders in the following ways:
visual
,
interactive
In browsers previous to Gecko 1.8 (Firefox 1.5) a similar effect can be achieved using Mozilla CSS Extension
-moz-outline
.
outline: [ <outline-width> || <outline-style> || <outline-color> ] | inherit
One, two or three values, given in arbitrary order:
medium
is used if absent. See
outline-width
. none
is used if absent. See
outline-style
. invert
. Since Gecko 1.9 (Firefox 3), the value of the element's color
property (foreground color) is used. See
outline-color
.outline: solid; | outline: dashed red; | outline: dotted 1px; | outline: ridge thick violet; | outline: custom 5px;
/* two identical declarations */ :link:hover { outline: 1px solid #000 } :link:hover { outline: solid black 1px }
| Feature | Chrome | Firefox (Gecko) | Internet Explorer | Opera | Safari (WebKit) |
|---|---|---|---|---|---|
| Basic support | 1.0 | 1.5 (1.8) | 8.0 | 7.0 | 1.2 (125) |
| Feature | Android | Firefox Mobile (Gecko) | IE Phone | Opera Mobile | Safari Mobile |
|---|---|---|---|---|---|
| Basic support | 1.0 | 1.0 (1.8) | 8.0 | 6.0 | 3.1 |