t = { name = "Bob" } function t:sayHello() -- note the 't:' part print("Hello" .. self.name) end t:sayHello() -- "Hello Bob"

lint: @luacheck -q .

-- patch os.getenv to not have existing environment variables interfere local _getenv = os.getenv os.getenv = function() end -- luacheck: ignore finally(function() os.getenv = _getenv -- luacheck: ignore end)

Tip: If you see require('mymodule') it is just an alternative syntax for require 'mymodule' the two perform identically and are interchangeable.

Here is the code from main() using different variables, both work fine:

This is the module, notice how the interface table mymodule is local and is returned on the last line of the module:

It's good practice to keep file loaded by content_by_lua_file at a minimum and place all processing logic into external modules. This allows lua_code_cache to work its magic and simplifies your testing.

output = lustache:render("{{title}} spends {{calc}}", view_model)

Is anyone aware of a lua http lib that supports keepalive?

local http = require "resty.http"
local httpc = http.new()
httpc:connect("127.0.0.1", 9081)
local response, err = httpc:request({
  path = "/proxy" .. ngx.var.request_uri, 
  method = "HEAD",
  headers = ngx.req.get_headers(),
  keepalive_timeout = 60,
  keepalive_pool = 10,
})

non-blocking internal requests

      location /external/ {
        internal;
        set $upstream "";
        rewrite_by_lua_file ./lua/get_external.lua;
        resolver 8.8.8.8;
        proxy_pass $upstream;

-- strip beginning '/' from uri path
ngx.var.upstream = ngx.var.request_uri:sub(2)

set $template_root /usr/local/openresty/nginx/html/templates;

docker-openresty/alpine/Dockerfile.fat

This API function (as well as ngx.location.capture_multi) always buffers the whole response body of the subrequest in memory. Thus, you should use cosockets and streaming processing instead if you have to handle large subrequest responses.

Network I/O operations in user code should only be done through the Nginx Lua API calls as the Nginx event loop may be blocked and performance drop off dramatically otherwise. Disk operations with relatively small amount of data can be done using the standard Lua io library but huge file reading and writing should be avoided wherever possible as they may block the Nginx process significantly. Delegating all network and disk I/O operations to Nginx's subrequests (via the ngx.location.capture method and similar) is strongly recommended for maximum performance.

local LuaSocket = require("socket") client = LuaSocket.connect("example.com", 80) client:send("GET /login.php?login=admin&pass=admin HTTP/1.0\r\nHost: example.com\r\n\r\n") while true do s, status, partial = client:receive('*a') print(s or partial) if status == "closed" then break end end client:close()

ngx.unescape_uri(str)

ngx.log(ngx.STDERR, 'your message here')

print(a .. " World") --> Hello World

header_filter_by_lua 'ngx.header.Foo = "blah"';

access_by_lua ' local res = ngx.location.capture("/auth") if res.status == ngx.HTTP_OK then return end if res.status == ngx.HTTP_FORBIDDEN then ngx.exit(res.status) end ngx.exit(ngx.HTTP_INTERNAL_SERVER_ERROR)

The Lua code cache can be temporarily disabled during development by switching lua_code_cache off

it defaults to /etc/nginx/conf.d/default.conf

resolver 8.8.8.8;

string.sub() Returns a substring (a specified portion of an existing string).

local data = ngx.req.get_body_data()

Terra is a low-level system programming language that is embedded in and meta-programmed by the Lua programming language

I don't know what then, I just remember somehow. Around the same time I install renoise, I also install vim. Then in renoise I go to Help>Show Preferences Folder.... Then I right click on Config.xml, then edit in VIM. Then I /search for showscr or something like that. Change false into true, done. On windows sometimes I'm lazy and I just modify the one shortcut that I use to have --scripting-terminal or something as an argument. Also: if you really do a lot of (re)installs I would advise to back up your Config.xml anyway, just like the KeyBindings.xml, TemplateSong.xrns, etc, it'll save you a lot of time right?