Date: Thu, 28 Mar 2024 07:00:42 -0400 (EDT) Message-ID: <280872710.27453.1711623642581@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_27452_1512573744.1711623642581" ------=_Part_27452_1512573744.1711623642581 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This document is a guide to getting up and running with Fedora a= s quickly as possible.
If you are looking for scripted deployments, please take a look at Fedor= a's deployment tooling= .
Java 11
java -v= ersion openjdk version "11.0.5" 2019-10-15 OpenJDK Runtime Environment (build 11.0.5+10-post-Ubuntu-0ubuntu1.1) OpenJDK 64-Bit Server VM (build 11.0.5+10-post-Ubuntu-0ubuntu1.1, mixed mod= e, sharing)
There are two primary ways of deploying Fedora. The first, One-Click Run= , is an easy way to get Fedora running to test out the basic features. The = second, Servlet Container Install<= /a>, is the approach to be used in production installations.
If you'd like to run using docker you can simply install docker and then= run the following command:
For the latest bleeding edge development:
docker run -p8080:8080 --name=3Dfcrepo fcrepo/fcrepo
For a particular version:
docker run -p8080:8080 --name=3Dfcrepo fcrepo/fcrepo:6.0.0-beta-1
For all the available docker configuration options for fcrepo see the fcre=
po-docker README.
Alternatively, instead of deploying Fedora via the "one-click run", the =
Fedora web-application can be installed by dropping the WAR file into a ser=
vlet 3 container, such as Tomcat 9 or Jetty 9.
For details on installing Fedora to those containers, see the Deployment guide.
Once Fedora is running,