Search by

omnipack / restaurant

GlitchArt

A restaurant on omnibase: the dining room and its layouts (a floor-plan editor, a QR poster per table), meal services and table reservations (availability under a lock, a public form, a management link, ICS), the menu (dishes as omnibase/marketplace products, sections, set menus, EU allergens), orde

Package info

github.com/glitchr-omnisense/omnipack-restaurant

Type:symfony-bundle

pkg:composer/omnipack/restaurant

Statistics

Installs: 2

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

v3.0.0 2026-11-22 08:39 UTC

This package is auto-updated.

Last update: 2026-11-22 14:17:00 UTC


README

A restaurant on omnibase: one bundle per trade, one site per restaurant.

  • The room: rooms, tables, named layouts (tables moved, taken out, joined), a floor-plan editor in the back office (SVG, drag on a snapping grid, turn, duplicate, join), a QR poster per table.
  • Services and reservations: meal services (MealService: days, seatings, table durations, automatic confirmation), opening hours and days off from omnisense/omnibase's OpeningHours, availability reckoned table by table and taken under a symfony/lock, a public form on a model, a management link (move, cancel), an ICS file.
  • The menu: Dish extends omnipack/marketplace's Product (price before VAT, VAT, stock), sections, set menus, the EU allergens of omnisense/omnibase, diets, a filter, a printable menu.
  • Ordering at the table: /t/{token} from the table's QR code, no account; rounds (Ticket) on the table's bill (Session), a dish's options (a cooking, extras); the bill paid from the phone where the site allows it; the waiter called, the bill asked for; symfony/rate-limiter per table.
  • The take-home shop (/traiteur): fresh dishes to cook at home (TakeHome: how it keeps, its use-by days, how to cook it), the cold chain (ColdChain: collected on a slot, brought to the postcodes around, a chilled parcel only when the whole basket travels and keeps, Monday to Wednesday), an order without an account and followed by its link (/suivi/{token}), prepared on the pass.
  • The pass (/service): the floor live, the tickets of every channel in columns, the day's book, dishes run out - polled with omnisense/omnibase's poll controller.
  • The platforms, when omnisense/omnifood is installed: webhooks made tickets and reservations, the pass's answers sent back, the menu pushed, keys typed in the back office.
composer require omnipack/restaurant

The persistence bridge (omnibridge/doctrine or omnibridge/eloquent) is suggested, not required: the site picks one.

Stable releases follow semantic versioning: this installs the latest 3.x, with omnisense/omnibase 7.0 or later on Symfony (omnibridge/symfony) and Doctrine ORM (DoctrineBundle), omnipack/admin and omnipack/marketplace. No minimum-stability setting is needed.

Under Symfony, register the bundle and its pages, then create its tables:

// config/bundles.php
Base\Restaurant\RestaurantBundle::class => ['all' => true],
Omnifood\Bridge\Symfony\OmnifoodBundle::class => ['all' => true],   // only with omnisense/omnifood
# config/routes.yaml
restaurant_controller:
    resource: "@RestaurantBundle/src/Controller/Client"
    type: attribute
bin/console make:migration && bin/console doctrine:migrations:migrate

First use: in the back office, draw a room and its tables, add a meal service and a few dishes; each table's QR poster then opens /t/{token}, its order page. docs/installation.md has the rest.

Documentation: docs/. Tests: vendor/bin/phpunit (no kernel needed).

The order without an account and the bill paid from a phone stand on omnipack/marketplace's quick order, and are loaded only where it exists; what is left is in docs/roadmap.md.

License: MIT since 2026-10-09; earlier versions remain published under LGPL-3.0-or-later.