PrestaShop

@webship.co/workspace-prestashop 1.0.7 · github.com/webship/workspace-prestashop · npm

PrestaShop for the Webship Workspace dashboard: a builder that makes a real PrestaShop shop in a container, a console tool for the shops it built, the default accounts, the PrestaShop step pack wired into the workspace's testing setup, and two AI agents that know all of it.

The workspace is container-based (DDEV by default): a PrestaShop project is a row like any other, so the row menus the core draws (start, stop, launch, backup, clone, remove, tests) work on it unchanged.

It is made from the reference platform plugin, @webship.co/workspace-wordpress.

Only the open-source release is built, on the 9.x line. Nothing outside the shop is connected: no account of a vendor, no marketplace, no paid module, no payment method that calls a service, and no e-mail that leaves the shop.

Use it

cd ~/workspace
bash core/scripts/plugins.sh --require github:webship/workspace-prestashop   # npm install into the dashboard
bash core/scripts/plugins.sh --activate prestashop                            # plugins.prestashop in settings.yml
bash core/scripts/plugins.sh --install prestashop                             # commands, functions, args, agents
bash core/scripts/plugins.sh --configure prestashop                           # nothing to configure: it has no settings file

The same four steps are buttons on the dashboard's Settings → Plugins page. --install is idempotent. --uninstall removes what it placed; an agent you edited stays.

The commands land in the sites folders that are in the workspace (dev, test, sandboxes, demos); the agents land in the AI Agents folder (ai-agents/) when the workspace has one, and are installed into ~/.claude/agents from there like any other agent.

It needs a Webship Workspace 1.0.7 or later.

What the package holds

Path	What it is
`commands/cmd-prestashop-project.sh`	The builder, in the Build list as PrestaShop (9.x), installed into every sites folder
`commands/cmd-tools-prestashop-cli.sh`	The console of the shop (`bin/console`) for one project: what the shop is, a command, the cache, the default accounts
`scripts/functions/fun-prestashop.sh`	The bash functions behind both, sourced by bootstrap once installed; the names the core's tools look for (`set_prestashop_users`, `add_prestashop_users`, `cancel_prestashop_users`, `testing_configure_prestashop`)
`scripts/args/arg-prestashop.sh`, `arg-prestashop-cli.sh`	Their argparse; the Build form draws the builder's flags from the first
`testing/site.feature`	The first feature a PrestaShop project gets when testing is set up
`agents/prestashop-site-builder.md`	The agent that builds and maintains PrestaShop shops with these commands
`agents/prestashop-tester.md`	The agent that writes and runs scenarios with the PrestaShop step pack
`src/index.ts`	`register(api)`: what the assistant is told about PrestaShop here
`features/prestashop.feature`	Scenarios for the dashboard's own browser suite

The workspacePlugin block in package.json is the manifest the installer reads.

The commands

Run them from a sites folder. --help is safe on both.

Build a shop

cd ~/workspace/dev
bash cmd-prestashop-project.sh myshop --install --add-users

Flag	What it does
`--version <x>`	The PrestaShop 9 release to download: `latest` (the default: the latest stable 9.x release), or a number such as `9.2.1`
`--install`	Install the shop, with the workspace account as its SuperAdmin
`--add-users`	With `--install`: add the default accounts, an administrator, an employee with a limited profile and two customers
`--demo-catalog <yes\|no>`	With `--install`: the demo catalog of the release (products, categories, customers, orders). `yes` by default; `no` gives an empty shop
`--php-version <x>`	The PHP of the project container (`8.3`)
`--launch`	Open the shop when it is ready

The shop answers at https://myshop.ddev.site, the back office at /admin-workspace. The container tool has no project type for PrestaShop, so the build runs ddev config --project-type=php with the docroot public, Apache (the shop routes its addresses through .htaccess), MariaDB 10.11 and the Node.js of the workspace (24). It reads the release list the project publishes, downloads the archive of the release in the container, checks it against its checksum, unpacks the shop, and installs it with the shop's own command-line installer: SSL on, the domain set to the project's address. The installer is given the container's database values (db / db / db), the same in every project, and nothing personal. A project of the same name is deleted first.

