profile
viewpoint
Jeffrey 'jf' Lim jf Singapore, Singapore Full-stack Problem-Solver

jf/rbenv-gemset 610

KISS yet powerful gem / gemset management for rbenv

jf/chronic 4

"Chronic is a pure Ruby natural language date parser." + improvements, corrections, speedups, and additions

jf/fosx-label 4

Add a text label to your Firefox icons in OS X

jf/jquery-validationEngine2---VE2-- 4

VE2 is a fork of the original jquery validationEngine found at http://www.position-absolute.com/articles/jquery-form-validator-because-form-validation-is-a-mess/.

chuyeow/mongrel 3

Fork of mongrel. Removes Etag generation and mongrel_cluster does rolling restarts. See the stable_1-1 branch.

jf/memcached 3

Ruby interface to the libmemcached C client. The original branch with the original code to set/get items bigger than the 1Mb limit. If you intend to use this functionality, though, it is better to track http://github.com/chuyeow/memcached

jf/chrollusion 2

Collusion for Chrome (and Safari!) — a browser extension that lets you visualize and, optionally, block the invisible websites tracking you, based on Mozilla’s Firefox add-on Collusion <https://github.com/toolness/collusion>.

jf/feather 1

personally-managed copy of the current feather. Call it "feather-stable", or "feather-works"!!! Meant to go in concert with jf/feather-plugins.

jf/feather-plugins 1

"feather-plugins-stable". Maintained, and designed to work in concert with jf/feather.

jf/mini_magick 1

mini_magick, - with my own fixes and patches

issue closedadnanh/webhook

`command-working-directory` is not obeyed

Example:

