PackagePublish Model

Overview

The packagepublish table serves as a model in the backend application to manage the publishing and unpublishing of packages. It tracks metadata related to each package file, including storage location, file size, and the user who performed the action. Despite not storing actual data, this table is integral to the system for interacting with package files, triggering publish/unpublish actions, and tracking changes.

Fields

Field	Type	Description	Required
id	string	Unique identifier for the package publish record	❌
org_id	string	ID of the organization for which the package was published. Ensures multi-tenant tracking.	✅
packagesettings_id	string	Links to packagesettings — this ties the publish event to a specific configuration set.	✅
storage_id	string	Refers to where the file is stored — could point to a record in a storage or media table.	✅
unpublish	boolean	Flag indicating whether the package has been unpublished (0 = published, 1 = unpublished).	✅
filename	string	Name of the published file.	✅
fileid	string	Unique file identifier, often used by the storage service.	✅
fileurl	string	URL where the published file is stored or can be accessed.	✅
filesize	string	Size of the published file	✅
created_at	date	Timestamp when the package was published.	❌
modified_at	date	Timestamp when the package publish record was last modified.	❌
created_by	string	Identifier for the user who published the package. Could be useful for audit trails.	✅

Sample JSON

{
  "id": "example_value",
  "org_id": "example_value",
  "packagesettings_id": "example_value",
  "storage_id": "example_value",
  "unpublish": "example_value",
  "filename": "example_value",
  "fileid": "example_value",
  "fileurl": "example_value",
  "filesize": "example_value",
  "created_at": "example_value",
  "modified_at": "example_value",
  "created_by": "example_value"
}