Files
documentation/content/getting-started/command-line-access.md
T
2026-10-20 09:41:46 -06:00

35 lines
1.8 KiB
Markdown

---
title: "Command-line access"
tagline: "What the Enterprise option adds, and how to get advanced tasks done without it."
weight: 40
---
## Standard installations
On a standard Federated Core installation, you do **not** have shell or SSH access to your virtual machine. You manage everything through:
- **Superpanel**, for people, groups, application access, and server-level options.
- **Each application's own admin screens**, for everything inside the app.
This covers nearly everything most organizations need. When a task in these guides needs the command line, it's marked like this:
{{< enterprise >}}
This step uses a command run on the server.
{{< /enterprise >}}
If you see that callout and you don't have Enterprise, contact Federated Computer support and describe what you want done. They can run the command for you.
## Enterprise installations
If Federated Core was installed using the Enterprise option, your designated administrators also have command-line access to the VM. That makes extra tasks possible, such as:
- Running application maintenance tools (for example Nextcloud's `occ`, Discourse's Rails console, or Bookstack's `artisan` commands).
- Bulk imports and exports that are too large for a web upload.
- Inspecting application logs directly.
{{< warning title="Shared responsibility" >}}
Command-line changes can affect updates and backups that Federated Computer performs. Before changing application configuration files or installed versions, check with Federated Computer support so that your change isn't overwritten by the next update.
{{< /warning >}}
Applications on Federated Core run in containers. Commands in these guides that start with an application tool (such as `occ` or `php artisan`) must be run inside that application's container. Federated Computer will tell Enterprise customers how containers are named on their server.