---
title: "FAQ | Parity docs"
description: "Short answers to the questions people ask first about Parity, from PHP on the laptop to Oracle, HTTPS and CI."
url: https://parity.apps.wayne.edu/docs/faq.html
llms: https://parity.apps.wayne.edu/llms.txt
generator: Squire agent-ready
---

# FAQ [#](https://parity.apps.wayne.edu/docs/faq.html#faq)

Short answers, with a link to the long one where there is one.

## Do I need PHP or Composer on my computer? [#](https://parity.apps.wayne.edu/docs/faq.html#do-i-need-php-or-composer-on-my-computer)

No. PHP, Apache and the extensions come from Citadel's image, inside the container. Composer runs where your `build.sh` runs it, inside the build, as on Citadel.

## Is this the same as Squire? [#](https://parity.apps.wayne.edu/docs/faq.html#is-this-the-same-as-squire)

No, and they work together. Squire gets the app onto Citadel (`build.sh`, `deployments/`, `release.sh`). Parity runs Citadel on your computer, and runs those same files the way Citadel does. Parity used to be Squire's parity kit: [Coming from Squire](https://parity.apps.wayne.edu/docs/guides/from-squire.html).

## Does my app have to use the WELD stack? [#](https://parity.apps.wayne.edu/docs/faq.html#does-my-app-have-to-use-the-weld-stack)

No. Parity depends on nothing in the stack. Any PHP app that runs on Citadel can use it, from a 2009 folder of PHP files to a current Laravel app.

## Why not just use the official PHP image? [#](https://parity.apps.wayne.edu/docs/faq.html#why-not-just-use-the-official-php-image)

Because Citadel does not. Citadel's image has its own users, modules, extensions, Oracle client and entrypoint, and its own `php.ini`. An app that works on the official image can still fail on Citadel. So Parity runs Citadel's own image, byte for byte, and nothing else. When Citadel has not published a download for a tag yet, Parity says so rather than run a look-alike ([Citadel's images](https://parity.apps.wayne.edu/docs/guides/images.html#when-citadel-has-not-published-an-image-yet)).

## Can I connect to Oracle or Banner? [#](https://parity.apps.wayne.edu/docs/faq.html#can-i-connect-to-oracle-or-banner)

Not with Parity's help. Parity ships no connectors, no credentials and no data. Citadel's image includes the Oracle client, so code that uses oci8 loads, but a local copy may point only at a test database its data owner approves, never production, and never real student or employee data on a laptop (FERPA).

## How do I sign in locally? [#](https://parity.apps.wayne.edu/docs/faq.html#how-do-i-sign-in-locally)

Set `sign_in` to `fake` in `parity.json` to use SESAME's fake driver, which signs you in as `fake_user` (`jdoe` unless you say otherwise) without CAS. Parity puts the settings in the app container's environment and never touches your `.env`. `cas` is for an app that must talk to the real CAS: it needs a wayne.edu `server_name` pointed at 127.0.0.1 in your hosts file and `"https": true`, so Parity serves https for `server_name` on 127.0.0.1:8443. [Sign-in](https://parity.apps.wayne.edu/docs/reference/parity-json.html#sign-in) has the details.

## How do I run a queue worker or a scheduled job? [#](https://parity.apps.wayne.edu/docs/faq.html#how-do-i-run-a-queue-worker-or-a-scheduled-job)

The way Citadel does: with a [cron entry](https://parity.apps.wayne.edu/docs/reference/parity-json.html#cron-entries). Citadel has no worker service, so a Laravel app runs `php artisan schedule:run` every minute and drains its queue from the scheduler. `parity init` proposes that entry when the app schedules anything.

## How do I build the front end? [#](https://parity.apps.wayne.edu/docs/faq.html#how-do-i-build-the-front-end)

Citadel's images carry Node (22 in `8.5r3`), so build in the app container, as the user who owns the code, the way a deployment script would on Citadel:

```text
parity shell --user citadel sh -c 'npm ci && npm run build'
```

The built files land in your folder and Apache serves them on the next request. Vite's dev server and hot reload are not part of Citadel, so run `npm run dev` on your own computer if you want them.

## Can my app use a second database? [#](https://parity.apps.wayne.edu/docs/faq.html#can-my-app-use-a-second-database)

Not in 1.0. Parity runs one MySQL 5.6, as Citadel gives one database per app. An app that reads a second database (a one-time import from an older app, say) points that connection at a test copy its data owner approves, in its own settings.

## What about HTTPS? [#](https://parity.apps.wayne.edu/docs/faq.html#what-about-https)

Set `"https": true` in `parity.json` and Parity serves https for `server_name` (and `localhost`) on 127.0.0.1:8443, a fixed port, with a leaf from the app's own local CA: one CA per app, name-constrained to the app's names, kept in Parity's per-user config folder, its key never leaving it. The https frontend sends `X-Forwarded-Proto: https`; plain http on `http_port` keeps working. Run `parity trust` once per computer and the browser stops warning (on Linux it prints the sudo commands for your distro, and Firefox always takes a manual import). `parity check` then shows `https.trust`: OK when your user store trusts the CA, a warning with `Fix: parity trust` when it does not, and it never fails, so CI stays green. `parity test` loads the home page over https pinned to the app's CA, which a CI machine never trusts system-wide. [Commands](https://parity.apps.wayne.edu/docs/reference/commands.html#parity-trust) has the details.

## Can I run two apps at once? [#](https://parity.apps.wayne.edu/docs/faq.html#can-i-run-two-apps-at-once)

Yes. Each app is its own compose project (`parity-<name>`). Give them different `http_port` values, and different `database.port` values if both use MySQL.

## Where is my data? [#](https://parity.apps.wayne.edu/docs/faq.html#where-is-my-data)

In a volume of the app's compose project. `parity down` keeps it; `parity down --volumes` empties it.

## Can I use Parity in CI? [#](https://parity.apps.wayne.edu/docs/faq.html#can-i-use-parity-in-ci)

Yes. Without a terminal it prints plain tags, and `--json` on `check`, `status`, `test`, `image list` and `version` is the stable contract. Exit codes are 0 pass, 1 findings or a failed test, 2 cannot run. A runner needs a container engine and Compose, and Citadel's image. Parity's own CI runs on runners that cannot fetch Citadel's image, so it builds a test-only image for its end-to-end job; that image is a fixture for Parity's tests, not something to run your app on.

## Is there an app for people who never open a terminal? [#](https://parity.apps.wayne.edu/docs/faq.html#is-there-an-app-for-people-who-never-open-a-terminal)

After 1.0: a desktop app with the same commands as buttons. Each button names the `parity` command it runs, so the app teaches the command line without asking anyone to use it. It is not released yet; [the desktop app guide](https://parity.apps.wayne.edu/docs/guides/desktop-app.html) shows its screens from the work in progress.

## Where do I report a problem? [#](https://parity.apps.wayne.edu/docs/faq.html#where-do-i-report-a-problem)

In the [repository's issues](https://git.wayne.edu/enterprise-apps/parity/-/issues) on git.wayne.edu. Include the output of `parity check --plain` and `parity version`.
