eclipse-sailing-analytics/sailing-analytics
1
0
Fork 0
mirror of https://github.com/eclipse-sailing-analytics/sailing-analytics.git synced 2026-09-16 10:48:47 +00:00
Code Activity

bug6060: admin release notes entry

Browse Source
This commit is contained in:
Axel Uhl
2025-11-21 11:32:34 +01:00
parent 7ef8f62e19
commit 05bb10d299
2 changed files with 22 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
configuration/environments/security-service-master
+1 -1
View File
@@ -20,7 +20,7 @@ ADDITIONAL_JAVA_ARGS="$ADDITIONAL_JAVA_ARGS -Dsecurity.sharedAcrossSubdomainsOf=
#REPLICATE_MASTER_SERVLET_PORT=443
#REPLICATE_MASTER_EXCHANGE_NAME=security_service
# Activate SAP Branding
ADDITIONAL_JAVA_ARGS="$ADDITIONAL_JAVA_ARGS -Dcom.sap.sse.debranding=false"
ADDITIONAL_JAVA_ARGS="$ADDITIONAL_JAVA_ARGS -Dcom.sap.sse.branding=SAP"
# Provide authentication credentials for a user on security-service.sapsailing.com permitted to replicate, either by username/password...
#REPLICATE_MASTER_USERNAME=(user for replicator login on security-service.sapsailing.com server having SERVER:REPLICATE:<server-name> permission)
java/com.sap.sailing.www/release_notes_admin.html
+21
View File
@@ -32,6 +32,27 @@
and install <em>all</em> releases available. For the time being, and for simplicity,
we decided to not require a GitHub access token, which however will cause a rate limit
of 60 release requests per hour per IP address.</li>
<li>Branding is now configurable beyond just switching it on and off. The corresponding
VM argument / system property name has changed from <tt>com.sap.sse.debranding</tt>
with its possible values <tt>true</tt> and <tt>false</tt> to <tt>com.sap.sse.branding</tt>
which can either be left empty to deactivate branding altogether, matching the old
<tt>true</tt> configuration for de-branding the solution, which was also the default,
or you can specify the ID of an existing branding configuration, such as <tt>SAP</tt>.
The command line option for an active SAP branding hence would look like this:
<pre>
-Dcom.sap.sse.branding=SAP
</pre>
and this is to be used only in an SAP context according to SAP's branding rules.
See also <a href="https://brand.sap.com/">https://brand.sap.com/</a> and
<a href="https://wiki.sapsailing.com/wiki/info/landscape/branding-setup.md">our wiki entry on branding configurations</a>.
</li>
<li>The project Wiki can now be viewed publicly, in line with the publication of the underlying
Git repository, at <a href="https://wiki.sapsailing.com">https://wiki.sapsailing.com</a>.
Currently, write access has to be requested at <a href="mailto:support@sapsailing.com">support@sapsailing.com</a>,
but you may also create a <a href="https://github.com/SAP/sailing-analytics/pulls"></a>pull request</a>
for changes you'd like to see appear in the Wiki. We are working on granting committers
write-access through a GitHub OAuth app soon. See also
<a href="https://bugzilla.sapsailing.com/bugzilla/show_bug.cgi?id=6181">bug 6181</a>.
</ul>
<h2 class="articleSubheadline">October 2025</h2>
<ul class="bulletList">