By far the easiest solution is to simply use a third-party's api (i.e. getalby.com) to interact with LN via lnurl protocol, as you won't have to deal with setting up and maintaining your own node. For example, payRequests allow you to call REST api to get encoded ln invoice, as in example below.

The trade offs are, of course, loss of control, placing trust in third-parties, and limitations of their api. Also there are serious limitation with the lnurl specs themselves. For example: there are limited extra data fields you can pass into invoices, such as 'amount', 'comment', 'name', and 'email' - although the spec will no doubt expand its capabilities overtime.

Here's some simple restful uri examples for interacting with getalby lnurl api from a web context - where 'bitanon' is my lnurl address username on getalby: bitanon@getalby.com.