background preloader

Airbrake

Airbrake

Adeptia Wiki Adeptia is a software vendor that provides Data Integration, Enterprise Application Integration (EAI), Business-to-business (B2B) Integration, and Business Process Management (BPM) software. Adeptia's products are designed to help consolidate databases, build data warehouses, enable Service-oriented architecture (SOA), implement real-time interfaces between systems, integrate with cloud applications and automate business processes. Adeptia products have been used by organizations in various industries including Insurance, Financial Services, Manufacturing, Logistics, Government, Healthcare and Retail. Adeptia is notable for being the most comprehensive “all-in-one” business integration software on the market that combines Data Integration, Enterprise Application Integration, Business-to-Business EDI capability and Business Process Management on a core SOA architecture.[1] History[edit] Products[edit] Adeptia offers the following products: See also[edit] References[edit] External links[edit]

Shipping nginx access logs to LogStash — DevOps & Programming Note: this blog post is a bit outdated. Kibana is now part of Elasticsearch, and a pure JavaScript project, no longer dependent on Ruby. Additionally we now run Elasticsearch version 0.9.11 and LogStash 1.3.3. At Commando.io, we’ve always wanted a web interface to allow us to grep and filter through our nginx access logs in a friendly manner. After researching a bit, we decided to go with LogStash and use Kibana as the web front-end for ElasticSearch. LogsStash is a free and open source tool for managing events and logs. First, let’s setup our centralized log server. The following guide assumes that you are running CentOS 6.4 x64. Centralized Log Server cd $HOME # Add the required prerequisite remi yum repositorysudo rpm —import rpm -Uvh -i ‘0,/enabled=0/s//enabled=1/’ /etc/yum.repos.d/remi.repo # Create LogStash configuration filecd /etcsudo touch logstash.conf Nginx Servers

pilu's web-app-theme at master - GitHub Apache CXF Fathom Mobile Command Center | CrittercismCrittercism Set alert thresholds for proactive notifications Integrated and comprehensive app performance alerting Why it matters: Be proactively identified about issues. Rubular: a Ruby regular expression editor and tester Ajax Wiki Ajax is not a single technology, but a group of technologies. HTML and CSS can be used in combination to mark up and style information. The DOM is accessed with JavaScript to dynamically display, and allow the user to interact with, the information presented. JavaScript and the XMLHttpRequest object provide a method for exchanging data asynchronously between browser and server to avoid full page reloads. In 1996, the iframe tag was introduced by Internet Explorer to load or to fetch content asynchronously. In 1998, Microsoft Outlook Web App team implemented the first component XMLHTTP by client script. Google made a wide deployment of standards-compliant, cross browser Ajax with Gmail (2004) and Google Maps (2005).[6] The term "Ajax" was publicly stated on 18 February 2005 by Jesse James Garrett in an article titled "Ajax: A New Approach to Web Applications", based on techniques used on Google pages.[1] get-ajax-data.js: send-ajax-data.php: jQuery example

Application Monitoring in Realtime - Instrumental Area Criações - Web e Design Blocos em Ruby( lambda, proc, yield e tudo mais) Seguindo a linha do último tutorial de ruby, hoje vamos falar de blocos. Vou tentar explicar de forma resumida e com exemplos o que são blocos e como usar. Lembro a primeira vez que vi um bloco em Ruby fiquei totalmente perdido pois ainda não tinha visto nada com uma sintaxe parecida em outras linguagens ( ex.: { |item| puts item } ). Um bloco é um trecho de código Ruby que deve ser executado: ["daniel","lopes"].each {|item| puts item} # => resultado sera:# => daniel# => lopes No exemplo acima, tenho um array e este array possui o método each. Nosso bloco é formado por chaves que delimitam o inicio e o fim do bloco, um parâmetro ( |item| ) e sentença a ser executada ( puts item ). No exemplo passamos o bloco para o método each e ele executou este bloco várias vezes, também optamos por passar um parâmetro para o bloco, mas podemos passar quantos parâmetros precisarmos. meu_hash = {:nome=>"daniel",:sobrenome=>"lopes"}meu_hash.each {|index,item| puts "chave #{index},valor #{item}"}

Petals ESB rsaikali/django-skwissh SSL checklist for Ruby on Rails Applications | Vinsol Cross posted from darthsid The purpose of SSL is to provide a reasonable level of protection against eavesdropping and man-in-the-middle attacks. Although SSL provides a greater level of security, it introduces a lot of overheads and hence should be used sparingly. Two of the most common places to use SSL is for payment transactions and user registration/login. . b. include SslRequirement c. ssl_required :new, :create if Rails.env.production? d. SslRequirement.disable_ssl_check = true 2. Replace “yourdomain” with your apps domain and “4” with the number of asset hosts required. The above should ensure that you have a proper SSL setup without displaying warnings to the user.

Related: