json.lua VS haproxy-auth-request

One option might be to look at the Path of Building “Data” folder. If you need them in another format (e.g. json), it wouldn’t be that hard to write a Lua script to export them in your preferred format (using this json library, for example.

If you don't want to reinvent the wheels, you might want a json encoder to transform data into strings and back. Or bitser if you want better performance and smaller files in exchange for human-readability.

Honestly, I just went with JSON because there's a nice Lua library for it (thank you https://github.com/rxi/json.lua).

I haven't thought about the file format much so far, just the experience of writing in it as if it's the "ground truth". We all seldom open our text files in a hex editor.

JSON https://github.com/rxi/json.lua

Get json.lua from here. Put it in your project directory alongside file1.lua.

Good point. How about this? It allows you to encode/decode Lua values into/from JSON.

I like this json library and tend to use it for save files (also makes them easy to edit by hand while debugging). It gets angry if you use tables with a mix of string and numerical keys, but I'd advise against that anyway. I've also used binser, which is also effective and easy to use.

lua json module can be found from here: https://github.com/rxi/json.lua

I've followed the HAProxy example for Lua-based auth server (https://bl.duesterhus.eu/20180119/).

A lot of the more advanced HAproxy configs for SSO (think Authelia for example) require the use of Lua scripts which would be fine, but the scripts themselves need to reference OTHER scripts. For example haproxy-auth-request requires the use of haproxy-lua-http which needs to reference a JSON library such as json.lua. You usually will see statement such as local http = require("haproxy-lua-http") which indicates our script very explicitly is looking for that other script.