What the build does to keep the shop to itself:

Only the modules of the open-source release are installed. The installer is handed their list. The marketplace, account, hosted checkout, marketing and assistant modules that travel in the downloaded archive stay uninstalled.
No e-mail is sent. The mail method is set to "never send".
The back office has a known folder. The installer gives it a random name; the builder renames it to admin-workspace, and removes the install folder the shop refuses to run with.

An employee and a customer sign in with their e-mail address: the SuperAdmin with the address of the workspace account. The shop asks for a password of 8 characters or more: --install stops before it starts when the workspace account's is shorter.

Work on a shop

bash cmd-tools-prestashop-cli.sh myshop                                  # version, addresses, employees and customers
bash cmd-tools-prestashop-cli.sh myshop --run "list"                     # every command of the console
bash cmd-tools-prestashop-cli.sh myshop --run "prestashop:module:list"
bash cmd-tools-prestashop-cli.sh myshop --clear-cache                    # clear the cache
bash cmd-tools-prestashop-cli.sh myshop --add-users                      # the default accounts
bash cmd-tools-prestashop-cli.sh myshop --cancel-users                   # delete them

The console runs in the environment the shop is served in (prod); --env=dev in a command names another. The tool has no --update: the console of the shop has no command that updates the shop itself. A newer release is a new build.

The default accounts

Account	What it is	Handle in the tests	Signs in to
the workspace account (Workspace Owner)	the SuperAdmin, made by the installer	none: it is never written into a test	the back office
`administrator@example.com` (Shop Admin)	an employee with the SuperAdmin profile	`admin`	the back office
`salesman@example.com` (Sam Salesman)	an employee with the Salesman profile	`salesman`	the back office
`customer@example.com` (Clara Customer)	a customer with one address	`customer`	the shop
`shopper@example.com` (Simon Shopper)	a second customer with one address	`shopper`	the shop

The four default accounts have the password of the workspace's other default lists. They are for local shops and for tests. The administrator is a test account of its own, so the features of the step pack that sign in as admin run on a built shop and the workspace account stays out of every test. The console of the shop makes a SuperAdmin and no other account, so they are made in the container through the shop's own classes, without the browser. bash cmd-tools-add-users.sh myshop prestashop and bash cmd-tools-cancel-users.sh myshop prestashop add and remove the same list.

The Users menu of a project row does not add them: the dashboard reads the user list of a row from the DDEV project type, and a PrestaShop project is a php project, because the container tool has no type for PrestaShop. Use the console tool or the two commands above.

Test a shop

bash cmd-tools-testing.sh myshop                 # webship-js, the step pack, the accounts, a first feature
bash cmd-tools-testing.sh myshop --run           # run the suite in the container
bash cmd-tools-testing.sh myshop --run --path tests/features/site.feature

cmd-tools-testing.sh is the workspace's own. For a PrestaShop project it also adds @webship-js/prestashop-steps to package.json, lists its step definitions in cucumber.js after webship-js's own, writes the folder of the back office (backOffice.folder, overridable with ADMIN_FOLDER) and the two registries of accounts (employees and customers: the handles above, overridable with SHOP_<HANDLE>_EMAIL and SHOP_<HANDLE>_PASSWORD), places tests/features/site.feature when the project has none, and makes sure the default accounts are in the shop. Run it again and it adds what is missing and keeps what you changed.

The agents

Agent	Use it to
`prestashop-site-builder`	Build, maintain or remove a PrestaShop shop with the commands above, in containers only, with the open-source release and nothing connected outside the shop
`prestashop-tester`	Set the testing stack up, look at the shop in the Playwright MCP browser first, write scenarios from the pack's steps and run them; it never creates an account in a suite and never writes a platform name into a step phrase

After --install they are in the AI Agents folder of the dashboard; Install there puts one into ~/.claude/agents, or from the command line:

cd ~/workspace/ai-agents
bash cmd-tools-ai-items.sh prestashop-tester --install

Develop it

npm install     # builds dist/ (TypeScript)
npm run lint
npm test        # the manifest, the commands, the agents, the functions against a scaffolded project