I have already implemented a couple of months ago and it works as it should: http://wyday.com/wybuild/help/limit-updates.php. However is it possible take it a step further and only allow certain pkeys (i.e. the testers) to access certain updates before allowing them to be downloaded and installed in production?
However is it possible take it a step further and only allow certain pkeys (i.e. the testers) to access certain updates before allowing them to be downloaded and installed in production?
Yes, just modify your server-side code to only allow certain tester's pkeys. If you're using LimeLM you can use the feature values to mark which testers are allowed to access the pre-release updates.
Would you be able to post or email me a simple example? I understand what needs to be done and I do use LimeLM but I am not understand how I should exactly implement this. I would need to know the versions that I did not want to release to the public (this I believe I would update in the script every update?) and then I would have to check a feature for that particular user via their pkey, correct? What would I need to return in order to silently fail the update check for a normal user without them knowing i.e. they are given the message that they are up-to-date?
Well, a good place to start is the "PHP/limit-updates" folder in the web API pack. Also, see this article: SaaS and time-limited licensing.
Almost everything you want is in that code and the article. the only difference is that instead of having an "update_expires" feature value you'll have something like "is_beta_user" feature value.
Then it's simply a matter of conditionally delivering the beta *.wys vs. the production *.wys:
if ($isTestUser){ // Deliver the "test/%file%"}else{ // Deliver the "production/%file%"}Does that make sense?
That's exactly what I needed. Thanks.