NPM Library #1606

Hey @silicoflare that is an interesting idea! I've been toying with patterns around embedding Rackula, this may be one of them.

May I ask, how would you use this: in part of an internal-facing site or something else?

It will a part of an internal facing site. I can't go into details, but yeah, we'll use it to visualize our infra in racks. Data will be fetched from a database and shown in the racks.

Also yeah, it would be great if we could add custom fields to each device, which would help with more effective integration.

Thank you for opening this discussion. I have a similar use case, and I think this direction could be very valuable.

In my case, the main system is a Vue-based asset management platform. I would like to embed Rackula’s rack layout capability into our existing asset entry workflow. Users could place devices into racks visually, but the rack diagram would also need to reflect assets imported through Excel. For example, if servers, switches, or other equipment are imported from an Excel template, they could be rendered onto the rack diagram based on rack name, U position, height, front/rear side, and related fields.

For this kind of use case, I would not necessarily need the full Rackula application UI. The most useful part would be the core rack designer capability, such as the rack/device data model, drag-and-drop placement, U-position calculation, collision validation, front/rear handling, read-only rendering, and change events that allow the host application to sync changes back to its own asset database.

I understand this may not be the current focus of the project, but I just wanted to share another real-world use case where a reusable package, embeddable component, or Web Component could be very helpful. It would make Rackula useful not only as a standalone rack layout tool, but also as an embedded asset visualization and asset input component in other systems.

Thanks again for the great work on this project.
@silicoflare @ggfevans