In our previous blog post, we discussed the WebXPRT 5 source code and how to contact us to request free access to the server setup package. In this post, we’ll answer the two most common questions about code access. The first question is, “How do I create a local instance of WebXPRT?” The second is, “What can I do with it?” Warning: this one gets a bit technical.
How to create a local WebXPRT 5 instance
After we receive your request for access, we’ll send you a secure link to the current WebXPRT 5 server package, which contains all the necessary source files and server setup instructions. To follow the server setup instructions, you’ll need a system to use as a server, and you’ll need to be proficient with Apache, PHP, and MySQL configuration. WebXPRT 5 uses a XAMPP for Windows (cross-platform, Apache, MariaDB, PHP, and Perl) setup on the server system, which includes Apache 2.4.58 (Win64), OpenSSL 3.1.3, and PHP 8.2.12. Please note that while the instructions focus on setting up a XAMPP stack, it is also possible to set up an instance by using a LAMP or WAMP stack.
The instructions include a step-by-step methodology for setting up the server. If you are familiar with XAMPP stack configuration, the setup and configuration process should take about two to three hours, depending on whether your XAMPP-related extensions and libraries are current. If those are not current, you might want to consider updating them to current versions or just plan on a somewhat longer installation process.
What you can do with a local WebXPRT 5 instance
We let you set up their own WebXPRT 5 instances for purposes of review, internal testing, or experimentation.
One use example is internal testing in an OEM lab. Some labs use WebXPRT to conduct extensive performance testing on pre-production gear or components, and the testers very carefully avoid any scenarios where hardware or test information could leave the lab. Even though we have our own strict policies about how we handle the small amount of data that WebXPRT gathers from tests, a local WebXPRT 5 instance provides those labs with an extra layer of security for sensitive tests.
Because benchmarking requires a consistent product that enables valid comparisons over time, we do ask that users publish results only from tests that they run on WebXPRT.com. In addition, while we allow people to download the source, we reserve the right to control both derivative works and which products can use the name “WebXPRT.” That way, when people see WebXPRT scores in tech press articles or vendor marketing materials, they can be confident that they can compare those results to the results they get from running their tests on WebXPRT.com.
If you have any questions about using the WebXPRT 5 source code, let us know!
Justin
