Last updated: December 29, 2018
Joget isn’t designed to be used as-is right out of the box. Instead, you use Joget as a platform to build something on top of. The end product that you build on top of Joget is referred to as a Joget App.
Joget is available as a free download from the official Joget site.
Go to the download page. Select the edition you wish to download.
There are two versions available, Community and Enterprise, and each version is available for Windows and Linux, with the Linux version capable of being installed on Mac OS X as well.
Installation of Joget varies depending on the operating system of the server where you’re installing the software.
The Windows installer is an executable installation wizard — just double-click and follow the wizard.
Installation on Linux is completed via the command line and it’s recommended that you install Joget using Docker.
Finally, installation on a Mac involves installing the dependencies first — Java and MySQL — followed by extraction of the Linux Joget bundle, execution of the included Apache Tomcat server, and finally setting up the database via a web-based interface.
Yes. However, the company that develops the Joget application does so independently and markets the Enterprise version of the application as commercial software.
What that means is that you are free to grab a copy of the community edition, dive right into the code, and use it for free.
However, development of the software is completed in-house by Joget, unlike other well-known open-source projects that are developed by the community of developer users.
Apps in Joget are created using a combination of forms, data lists, and HTML content.
The content is presented in what is referred to as a userview.
Finally, Joget Apps are built by combining these components and stringing them into a series of UI screens that describe a work process.
For instance, a simple expense report app would include a form to fill out, which would then be walked through an approval process consisting of multiple review steps.
Yes. However, it is not an automatic process.
Upgrading involves deletion of a few key files and the replacement of those files with the updated versions.
Prior to doing that, you’ll need to shut down Apache Tomcat and Joget.
In addition, it is recommended that you upgrade a development copy of Joget before attempting to upgrade the production version.