Sha256: b5b346da1531597e24f9b3ba01f1a75222361efdd423d4752d66e703eb42dd70
Contents?: true
Size: 1.38 KB
Versions: 8
Compression:
Stored size: 1.38 KB
Contents
########################
# RackServer rack interface
#
# using Rack with Plezi poses some limitations...:
#
# 1. only the first service (and all it's virtual hosts) will be running.
# (only the first `listen` call and all it's related `host` calls)
#
# 2. there is NO WebSockets support for Rack apps.
#
# 3. this WILL BREAKE any streaming / asynchronous methods calls that use the Plezi events engine.
#
# 4. Plezi parameters and file uploads are different then Rack - HTML Form code might be incompatible!
# This MIGHT BREAKE YOUR CODE! (changing this requires Plezi to re-parse the HTML, and costs in performance).
#
# also, all Plezi server specific configuration will be ignored.
#
# on the other hand, there is an upside:
#
# 1. you can choose a well tested server written in C that might (or might not) bring a performance boost.
#
# 2. you have better control over Middleware then you could have with Plezi.
# ("wait", you might say, "there is no Middleware in Plezi!"... "Ahhh", I will answer, "so much to discover...")
working_dir = ::File.expand_path(Dir.pwd)
app_path = ::File.expand_path(File.join(".."), __FILE__)
app_file_name = app_path.split(/[\\\/]/).last + ".rb"
# # make sure plezi doesn't set up sockets nor starts the event cycle.
PLEZI_ON_RACK = true
#load the Plezi application file
Dir.chdir app_path
require File.join(app_path, app_file_name)
Dir.chdir working_dir
run Plezi
Version data entries
8 entries across 8 versions & 1 rubygems