How can more of us help? I'm a php developer with css/js/vue skills also.

Any luck in bringing support to PHP yet? I know we had chatted a while ago about that being a possibility - was hoping that was still on the radar.

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!

Ah, no worries.

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).

Good to know - as you can see, I don't have a lot of PHP experience.

If anyone knows of a good way to get a PHP process's parent server pid (regardless of what server it's running on), please let me know :)

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).

On linux you can get the master process through posix-getppid (http://php.net/manual/en/function.posix-getppid.php) but this won't work on windows and has the same limitations as above.

Have you thought about having a linux daemon/agent that runs in the background and keeps the ENV in sync?

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.

> Have you thought about having a linux daemon/agent that runs in the background and keeps the ENV in sync?

Yes, though I think it's also important to give developers control of when their config reloads, since surprises here can be dangerous.

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.

-php dev

Read this: https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect

As someone else pointed out, this is more commonly referred to as Imposter Syndrome.

> 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

Don't think that is the same as Imposter Syndrome: https://en.wikipedia.org/wiki/Impostor_syndrome

The Impostor Syndrome is quite the reverse of the Dunning–Kruger effect.

Get out of here with your reasonable requests, this is a DEVELOPER conference, not a design conf... oh - wait.

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.

Why not take it a step further and limit the lobbyists and bad telcos?

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 :)

I'm sure the lobbyists for the music and film industry can be uniquely identified by their IP addresses. You could at least do them.

I would think that the employee would have an idea that their salary would be publicly known before taking the job.

Any idea of how their layer styles are now?

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.

I have to open PSDs that make use of layer styles on a regular basis, so I'd love to pay a much higher price, would it fully support PSDs.

Check out [1]codekit. It watches and automatically compiles your LESS/SASS on save and will even refresh your browser for you.

[1]: http://incident57.com/codekit/