new canary server
Oct. 24th, 2022 11:12 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
kareilaFor those who haven't seen it, I just posted about the new canary server in ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
dw_beta. Although it's technically a beta feature, I also wanted to mention it here since it's a feature that will be mostly used by developers to test how their code behaves on the live site.
Right now, the people who can deploy to canary are (I believe) the same people who can merge code changes - so me,![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
mark, alierak, momijizukamori. It's not an automatic process, at least not yet; it has to be kicked off by hand, and it doesn't manage everything - any database or text string changes still have to be applied by running the update-db and texttool scripts, and those changes will affect both canary and stable servers, since they both use the main database.
Right now the only way to be notified when a canary deploy happens is to monitor the #commits channel on our Discord server. I'll try to remember to post here if a canary deploy happens that looks like it will take a while to migrate to the stable server. At the moment, canary and stable are identical.
If you have any questions or comments about how the canary impacts our development workflow, please share them here!
If you have any questions or comments about how turning on the canary impacts your use of the site, please share those on thedw_beta post I linked above.
Cool? Cool.
dw_beta. Although it's technically a beta feature, I also wanted to mention it here since it's a feature that will be mostly used by developers to test how their code behaves on the live site.Right now, the people who can deploy to canary are (I believe) the same people who can merge code changes - so me,
mark, alierak, momijizukamori. It's not an automatic process, at least not yet; it has to be kicked off by hand, and it doesn't manage everything - any database or text string changes still have to be applied by running the update-db and texttool scripts, and those changes will affect both canary and stable servers, since they both use the main database.Right now the only way to be notified when a canary deploy happens is to monitor the #commits channel on our Discord server. I'll try to remember to post here if a canary deploy happens that looks like it will take a while to migrate to the stable server. At the moment, canary and stable are identical.
If you have any questions or comments about how the canary impacts our development workflow, please share them here!
If you have any questions or comments about how turning on the canary impacts your use of the site, please share those on the
dw_beta post I linked above.Cool? Cool.