It basically works very smoothly. More specific:
- nice and stable
- .htm pages display fine
- .pht files with single-line lua statements embedded in HTML work fine
- .lua files seems to be executed
- .pht files display fine
- new features is a matter of writing HTML/PHT and uploading. No reboot required! Great for prototyping.
What I would like having improved:
- .html files lead to a PANIC reset, both .htm and .html should be accepted
- multiline Lua code is not working now. It's listed on the elua web as a feature, and is used in the example.pht. Probably a bug.
- larger print output (>256 bytes) of an embedded Lua lines leads to a PANIC reset.
- when .lua page is requested it seesm to be executed, but results are not printed to the serial console, as expected. Returned page to the browser is empy.
- when embedded Lua is faulty in browser is printed :>>> Invalid Lua code <<< 1. Please add the line that was faulty both in the browser and console.- provide some debugging in the serial console, like http request. Now testing more or less a shot in the dark.
- if file exists, but NOT .lua or .htm or .html, display the content in the browser. Great to check log files, if you have any.
The list of improvements seems longer than the „like” list. Don’t let this discourage you, is my enthusiasm on the usability of this code for "real world" web based applications. The combination of HTML and LUA is "golden" for that. The pro’s outweigh the cons easily.
Adamjp has done excellent work here, thanks for that!
For reference my updated index.pht and the browser screen it produces.