-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[vagrant] use fedora 26 #540
Conversation
gateway/bin/apicast
Outdated
@@ -82,7 +82,9 @@ _LUA_ | |||
$bin = $lua_file; | |||
} | |||
|
|||
my @resty_args = (); | |||
my $nginx = $ENV{TEST_NGINX_BINARY} || $ENV{APICAST_OPENRESTY_BINARY} || 'openresty'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason why TEST_NGINX_BINARY
has preference over APICAST_OPENRESTY_BINARY
?
We are doing the opposite in https://github.com/3scale/apicast/blob/25009f6e3f6029931066aa1c0737d70014a00570/gateway/src/apicast/cli/command/start.lua#L100
Also, it might be worth it to extract the method that selects the binary to a place where the cli and this bin can call it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, will make it the same.
What's the reason to change from centos to fedora? Would be good to include in the commit or the PR description. |
@davidor updated the description. Main reason is outdated profiling toolchain on CentOS. |
* use rsync * install perl dependencies * install redis * use Fedora
so we can run against custom nginx binaries like openresty-asan
JSON::WebToken does not work with OpenSSL 1.1
Change Vagrant box from CentOS to Fedora so we can use the latest tooling.
For development it makes sense to use latest profiling tooling like eBPF, perftools, SystemTap, ...
In centos all those tools are quite ancient because of the 3.11 kernel.