[
        {
                "id": "runscript",
                "execute-command": "/path/to/script.sh",
                "command-working-directory": "/tmp",
                "pass-environment-to-command": [
                        {
                                "source": "payload",
                                "name": "env1",
                                "envname": "ENV1"
                        },
                        {
                                "source": "payload",
                                "name": "env2",
                                "envname": "ENV2"
                        }
        }
]

script.sh

#!/bin/sh
pwd

In my log, I see the following

[webhook] 2020/09/24 16:09:40 [d92f25] executing /path/to/script.sh (/path/to/script.sh) with arguments ["/path/to/script.sh"] and environment [ENV1=a ENV2=b] using /path/to as cwd
/path/to

This is with the latest version of webhook: 2.7.0

closed time in an hour

jf

issue commentadnanh/webhook

`command-working-directory` is not obeyed

sorry, my bad! I had been editing the wrong hooks.json. Turns out that there is no problem with command-working-directory. 👍

jf

comment created time in an hour

issue openedadnanh/webhook

`command-working-directory` is not obeyed

Example:

[
        {
                "id": "runscript",
                "execute-command": "/path/to/script.sh",
                "command-working-directory": "/tmp",
                "pass-environment-to-command": [
                        {
                                "source": "payload",
                                "name": "env1",
                                "envname": "ENV1"
                        },
                        {
                                "source": "payload",
                                "name": "env2",
                                "envname": "ENV2"
                        }
        }
]

script.sh

#!/bin/sh
pwd

In my log, I see the following

[webhook] 2020/09/24 16:09:40 [d92f25] executing /path/to/script.sh (/path/to/script.sh) with arguments ["/path/to/script.sh"] and environment [ENV1=a ENV2=b] using /path/to as cwd
/path/to

This is with the latest version of webhook: 2.7.0

created time in an hour

issue commenthashicorp/nomad

`nomad job stop` sends `interrupt` signal for docker driver?

Sure. I just had the impression (as I believe most folks would as well) from the docs (https://www.nomadproject.io/docs/job-specification/task#kill_signal) that my tasks would be getting TERM instead of KILL

jf

comment created time in 3 days

push eventjf/nomad

Jeffrey 'jf' Lim

commit sha 84e5907c0f9199530f057da27a6dbbb54cde2c87

drivers/docker/driver.go: change default signal for docker driver to SIGTERM?

view details

push time in 5 days

PR opened hashicorp/nomad

drivers/docker/driver.go: change default signal for docker driver to SIGTERM?

Fixes #8932

NOTE: I'm guessing ideally, the standard messaging in various places (nomad/structs/structs.go, command/alloc_status.go) with text like 'Sent interrupt' might have to change as well, but maybe that can be part of a bigger discussion. For now, I think updating the default from SIGINT to SIGTERM makes sense.

References: https://www.nomadproject.io/docs/job-specification/task#kill_signal, https://docs.docker.com/engine/reference/commandline/stop/

+1 -1

0 comment

1 changed file

pr created time in 5 days

create barnchjf/nomad

branch : fix_docker_stopsignal

created branch time in 5 days

issue openedhashicorp/nomad

`nomad job stop` sends signal interrupt for docker driver?

Nomad version

Nomad v0.13.0-dev (fb170f37a05d712e3046d604c362804c7934cfc9+CHANGES)

Operating system and Environment details

Ubuntu 20.04.1 LTS

Issue

Reproduction steps

Not too sure why nobody has noticed, but it seems like nomad job stop sends a docker task the interrupt signal, as opposed to the expected TERM as per https://www.nomadproject.io/docs/job-specification/task#kill_signal

To confirm this, I basically added debug logging to https://github.com/hashicorp/nomad/blob/943854469db945631e79ccd0f8014cdb1e584963/drivers/docker/handle.go#L127

My debug output for the signal parameter gives interrupt.

My first clue was from my alloc logs, where I see 'Sent interrupt'. The line from nomad job stop is called out below

Time                  Type        Description
2020-09-19T10:50:04Z  Killing     Sent interrupt. Waiting 30s before force killing
2020-09-19T10:50:04Z  Killed      Task successfully killed
2020-09-19T10:50:04Z  Terminated  Exit Code: 1, Exit Message: "Docker container exited with non-zero exit code: 1"
2020-09-19T10:50:02Z  Killing     Sent interrupt. Waiting 30s before force killing                 --> did `nomad job stop` here
2020-09-19T10:45:51Z  Started     Task started by client
2020-09-19T10:45:37Z  Driver      Downloading image
2020-09-19T10:45:37Z  Task Setup  Building Task Directory
2020-09-19T10:45:34Z  Received    Task received by client

Job file (if appropriate)

any standard job file will do

created time in 5 days

issue commenthashicorp/nomad

Non-leader task in taskgroup not being sent interrupt

I am seeing this as well - with the latest Nomad version too (Nomad v0.12.4 (8efaee4ba5e9727ab323aaba2ac91c2d7b572d84)). This issue should not have been closed by the bot. Is anybody looking at this?

djenriquez

comment created time in 6 days

issue commentCircleCI-Public/aws-ecr-orb

Set `tag` dynamically causes failure

Thank you for coming up with this, @toymachiner62 . I didnt even think that we could have a dynamic tag this way!!

I've improved upon this and fixed the way to keep the tag constant between the build and push steps:

      - run:
          name: seed environment
          command: |
            echo $(date +%Y-%m-%d__%H-%M)__$(git log -n1 --format=%h) > IMAGE_TAG
      - aws-ecr/build-and-push-image:
          tag: $(cat IMAGE_TAG)
          ...

This works and gives you a stable tag in the environment. Really all you need is a a stable tag between "Build docker image" and "Push image to Amazon ECR". The format of the tag is entirely up to you, but I like having the datetime + hash reflected

toymachiner62

comment created time in 8 days

issue commentunbit/uwsgi

http-socket does not support Keep-Alive

@jf From the source code: https://github.com/unbit/uwsgi/blob/uwsgi-2.0/plugins/http/http.c#L658

Excellent, thanks! I see it now. On another note, if anybody has any recommendations for another server to check out that has proper http keep-alive support, I'd be glad to hear it.

parasyte

comment created time in 9 days

issue commentunbit/uwsgi

http-socket does not support Keep-Alive

Btw, "http-keepalive" option value is a number which specify timeout (in seconds) after which an inactive connection is closed by server. How can I configure this timeout when I will use "http11-socket"?

@marc1n what is your source for this? I see https://github.com/unbit/uwsgi/issues/2018, which seems to indicate that this is a boolean instead.

parasyte

comment created time in 9 days

pull request commenthashicorp/consul

Add auto-fill for Service.Address with Node.Address

I wonder if the fix is not more complicated than that:

* there might be IPv6/IPv4 addresses in nodes as well, some existing implementations might have chosen some strategies to use ServiceAdress _before_ Node.Address or Node.TaggedAddress[IPv4/v6] and it might break some clients. For instance, we consider the semantics to be very precise (aka, it means this is a virtual IP, not the IP value)

I agree with you that the choice of letting it empty is probably unfortunate, but the change would be very late in the game, what I mean is that some users might take decisions based on the fact this value is present or not.

As mentioned at https://github.com/hashicorp/consul/issues/4599#issuecomment-689611373, I'm not sure what the value of having Service.Address be empty would be.

About choosing to use it the correct version, (Service OR Node), maybe the doc should be lear about what the default strategy should be, but it is probably to the Consul wrappers to implement it.

it would indeed be helpful for the docs to clear about this, yes

For instance, in the implementations of our SDKs, we provide wrappers for that, for example, https://github.com/criteo/consul-templaterb/blob/master/TemplateAPI.md#service_address

tdakkota

comment created time in 15 days

issue commenthashicorp/consul

API: Autofill Service.Address with Node.Address if Service.Address is empty

I agree with you on the initial issue, but I think that many tools are now doing assumptions based on this value being present or not, see my comment: #7782 (comment)

I'm late to this issue but... what tools would these be, and why would they care about it being empty (""?) vs being filled with an actual IP address? I fail to see why having the actual IP address reflected in Service.Address is a problem vs it's current "" value

johncowen

comment created time in 15 days

issue commentdocker/docker.github.io

notes for "Shell form ENTRYPOINT example" need to be cleaned up

Now no external dependencies are needed to play with all combinations of ENTRYPOINT and CMD.

this is great! thanks.

At least the shell form prevents the CMD to be used. A second /bin/sh normally doesn't make sense in the command line, but of course depends on what the entrypoint does with it.

Surely the shell form still does something with the CMD provided in the Dockerfile? That was my point and why I say the documentation isnt really correct.

I you like you could draft a PR to update the table in docker/cli repo.

Thanks. I can. Just not too sure about (as I've said) whether this is a bug in the doc, or if the behaviour has changed.

jf

comment created time in 20 days

issue commentdocker/docker.github.io

notes for "Shell form ENTRYPOINT example" need to be cleaned up

But coming back to what I would like to verify (or else I could have just done the PR to docker/cli myself): is this a bug and the intention of The shell form prevents any CMD or run command line arguments from being used still remains the same... or has that changed? Can you help me with that?

jf

comment created time in 21 days

issue commentdocker/docker.github.io

notes for "Shell form ENTRYPOINT example" need to be cleaned up

(Your echo test, btw, failed because it would have been (breaking up the parameters) run as /bin/sh, -c, echo, /bin/sh,-c, exec_cmd p1_cmd. All of those arguments after echo got passed as arguments to /bin/sh, and not to echo)

jf

comment created time in 21 days

issue commentdocker/docker.github.io

notes for "Shell form ENTRYPOINT example" need to be cleaned up

yeah, I know because I did see the result of docker top... but also because I investigated the process data (not necessary, but just helps to confirm things) in the container. Now the question remains: is this a bug? is it still intended that, according to the doc The shell form prevents any CMD or run command line arguments from being used? Which is it?

jf

comment created time in 21 days

issue commentdocker/docker.github.io

notes for "Shell form ENTRYPOINT example" need to be cleaned up

It's either that the table has to be changed.. or the statement that The shell form prevents any CMD or run command line arguments from being used, ... has to be changed.

@StefanScherer can you confirm which is correct?

jf

comment created time in 21 days

issue commentdocker/docker.github.io

notes for "Shell form ENTRYPOINT example" need to be cleaned up

# docker version
Client: Docker Engine - Community
 Version:           19.03.12
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        48a66213fe
 Built:             Mon Jun 22 15:45:44 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.12
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       48a66213fe
  Built:            Mon Jun 22 15:44:15 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683
jf

comment created time in 21 days

issue commentdocker/docker.github.io

notes for "Shell form ENTRYPOINT example" need to be cleaned up

It's either that the table has to be changed.. or the statement that The shell form prevents any CMD or run command line arguments from being used, ... has to be changed.

FROM ubuntu
ENTRYPOINT top -b
CMD exec_cmd p1_cmd

docker build ... docker run --name test ... docker top test

jf

comment created time in 21 days

fork jf/cli

The Docker CLI

fork in 21 days

issue commentdocker/docker.github.io

notes for "Shell form ENTRYPOINT example" need to be cleaned up

If you only look at the output, how do you verify that echo got run with sh -c echo?

jf

comment created time in 21 days

issue commentdocker/docker.github.io

notes for "Shell form ENTRYPOINT example" need to be cleaned up

My testing for the table shows otherwise. Have you tested it?

jf

comment created time in 21 days

issue openeddocker/docker.github.io

notes for "Shell form ENTRYPOINT example" need to be cleaned up

File: engine/reference/builder.md

These points relate to https://docs.docker.com/engine/reference/builder/#shell-form-entrypoint-example. Several points:

  1. The following Dockerfile does not build:
FROM ubuntu
ENTRYPOINT top -b
CMD --ignored-param1
# docker build -t top .
Sending build context to Docker daemon  70.14kB
Error response from daemon: Dockerfile parse error line 6: Unknown flag: ignored-param1
#
  1. command output conflicts with argument(s?) to docker run in the example given:
$ docker run -it --name test top --ignored-param2

Mem: 1704184K used, 352484K free, 0K shrd, 0K buff, 140621524238337K cached
CPU:   9% usr   2% sys   0% nic  88% idle   0% io   0% irq   0% sirq
Load average: 0.01 0.02 0.05 2/101 7
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
    1     0 root     S     3168   0%   0% /bin/sh -c top -b cmd cmd2
    7     1 root     R     3164   0%   0% top -b

Command gives --ignored-param2, while output uses cmd cmd2. This is besides the fact that the container's output from top does not reveal the command line arguments for both sh and top; you need to use docker top test for that.

  1. The table at https://docs.docker.com/engine/reference/builder/#understand-how-cmd-and-entrypoint-interact needs to be updated. Specifically the ENTRYPOINT exec_entry p1_entry, with CMD exec_cmd p1_cmd entry. I get /bin/sh -c exec_entry p1_entry sh -c exec_cmd p1_cmd

created time in 23 days

PR opened hashicorp/nomad

Fix cmd.Name() for NodeEligibilityCommand

First up, my apologies if this isn't really as vetted as it should be. I'm not entirely certain that this affects its use as called from c.Meta.FlagSet within the same file. What I do know and can tell is that this same string is used for the help output... which gives you misleading text:

# nomad node eligibility
Either the '-enable' or '-disable' flag must be set
For additional help try 'nomad node-eligibility -help'
#

It really should be nomad node eligibility -help instead.

I also see other Name() funcs for other commands that might need fixing, btw. If I can get some confirmation that all of the Name() funcs within command/*.go only affect help text, then I can go about fixing them.

+1 -1

0 comment

1 changed file

pr created time in a month

push eventjf/nomad

Jeffrey 'jf' Lim

commit sha 4f0cfbd7522f1f0cf06e9fdd2d80edab9c57f6d9

Fix cmd.Name() for NodeEligibilityCommand

view details

push time in a month

push eventjf/nomad

Tim Gross

commit sha cc7e4b226b61f9c566232ac8ba08500c71b5ff33

csi: skip unit tests on unsupported platforms (#8033) Some of the unit tests for CSI require platform-specific APIs that aren't available on macOS. We can safely skip these tests.

view details

Mahmood Ali

commit sha c7816081a546bc969005c2fc2cd8ec4e00097b1a

vault: ensure ttl expired tokens are purge If a token is scheduled for revocation expires before we revoke it, ensure that it is marked as purged in raft and is only removed from local vault state if the purge operation succeeds. Prior to this change, we may remove the accessor from local state but not purge it from Raft. This causes unnecessary and churn in the next leadership elections (and until 0.11.2 result in indefinite retries).

view details

Mahmood Ali

commit sha fbc42a8086391c34ac4e43ab37058d354e8d5060

Add `snapshot` helper Effectively Copied from https://github.com/hashicorp/consul/tree/v1.8.0-beta1/snapshot With addition of overall snapshot checksum file

view details

Mahmood Ali

commit sha f4fcc1c02c65e0a72dabea89f812b24a8193eec7

Endpoint for snapshotting server state

view details

Mahmood Ali

commit sha 1bec2425b0b9a8b4352720a7cdb140f6739d7ca1

Add api/ package function to save snapshot

view details

Mahmood Ali

commit sha 845788437b170dfdf4c9940e071a20e25260b4b7

Implement snapshot save CLI

view details

Mahmood Ali

commit sha 73e4bf63ac514d265716123c0aa95e51cc5c930f

implement snapshot inspect CLI

view details

Mahmood Ali

commit sha abda1a1c7adf25a8f3bef2b3862258a46b8c3fbf

always set purgeFunc purgeFunc cannot be nil, so ensure it's set to a no-op function in tests.

view details

Yoan Blanc

commit sha 817eb9788e7f9a94ddc48f97ac20cdf0ed53e732

vendor: pin docker/distribution to v2.7.1 Signed-off-by: Yoan Blanc <yoan@dosimple.ch>

view details

Seth Hoenig

commit sha 051e387d0cd24c612207454cafbb5da4786a3ef5

build: use hashicorp hclfmt We have been using fatih/hclfmt which is long abandoned. Instead, switch to HashiCorp's own hclfmt implementation. There are some trivial changes in behavior around whitespace.

view details

G

commit sha 3f47a67f889f00e378b1fdd61fd11540943226ec

docs: static port incorrectly declared as a string (#8046) static attribute of the port stanza is supposed to be an integer but is incorrectly declared as a string in the example.

view details

Mahmood Ali

commit sha ada9a6a844562eb9e370fa2407eb3a923f8c1db7

volumewatcher: no batcher when disabling When disabling volumewatcher (at the end of a test), avoid starting a new update batcher with its new goroutine.

view details

Mahmood Ali

commit sha 2bdbed0974d2f6e2a5644a5a2bc8a1cda7952f25

refactor: context is first parameter By convention, go functions take `context.Context` as the first argument.

view details

Mahmood Ali

commit sha 4a7f4b22cfc93cd9f3d26ea4e897e1af25a1a09c

fix a trace logline

view details

Mahmood Ali

commit sha 29eca948ad6a863300b1dd0cb93ea8b9f7b49df7

terminate leader goroutines on shutdown Ensure that nomad steps down (and terminate leader goroutines) on shutdown, when the server is the leader. Without this change, `monitorLeadership` may handle `shutdownCh` event and exit early before handling the raft `leaderCh` event and end up leaking leadership goroutines.

view details

Seth Hoenig

commit sha bc72de5d49cbd2d15cfe35821a0532ff05771e3a

Merge pull request #8018 from hashicorp/b-sidecar-task-resources-npe api: canonicalize connect components

view details

Buck Doyle

commit sha b965e6a84bd1613f852ffff8ecfdc050e220ca44

UI: use lazy-loading for Xterm.js (#7964) This updates Xterm.js to 4.6.0, which includes support for reverse-wraparound mode, so we no longer need to use a vendored dependency, which closes #7461. The interface for accessing the buffer that’s used for test assertions changed. With the dependency now accessed conventionally, we can have it load only when it’s needed by an exec popup window, which closes #7516. That saves us ≈60kb compressed in the dependency bundle!

view details

Seth Hoenig

commit sha 41f9ec5643de3e653b31856baf71ac4f9a1deb80

Merge pull request #8044 from hashicorp/d-use-hashi-hclfmt build: use hashicorp hclfmt

view details

Mahmood Ali

commit sha d6c75e301e3701970850ef7f55d8da1733a2da81

cleanup driver eventor goroutines This fixes few cases where driver eventor goroutines are leaked during normal operations, but especially so in tests. This change makes few modifications: First, it switches drivers to use `Context`s to manage shutdown events. Previously, it relied on callers invoking `.Shutdown()` function that is specific to internal drivers only and require casting. Using `Contexts` provide a consistent idiomatic way to manage lifecycle for both internal and external drivers. Also, I discovered few places where we don't clean up a temporary driver instance in the plugin catalog code, where we dispense a driver to inspect and validate the schema config without properly cleaning it up.

view details

Jimmy Merritello

commit sha 9741abefe0a0bfbc961383eb54d689ab8e0db919

Add Carousel Item

view details

push time in a month

create barnchjf/nomad

branch : fix_cmd_name

created branch time in a month

issue openedhashicorp/nomad

systemd unit file in latest (0.12.3-2) nomad package for Ubuntu (focal): should be s/StartLimitInterval/StartLimitIntervalSec/ ?

As per subject, if you install the latest nomad package for Ubuntu (I'm using Focal), the systemd unit file is as follows:

[Unit]
Description=Nomad
Documentation=https://nomadproject.io/docs/
Wants=network-online.target
After=network-online.target

# When using Nomad with Consul it is not necessary to start Consul first. These
# lines start Consul before Nomad as an optimization to avoid Nomad logging
# that Consul is unavailable at startup.
#Wants=consul.service
#After=consul.service

[Service]
ExecReload=/bin/kill -HUP $MAINPID
ExecStart=/usr/bin/nomad agent -config /etc/nomad.d
KillMode=process
KillSignal=SIGINT
LimitNOFILE=65536
LimitNPROC=infinity
Restart=on-failure
RestartSec=2
StartLimitBurst=3
StartLimitInterval=10
TasksMax=infinity
OOMScoreAdjust=-1000

[Install]
WantedBy=multi-user.target

It looks like it should be StartLimitIntervalSec=10 instead of StartLimitInterval=10

created time in a month

pull request commentterraform-providers/terraform-provider-aws

Add `aws_security_group_rules` resource

Progress update please, can this be merged?

I think it looks like this was the intention, but https://github.com/terraform-providers/terraform-provider-aws/pull/9032#issuecomment-639695850 seems to indicate that discussion is being moved to https://discuss.hashicorp.com/t/discussion-of-aws-security-group-rules-for-absolute-management-while-avoiding-cyclical-dependencies/9647

jakauppila

comment created time in a month

pull request commentcloudhead/neovim-fuzzy

Fixed: Open selected files in splits with keybindings

@cloudhead just a ping again. Do you have any issues with this PR?

nannery

comment created time in 2 months

issue commentjf/rbenv-gemset

add an OSI-approved license

I see that "Unlicense" was already stated as the license without this project's approval. Please do not think to speak for rbenv-gemset.

chenrui333

comment created time in 2 months

issue closedjf/rbenv-gemset

Gemset not "hooking" into rbenv version

I'm new to this, so forgive me for some simple mistakes. Following the README hasn't really helped me; I've seen on other issues that there has been some confusion about the README.

When I used a gemset for RVM, I would see it in the ruby version. I would run:

rvm gemset create my_cool_app rvm 2.5.1@my_cool_app

I could also a have a .ruby-version file with the gemset in it like this: 2.5.1@my_cool_app. And it worked perfectly. When I would view my ruby version, it would tell me my version with the gemset.

However, that's not happening with this plugin. I followed the README

I ran rbenv gemset init in my Rails project which created the .rbenv-gemsets file. When I ran rbenv gemset active it showed my gemset correctly. But when I run:

rbenv version in my project, I get this:

2.6.3 (set by /Users/garcia/.rbenv/version)

There is no gemset. It seems like the gemset is there, but it's not doing anything.

Am I wrongly expecting RVM behavior? Is it actually working fine?

Additional Questions

  • Is a .ruby-version file necessary with version and gemset in it?

closed time in 2 months

angarc

pull request commentopenresty/lua-nginx-module

Update/correct phase info for lua_need_request_body

I did it all in the same commit, if that's ok. Figured it's probably better, and a cleaner commit.

jf

comment created time in 2 months

push eventjf/lua-nginx-module

Jeffrey 'jf' Lim

commit sha f8bcc8af21093b306ffc7a98c30916204ee2d8cf

Update/correct phase info for lua_need_request_body

view details

push time in 2 months

issue openedneovim/neovim

Feature request: different-coloured cursor for insert vs normal mode?

I think this will be helpful. If there were some option or way to configure it that would be great.

created time in 2 months

PR opened openresty/lua-nginx-module

Update/correct phase info for lua_need_request_body

as per subject, correct the phase info for lua_need_request_body. I assume this should be rewrite/access/content_by_lua

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchjf/lua-nginx-module

branch : correct_doc,_lua_need_request_body

created branch time in 2 months

fork jf/lua-nginx-module

Embed the Power of Lua into NGINX HTTP servers

https://openresty.org/

fork in 2 months

more