Date: Fri, 29 Mar 2024 14:41:40 +0000 (UTC) Message-ID: <1124639726.8109.1711723300468@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8108_2136817185.1711723300467" ------=_Part_8108_2136817185.1711723300467 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
As of Registry v1.0.0, if you would like to publish mostly static conten=
t (such as policy documents or help information) with the look and feel of =
Registry, you may do so by placing these documents in /local/Vie=
w/Pages/public
. Each document should end with the extension
Once uploaded, documents are accessible without authentication at <=
code>http[s]://yourserver/registry/pages/public/file=
name, with or without the .ctp
extension.
Do not use this mechanism for accessing the Registry database. Only pres= ent public, generally static information, otherwise you risk compromising R= egistry security and exposing restricted information.
If you need to work with Registry content, you most likely need to write a Registry Plugin= a>.
As of Registry v3.2.0, images or any other static content may also be se=
rved from the /local
directory, by placing these files in =
;/local/webroot/resources
. Make sure any files you upload ther=
e are readable by the web server user (e.g. apache).
Once uploaded, files are accessible without authentication at&n=
bsp;http[s]://yourserver/registry/local-resour=
ces/filename
, and can be used anywhere, including Registry co=
ntent such as mostly static documents (described above), Themes, or Service=
Logos.