-
Notifications
You must be signed in to change notification settings - Fork 396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add MARTI staging dice server properties #2685
Add MARTI staging dice server properties #2685
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2685 +/- ##
===========================================
+ Coverage 20.2% 20.2% +<.01%
Complexity 5755 5755
===========================================
Files 816 816
Lines 73780 73780
Branches 12321 12321
===========================================
+ Hits 14907 14909 +2
Misses 56735 56735
+ Partials 2138 2136 -2
Continue to review full report at Codecov.
|
I suggest
|
@panther2 Thanks for the naming suggestion.
This will require a code change as we currently hard-code the "Internal Dice Server" to be the last item in the list. However, I don't think it would be too difficult to give the internal server a custom order in the list so that we can force the beta servers to appear after it. Let me see how that works out. |
@ssoloff As discussed in triplea-game/tripleawarclub.org#16 , I'd appreciate, if this PR would change the domain to not run into any issues later this year |
@RoiEXLab Yeah, I was thinking the same thing. Might as well do it now. 😄 |
The order
would be fine, too, in case it is easier. |
903769d
to
a085673
Compare
@panther2 Sounds good. After looking at the code, it would take a bit more work than I first thought in order to keep the code clean. Not too difficult, but if it's not necessary, I don't want to make the change "just because." If we start getting complaints from users, we can always re-order the list then. |
# name to display to the user | ||
name=dice.tripleawarclub.org (experimental BETA) | ||
# dice server host | ||
host=www.tripleawarclub.org |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, we probably want to avoid this domain
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Just so this isn't being missed accidentally, you know when you think about everything else but not this small thing 😄 )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in 7ed87cf.
The MARTI staging server has been moved to the Any thoughts about changing the label displayed in the UI to |
@ron-murhammer Do you have any objections to including the staging server entry in the dice server list for general usage? In this PR's current state, the dice server list will appear as
|
@ssoloff Will the use of the staging server require a new e-mail address registration? |
@panther2 AFAIK users do indeed need to reregister themselves |
Off topic but could someone please bump the stable to .7634 which is what all bots use please. @ssoloff @RoiEXLab @DanVanAtta |
@ron-murhammer Bumping... Note that after the latest commit, the dice server list will now appear as
Please advise if you have any objections to including the MARTI staging server in the list or, if no objection, if you have any recommendations for improving the label. I'd like to get this out so the QA team can use the staging server in real play. That should give us confidence to promote it into production so we can start fixing the open MARTI issues. |
@ssoloff Looks fine to me. |
Thanks, @ron-murhammer. Going to squash and merge this now. |
In support of #2603.
The new MARTI code has been deployed to the staging server at
http://www.tripleawarclub.org/dice-staging/
. Before promoting this code to production, I would like to have some volunteers use it for an extended period of time. I thought the easiest way to do this would be to add a new entry to the dice server dropdown on the PBEM/PBF configuration screen. Once merged, I would make an announcement on the forum asking for testing help.This PR adds a new dice server entry named
dice.tripleawarclub.org (BETA)
that points to the MARTI staging server. The new entry will appear after the existing MARTI entry but before the internal dice server entry.However, I'm not sure of the following:
(BETA)
label sufficient to distinguish the two versions of MARTI? Is there a better term? Should there be more "noise" in the label to make sure users realize it is a beta server (e.g.(***BETA***)
)?