PacOS variables let you reuse values across fields and change configuration without editing every place where a value is used. They can represent fixed values, values generated by JavaScript, or settings that change with the active variable collection.

Variables are available in fields that support them. These fields are marked with a variables icon, and variables are written inside double curly braces, for example {{base_url}}.

When developing or testing an application, the service it depends on may be unavailable, expensive to use, or difficult to put into a particular state. A mock server lets you return controlled responses instead. The awkward part is often managing those mocks: editing configuration, switching scenarios and making sure everyone on the team is using the same setup.

PacOS includes a Mock Server plugin based on WireMock. It adds a graphical interface for working with mock definitions and supports REST and SOAP services. Install it during PacOS setup or later from the in-app App Store.

When an application runs in containers, checking a log can mean finding the right container, opening a shell, locating the file and running a command. That is manageable for someone comfortable with the terminal, but it is an unnecessary hurdle for teammates who only need to inspect an error or follow what happens during a test.

G-Logger is a PacOS plugin for opening and working with log files in the browser. You can install it during PacOS setup or later from the in-app App Store.

Test environments often contain several databases used by developers, testers, and application teams. Giving everyone access can mean installing a database client, configuring connections, and keeping those tools up to date on individual machines.

The PacOS Database plugin offers another option: configure database connections in PacOS and access them through its browser-based interface. If PacOS can reach databases running in other containers or elsewhere on the network, it can provide a single place to connect to them—without requiring every team member to install a separate database client.

When a development environment contains multiple containers, files are often scattered across services: application logs, configuration, test fixtures and generated artifacts.

Routine tasks such as retrieving a log, replacing a configuration file or unpacking test data can mean finding the right container and running docker exec, docker cp or shell commands.

PacOS provides a browser-based alternative. Mount the directories you want to work with into the PacOS container, then access them from the Explorer plugin.