OT: how to parse code followed by content_by_lua?

vincent.mc.li · 2014-10-24T06:43:24+00:00

any progress here?Am Mittwoch, 12. November 2014 00:42:46 UTC+1 schrieb agentzh:Hello! On Tue, Nov 11, 2014 at 5:17 AM, Jurgen Weber wrote: > any more...

OT: how to parse code followed by content_by_lua?

vincent.mc.li

Hi,

I am attempting to write a PHP code to parse nginx configuration file, display it in browser and change it in browser, sort of GUI for nginx configuration. it seems not so hard to do but i have no idea how to parse the directive like below

content_by_lua '
      blabla
          blabla
            blabla
      blabla
';

my intention is to use content_by_lua as PHP array key and value as content quoted in the single quote that is crossing multiple lines. when i output it, I also prefer to preserve the space indentation. anyone has idea to approach it?

agentzh

Hello!

On Thu, Oct 23, 2014 at 3:43 PM,  vincent.mc.li wrote:
> I am attempting to write a PHP code to parse nginx configuration file,
> display it in browser and change it in browser, sort of GUI for nginx
> configuration. it seems not so hard to do but i have no idea how to parse
> the directive like below
>
> content_by_lua '
>       blabla
>           blabla
>             blabla
>       blabla
> ';
>

I don't really write PHP. But I think the following regex to match the
single-quoted strings should be sufficient: /'(?:\\.|[^'])*'/ (The //
are just regex delimiters as in Perl).

Hope this helps.

Regards,
-agentzh

vincent.mc.li

On Thursday, October 23, 2014 5:29:46 PM UTC-7, agentzh wrote:

Hello!

On Thu, Oct 23, 2014 at 3:43 PM, vincent.mc.li wrote:
> I am attempting to write a PHP code to parse nginx configuration file,
> display it in browser and change it in browser, sort of GUI for nginx
> configuration. it seems not so hard to do but i have no idea how to parse
> the directive like below
>
> content_by_lua '
> blabla
> blabla
> blabla
> blabla
> ';
>

I don't really write PHP. But I think the following regex to match the
single-quoted strings should be sufficient: /'(?:\\.|[^'])*'/ (The //
are just regex delimiters as in Perl).

Thanks for the prompt reply, I actually don't write PHP thus not sure how to do it. I know a little Perl better than PHP :). Perl can read one paragraph at a time, but I find no easy way to do it in PHP. well anyway this off topic and I will look for some PHP help somewhere else. thanks.

Hope this helps.

Regards,
-agentzh

lordnynex

Hello,

Here is a perl Regexp::Grammar that is capable of parsing nginx config files. You will likely need an addition for *_by_lua directives, but I have not tested. https://gist.github.com/lordnynex/1a568e54b5d1af38f549

On Thu, Oct 23, 2014 at 7:50 PM, <vincen...@gmail.com> wrote:

On Thursday, October 23, 2014 5:29:46 PM UTC-7, agentzh wrote:
Hello!

On Thu, Oct 23, 2014 at 3:43 PM, vincent.mc.li wrote:
> I am attempting to write a PHP code to parse nginx configuration file,
> display it in browser and change it in browser, sort of GUI for nginx
> configuration. it seems not so hard to do but i have no idea how to parse
> the directive like below
>
> content_by_lua '
> blabla
> blabla
> blabla
> blabla
> ';
>

I don't really write PHP. But I think the following regex to match the
single-quoted strings should be sufficient: /'(?:\\.|[^'])*'/ (The //
are just regex delimiters as in Perl).

Thanks for the prompt reply, I actually don't write PHP thus not sure how to do it. I know a little Perl better than PHP :). Perl can read one paragraph at a time, but I find no easy way to do it in PHP. well anyway this off topic and I will look for some PHP help somewhere else. thanks.

Hope this helps.

Regards,
-agentzh

.

vincent.mc.li

On Friday, October 24, 2014 1:28:52 PM UTC-7, Lord Nynex wrote:

Hello,

Here is a perl Regexp::Grammar that is capable of parsing nginx config files. You will likely need an addition for *_by_lua directives, but I have not tested. https://gist.github.com/lordnynex/1a568e54b5d1af38f549

thanks, I already have a PHP script parsing nginx config properly, just the hit the wall when dealing with *_by_lua. I will just use the *_by_lua_file as workaround.