Yes, it's definitely still on the radar. I have a basic version working, but ran into some complexity with Apache and PHP's request model. It doesn't make sense to run EnvKey in every PHP process (since they are per-request), so I'm thinking it needs to cache based on the Apache pid. I'm still working out the best way to accomplish this. Sorry for the delay!
I'm not sure if you're thinking it would be web server dependent, but NGINX is the bigger share of the market. (Ideally it wouldn't matter what the web server is though).
PHP has an execution model that's /really/ bad for per-process requests. Even attempting to grab the parent pid is probably not sufficient as you can have execution contexts with no parent (ex: running php from cron).
I think a caching daemon would be good option for PHP, but it does add a level of complexity.
Another option would be to add EnvKey support to confd (or similar project), and provide config and template files that write the env vars to Apache and Nginx configs, and reload when they change.
Though neither confd or a daemon would work for PHP sites that use a PaaS or shared hosting, which I think is a large percentage of the market for PHP.
Using one of the existing PHP caching solutions (like opcache) might be an option.
I think having a daemon running on the OS that only syncs with an explicit ‘service envkey reload’ would work well.
If running php with nginx (via php-fpm), it’s still common for worker processes to come and go rather frequently. Imo, per-request pricing just won’t work well with php.
I would love to use your product, btw. Congratulations on launch.
> the Dunning–Kruger effect is a cognitive bias wherein persons of low ability suffer from illusory superiority, mistakenly assessing their cognitive ability as greater than it is
I'm not sure I understand the pricing plan - limiting on pages tested seems like a bad way to get customers. I would plan on testing quite a few pages per site and testing those after each commit.
Oh I thought about that, but how are you going to target the lobbyists and bad telcos without harming actual customers on those providers who may very well be against this whole debacle.
Government branches likely have a block of IPs while lobbyists I doubt are registered like that :)
This is exactly what I wanted to know. Last time I tried it it was nice, but without the ability to read PSDs correctly (and not misinterpret things to be all over the place) it's quite useless to me.
