Control
Display unique content on each display
Praisenter allows you to send content to each display independently. The number of displays is dependent on the number of video outputs your system supports.
Praisenter
Specialized presentation software tailored for churches, enabling seamless and engaging presentations for worship services and sermons
Feature rich
Praisenter is packed with features that make presenting content easy and manageable.
Open source
Praisenter is an open source project built by others that share your passion. This means that you can directly contribute to make Praisenter better.
Free
100% free for any use. No registration or sign-up. No trial period or limited feature set. Just download and enjoy!
Before deploying any firmware, you must understand what you are deploying. Let us break the filename into eight discrete tokens:
Fgt - vm64 - kvm - v7.2.3 - f - build1262 - fortinet.out - kvm.qcow2
virt-install
--name fortigate
--ram 2048
--vcpus 1
--disk path=/var/lib/libvirt/images/fgt-vm64-kvm-v7.2.3.f-build1262-fortinet.out.kvm.qcow2,format=qcow2
--import
--os-variant generic
--network network=default
--graphics vnc
On boot, the console will display:
FortiGate-60F (v7.2.3) login:
Default credentials: admin / (no password). Set a password immediately.
Basic configuration using the CLI console:
config system interface
edit port1 # First virtio interface (management)
set mode static
set ip 192.168.1.99 255.255.255.0
set allowaccess ping https ssh http
next
end
config router static
edit 1
set gateway 192.168.1.1
set device port1
next
end Fgt-vm64-kvm-v7.2.3.f-build1262-fortinet.out.kvm.qcow2
This is the specific build number (1262). Fortinet sometimes releases multiple builds of the same version (e.g., v7.2.3 vs v7.2.3.f-build1262). The build number is the source of truth for bug fixes.
QCOW2 stands for QEMU Copy-On-Write version 2. It’s the native disk image format for KVM/QEMU. Key advantages:
Fortinet provides this format because it’s the most efficient for production KVM deployments. Before deploying any firmware, you must understand what
Here’s how to get this image running on a Linux server with KVM.
If you are running this specific build in production, you can optimize performance by editing the libvirt domain XML:
Sample optimization snippet:
<vcpu placement="static" cpuset="4-7">4</vcpu>
<cpu mode="host-passthrough" check="none"/>
<memoryBacking>
<hugepages/>
</memoryBacking>
Praisenter is available on the Windows, Snap, and macOS app stores. Using the app store is the safest way to ensure you get an official version of Praisenter. Praisenter can also be downloaded from the project site under the Releases section, but these builds require more steps to install properly. If you need help with manual install steps, see this article. Praisenter is open source, so if none of the options above work for you, you can always try building Praisenter yourself by cloning the GitHub repo.
Windows 10 x64 or higher
Ubuntu 22.04 x64 or higher
macOS Catalina (10.15) or higher
Before deploying any firmware, you must understand what you are deploying. Let us break the filename into eight discrete tokens:
Fgt - vm64 - kvm - v7.2.3 - f - build1262 - fortinet.out - kvm.qcow2
virt-install
--name fortigate
--ram 2048
--vcpus 1
--disk path=/var/lib/libvirt/images/fgt-vm64-kvm-v7.2.3.f-build1262-fortinet.out.kvm.qcow2,format=qcow2
--import
--os-variant generic
--network network=default
--graphics vnc
On boot, the console will display:
FortiGate-60F (v7.2.3) login:
Default credentials: admin / (no password). Set a password immediately.
Basic configuration using the CLI console:
config system interface
edit port1 # First virtio interface (management)
set mode static
set ip 192.168.1.99 255.255.255.0
set allowaccess ping https ssh http
next
end
config router static
edit 1
set gateway 192.168.1.1
set device port1
next
end
This is the specific build number (1262). Fortinet sometimes releases multiple builds of the same version (e.g., v7.2.3 vs v7.2.3.f-build1262). The build number is the source of truth for bug fixes.
QCOW2 stands for QEMU Copy-On-Write version 2. It’s the native disk image format for KVM/QEMU. Key advantages:
Fortinet provides this format because it’s the most efficient for production KVM deployments.
Here’s how to get this image running on a Linux server with KVM.
If you are running this specific build in production, you can optimize performance by editing the libvirt domain XML:
Sample optimization snippet:
<vcpu placement="static" cpuset="4-7">4</vcpu>
<cpu mode="host-passthrough" check="none"/>
<memoryBacking>
<hugepages/>
</memoryBacking>