![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
momijizukamori2023-07-24 07:49 pm
Entry tags:
momijizukamori2023-07-24 07:49 pmnew canary server
For 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.
foxfirefey2012-03-28 07:35 pmEntry tags:
Enabling beta features on your hack
So, if you're looking to test/develop with the beta journal jquery or the upcoming update page, you are going to need to set the BETA_FEATURES hash in your hack like so:
You can then turn things on/off for individual accounts at: [YOUR_HACK_URL]/betafeatures
%LJ::BETA_FEATURES = (
"journaljquery" => {
start_time => 0,
end_time => "Inf",
},
"updatepage" => {
start_time => 0,
end_time => "Inf",
},
);You can then turn things on/off for individual accounts at: [YOUR_HACK_URL]/betafeatures
New JS implementation on Journals // jQuery Code Guidelines
We just released a beta-test of the jQuery implementation on journals. You can turn it on by going to the Dreamwidth Beta page.
You can test even if you're not a dev-type, but please don't spread this link around too widely just yet. There's still a lot left unimplemented (most notably quick reply), and until the most widely-used user-facing bits are done, it's going to seem pretty broken.
(I'd rather not have random people who don't see the warning in this entry come away with the impression that we all just broke / are planning to break Dreamwidth).
When things are ready to go public, we will be setting up a public beta procedure, and post in the appropriate locations. For now, please if you go turn on beta, expect only comment moderation and deletion to work :)
You'll probably want to save the link so you can go turn it off at will.
For developers, I've put up on the wiki some instructions for putting future features in beta.
There's a lot of ways to set up code in jQuery; here are some things that have been working for me. Putting up for discussion; I'd like to start setting up guidelines to make it easier to get started quickly, soon.
( thoughts on standardizing jQuery implementation )
You can test even if you're not a dev-type, but please don't spread this link around too widely just yet. There's still a lot left unimplemented (most notably quick reply), and until the most widely-used user-facing bits are done, it's going to seem pretty broken.
(I'd rather not have random people who don't see the warning in this entry come away with the impression that we all just broke / are planning to break Dreamwidth).
When things are ready to go public, we will be setting up a public beta procedure, and post in the appropriate locations. For now, please if you go turn on beta, expect only comment moderation and deletion to work :)
You'll probably want to save the link so you can go turn it off at will.
For developers, I've put up on the wiki some instructions for putting future features in beta.
There's a lot of ways to set up code in jQuery; here are some things that have been working for me. Putting up for discussion; I'd like to start setting up guidelines to make it easier to get started quickly, soon.
( thoughts on standardizing jQuery implementation )