Results for stack-sites

Access any Stack Exchange site (stackoverflow.com, ect.) from Ruby.

Generates a static site from template files with YAML and Liquid. Stack supports template transformation through Markdown, Textile and Less CSS.

SequenceLogo is a tool for drawing sequence logos of motifs. It gets Positional Count Matrices(PCMs) or IUPAC sequences as input and generates png-logos for a motif. Also one can create logo for reverse complement or even generate logos for a whole collection of motifs. Sequence logos are a graphical representation of an amino acid or nucleic acid multiple sequence alignment developed by Tom Schneider and Mike Stephens. Each logo consists of stacks of symbols, one stack for each position in the sequence. The overall height of the stack indicates the sequence conservation at that position, while the height of symbols within the stack indicates the relative frequency of each amino or nucleic acid at that position. In general, a sequence logo provides a richer and more precise description of, for example, a binding site, than would a consensus sequence (see http://weblogo.berkeley.edu/)

If you're building an application that has both online and offline functionality it can be useful to know if the site is really still up (because you can't rely on navigator.onLine). This middleware allows you to poll /online or the path of your choice and return simple text or the result of a block without involving the whole application stack. Meaning, you can poll more frequently without melting your server.

While rails' default error pages are great, they look totally unprofessional for any real site. RuRoh provides a quick and easy way to have nicely rendered error pages generated from your stack during deployment. This allows you to re-use your existing layouts and customize your error pages without having to re-create them on the fly (which could result in further errors). The pages can be generated via capistrano during deploy, or generated during a post-commit hook similar to asset pipeline resources.

Backtrace (Stack traces) are essential information for debugging our applications. However, they only tell us what the program did, but don't tell us what it had (the arguments, local variables...etc.). So it's very often that we'd need to visit each call site, rerun the program, and try to print out the variables. To me, It's like the Google map's navigation only tells us the name of the roads, but not showing us the map along with them. So I hope to solve this problem by adding some additional runtime info to the backtrace, and save us the work to manually look them up.

A Jekyll plugin for address munging — defending email addresses on public sites against bulk harvesters. Stacks five independently-effective techniques (AES-128-GCM encryption, JS conversion, click trigger, CSS-hidden decoy, SVG noscript fallback) so scrapers see ciphertext while humans see a normal mailto link. Drop in a Liquid tag — `{% munge_email "user@example.com" %}` — and the plugin handles encryption at build time, the decoder script, and the fallback markup.

No description provided.