Simple http file server that supports files and directories
A simple HTTP static file server
A simple http file server
A simple http file server that also allows PUT and DELETE operations
A simple zero-configuration command-line http server
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Rush plugin for generic HTTP cloud build cache
Node.js implementation of a proxy server (think Squid) with support for SSL, authentication, upstream proxy chaining, and protocol tunneling.
Simple http server for developers of apps with client side routing
Simple, pluggable, zero-dependency, GraphQL over HTTP spec compliant server, client and audit suite.
file downloading using client-side javascript
Zero-dependency, HTTP/1 safe, simple, GraphQL over Server-Sent Events Protocol server and client
Node.js CORS middleware
Simple, EventEmitter API for WebSockets (browser)
A light-weight module that brings Fetch API to node.js
Simple pub/sub messaging for the web
Coherent, zero-dependency, lazy, simple, GraphQL over WebSocket Protocol compliant server and client
LiveReload JS client - auto reload browser on changes
Simplest way to make http get requests. Supports HTTPS, redirects, gzip/deflate, streams in < 100 lines.
Returns a `stream.Readable` from a URI string
A simple service worker used for the static template in sandpack, allowing users to develop websites like they would locally in the browser.
Tiny LiveReload server, background-friendly
An HTTP(s) proxy `http.Agent` implementation for HTTP
TypeScript client library for the Mistral AI API
httphere is a very small and simple ruby command-line HTTP file server.
Pasu is a simple HTTP Server for serving (and uploading) Files.
a simple file http server by pure ruby code.
Very simple http server following https://practicingruby.com/articles/implementing-an-http-file-server?u=2c59db4496 as a guide
Simple HTTP server which allows transpiling HAML files through HTTP request using Ruby implementation
Ferver is a super, simple ruby gem to serve files over http; useful as a basic file server to quickly share files on your local network.
Hstatic is a simple HTTP server for your static files. It's designed for launching it from anywhere in your filesystem tree. It features a nice directory listing and automatic publishing of your index.html files
Torquebox (http://www.torquebox.org) is a JBoss Application Server that will run your Rack and Rails apps in JRuby. Torquebox provides a number of additional functionality that you might find useful, such as messaging, background services, and scheduled tasks. Configuring those is incredibly easy, since they all rely on simple YAML file configs. This CLI application simplifies that further by lettnig you generate your applications and application templates with simple command line executions.
+js-rails-routes+ is a utility for generating JavaScript equivalents to the +<route>_path+ functions provided by {Ruby on Rails}[https://github.com/rails/rails]. This allows you to do very similar things in your {+ejs+}[https://rubygems.org/gems/ejs/] JavaScript templates as you would in your +erb+ ruby templates. You can move html rendering to the client and keep it looking very similar to how it would look on the server. For example, if you have a model +Item+ and a simple route to list all the items, a link to that items page (using an explicit +a+ anchor tag instead of the Rails +link_to+) would look the same in either an +erb+ file or an +ejs+ file: <a href="<%= items_path() %>">List all Items</a> This gem was originally developed as part of the {MVCoffee}[http://mvcoffee.org] suite of tools, and integrates strongly with the {mvcoffee.js}[https://github.com/kirkbowers/mvcoffee] CoffeeScript MVC framework.
# Excel to Code [](https://travis-ci.org/tamc/excel_to_code) excel_to_c - roughly translate some Excel files into C. excel_to_ruby - roughly translate some Excel files into Ruby. This allows spreadsheets to be: 1. Embedded in other programs, such as web servers, or optimisers 2. Without depending on any Microsoft code For example, running [these commands](examples/simple/compile.sh) turns [this spreadsheet](examples/simple/simple.xlsx) into [this Ruby code](examples/simple/ruby/simple.rb) or [this C code](examples/simple/c/simple.c). # Install Requires Ruby. Install by: gem install excel_to_code # Run To just have a go: excel_to_c <excel_file_name> This will produce a file called excelspreadsheet.c For a more complex spreadsheet: excel_to_c --compile --run-tests --settable <name of input worksheet> --prune-except <name of output worksheet> <excel file name> See the full list of options: excel_to_c --help # Gotchas, limitations and bugs 0. No custom functions, no macros for generating results 1. Results are cached. So you must call reset(), then set values, then read values. 2. It must be possible to replace INDIRECT and OFFSET formula with standard references at compile time (e.g., INDIRECT("A"&"1") is fine, INDIRECT(userInput&"3") is not. 3. Doesn't implement all functions. [See which functions are implemented](docs/Which_functions_are_implemented.md). 4. Doesn't implement references that involve range unions and lists (but does implement standard ranges) 5. Sometimes gives cells as being empty, when excel would give the cell as having a numeric value of zero 6. The generated C version does not multithread and will give bad results if you try. 7. The generated code uses floating point, rather than fully precise arithmetic, so results can differ slightly. 8. The generated code uses the sprintf approach to rounding (even-odd) rather than excel's 0.5 rounds away from zero. 9. Ranges like this: Sheet1!A10:Sheet1!B20 and 3D ranges don't work. Report bugs: <https://github.com/tamc/excel_to_code/issues> # Changelog See [Changes](CHANGES.md). # License See [License](LICENSE.md) # Hacking Source code: <https://github.com/tamc/excel_to_code> Documentation: * [Installing from source](docs/installing_from_source.md) * [Structure of this project](docs/structure_of_this_project.md) * [How does the calculation work](docs/how_does_the_calculation_work.md) * [How to fix parsing errors](docs/How_to_fix_parsing_errors.md) * [How to implement a new Excel function](docs/How_to_add_a_missing_function.md) Some notes on how Excel works under the hood: * [The Excel file structure](docs/implementation/excel_file_structure.md) * [Relationships](docs/implementation/relationships.md) * [Workbooks](docs/implementation/workbook.md) * [Worksheets](docs/implementation/worksheets.md) * [Cells](docs/implementation/cell.md) * [Tables](docs/implementation/tables.md) * [Shared Strings](docs/implementation/shared_strings.md) * [Array formulae](docs/implementation/array_formulae.md)
+drupalcluster+ is a command line tool to quickly deploy a Drupal hosting cluster of a scalable amount [2..5] of virtual webservers. !! AWS identity is required for this script !! Your AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY should be either environment variables, or set in ~/.aws/credentials. The configuration file contains additional details for the cluster, including an ssh KeyName that's needed to access the servers. The KeyName defaults to 'Drupal', easiest if it's precreated. $HOME/.drc/drupalcluster.conf This is a demo version only, builds Drupal on HTTP connection. Don't use it seriously. Especially, don't post personal/sensitive data on your Drupal site. ==== Commands create name -- Creates a Drupal hosting cluster check [name] -- Checks the status of creation/deletion delete name -- Deletes permanently the given cluster test name|url -- Sends a simple HTTP GET to the URL (of the given cluster) attack instance -- Permanently terminates the given server instance list -- Lists the recently created/deleted clusters. ----------------------- *** Please contribute to add rspec's ***
Log2json lets you read, filter and send logs as JSON objects via Unix pipes. It is inspired by Logstash, and is meant to be compatible with it at the JSON event/record level so that it can easily work with Kibana. Reading logs is done via a shell script(eg, `tail`) running in its own process. You then configure(see the `syslog2json` or the `nginxlog2json` script for examples) and run your filters in Ruby using the `Log2Json` module and its contained helper classes. `Log2Json` reads from stdin the logs(one log record per line), parses the log lines into JSON records, and then serializes and writes the records to stdout, which then can be piped to another process for processing or sending it to somewhere else. Currently, Log2json ships with a `tail-log` script that can be run as the input process. It's the same as using the Linux `tail` utility with the `-v -F` options except that it also tracks the positions(as the numbers of lines read from the beginning of the files) in a few files in the file system so that if the input process is interrupted, it can continue reading from where it left off next time if the files had been followed. This feature is similar to the sincedb feature in Logstash's file input. Note: If you don't need the tracking feature(ie, you are fine with always tailling from the end of file with `-v -F -n0`), then you can just use the `tail` utility that comes with your Linux distribution.(Or more specifically, the `tail` from the GNU coreutils). Other versions of the `tail` utility may also work, but are not tested. The input protocol expected by Log2json is very simple and documented in the source code. ** The `tail-log` script uses a patched version of `tail` from the GNU coreutils package. A binary of the `tail` utility compiled for Ubuntu 12.04 LTS is included with the Log2json gem. If the binary doesn't work for your distribution, then you'll need to get GNU coreutils-8.13, apply the patch(it can be found in the src/ directory of the installed gem), and then replace the bin/tail binary in the directory of the installed gem with your version of the binary. ** P.S. If you know of a way to configure and compile ONLY the tail program in coreutils, please let me know! The reason I'm not building tail post gem installation is that it takes too long to configure && make because that actually builds every utilties in coreutils. For shipping logs to Redis, there's the `lines2redis` script that can be used as the output process in the pipe. For shipping logs from Redis to ElasticSearch, Log2json provides a `redis2es` script. Finally here's an example of Log2json in action: From a client machine: tail-log /var/log/{sys,mail}log /var/log/{kern,auth}.log | syslog2json | queue=jsonlogs \ flush_size=20 \ flush_interval=30 \ lines2redis host.to.redis.server 6379 0 # use redis DB 0 On the Redis server: redis_queue=jsonlogs redis2es host.to.es.server Resources that help writing log2json filters: - look at log2json.rb source and example filters - http://grokdebug.herokuapp.com/ - http://www.ruby-doc.org/stdlib-1.9.3/libdoc/date/rdoc/DateTime.html#method-i-strftime
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.