Currently Rosetta is specifying the version of the sim to be built when it sends a request to the build server. This just caused a problem where cached metadata was used by Rosetta (due to the recent setup of Cloudflare CDN support) and an older version of the sim was requested, which caused the .htaccess file to be overwritten, which caused phet.colorado.edu to start serving up the previous version of the sim from the "latest" link.
It may be possible to avoid issues like this in the future if it were possible to simply specify that the latest version of the sim be built. @mattpen and I were just discussing this, and he was thinking that if the locale is specified in the build request it could assume the latest version unless otherwise specified. He'll think this over a bit and then, if it seems reasonable, proceed with implementation.
@mattpen - if this is added, please create an issue in the rosetta repo about changing the build requests to use it, and assign it to me.
Currently Rosetta is specifying the version of the sim to be built when it sends a request to the build server. This just caused a problem where cached metadata was used by Rosetta (due to the recent setup of Cloudflare CDN support) and an older version of the sim was requested, which caused the
.htaccessfile to be overwritten, which caused phet.colorado.edu to start serving up the previous version of the sim from the "latest" link.It may be possible to avoid issues like this in the future if it were possible to simply specify that the latest version of the sim be built. @mattpen and I were just discussing this, and he was thinking that if the locale is specified in the build request it could assume the latest version unless otherwise specified. He'll think this over a bit and then, if it seems reasonable, proceed with implementation.
@mattpen - if this is added, please create an issue in the rosetta repo about changing the build requests to use it, and assign it to me.