Skip to main content

​
Prerequisites

  • A compatible Ruoom Core 1.x checkout.
  • The licensed booking-plugin-1.2.2-customer.zip release artifact.
  • Optional: an installed and configured Payment Plugin for paid bookings.

​
Current installation method

Booking 1.2.2 is the remaining legacy-layout plugin. Its repository release workflow intentionally publishes a customer source ZIP and no Python wheel. Do not pass this ZIP to pip.
  1. Extract booking-plugin-1.2.2-customer.zip outside the Core checkout.
  2. Locate the inner booking-plugin-1.2.2 directory.
  3. Create plugins/booking below the Core checkout and copy the contents of that inner directory into it. The result must include paths such as:
  4. Add booking to .env; preserve any other enabled identifiers.
    For paid bookings, a typical composition is RUOOM_PLUGINS=payment,booking.
  5. Apply migrations, collect static files, and check Django.
  6. Restart the application. Do not add plugins.booking to INSTALLED_APPS manually; Core adds it from RUOOM_PLUGINS when the module is present.

​
Verify and configure

Sign in as staff and open the Schedule page. Create a service type, then schedule a service. Confirm that the customer calendar is available at /booking/calendar/ and use /booking/settings/ for embed settings.
This legacy procedure is specific to Booking 1.2.2. Payment, Digital Products, Email OTP, and Single Sign-On use wheel installation and must not be copied into Core.