Nextcloud apps add server-side features such as calendars, external storage connectors, workflows, or sign-in controls after the base server is running. Installing one through the app catalog is a normal administrator task when a site needs a feature that is not shipped or enabled by default.
The web Apps page and the occ app:install command use the same app store backing when the app store is enabled. The CLI path fits production maintenance because it runs as the web-server user, leaves a terminal record, and does not depend on an active admin browser session.
Run occ from the Nextcloud web root as the web-server account, commonly www-data on Debian and Ubuntu package-style installs. Use the app ID from the app store URL or the Apps page, and install only apps compatible with the running Nextcloud release; forcing an incompatible app can break background jobs, UI pages, or future upgrades.
Related: How to disable a Nextcloud app
$ cd /var/www/nextcloud
Use the directory that contains occ if your server is installed somewhere else.
Related: How to run Nextcloud occ commands
For the Calendar app, the display name is Calendar and the app ID is calendar.
$ sudo -E -u www-data php occ app:install calendar calendar 6.5.0 installed calendar enabled
app:install downloads the app and enables it by default. Use --keep-disabled before the app ID only when the app should be staged but not activated yet.
Use --force only after checking the app release notes and compatibility notes. It ignores the Nextcloud version requirement for the app.
$ sudo -E -u www-data php occ app:list --enabled Enabled: - activity: 7.0.0 - appstore: 1.0.0 - calendar: 6.5.0 ##### snipped #####
For other app types, use the equivalent app menu entry or admin settings page. Some apps become active immediately after installation, while others require app-specific setup before users see a new menu entry.