How is the best way to edit rock-ons?

[phillxnet (Philip Guyton)]

@pepsov Hello there.
@Flox is far more familiar with the Rock-on system but I can chip in on this one:

@pepsov

The original question still remains unanswered though:
Where does RockStor keep the configuration files for the ‘standard’ rockons?

and:

@pepsov

So, what is the equivalent for /opt/rockstor/rockons-metastore for the ‘standard’ rockons? Is it even stored locally on my server, or is it always fetched from an external repo?

They are here:

GitHub - rockstor/rockon-registry: hosted registry for Rock-ons

or more specifically the published counterpart at rockstor.com.
These files are then parsed and the infromation translated into database entries.

When you press the update button they are re-read form the interwebs and re-parsed. Otherwise the database entries are used.

Take a look at @Flox excellent technical doc on the Rock-ons system internal workings:

Rock-on framework implementation

Note: this document will be split in several posts in order to fit within characters’ limit. Make sure to browse the second post as well for more information . Preambule This is a wikified post documenting how Rockstor implements the rock-on framework, and should thus be considered a live document expected to be updated as necessary. As a user documentation already exists on how to use the framework (see link below), however, this write-up intends to first summarize the overall rock-on …

and

Rock-on framework implementation

Note: This is part 2 of the document, directly following the above post. Rock-on install process Main file of interest: rockons.js Clicking the “Install” button for a given rock-on triggers the installRockon function, which gathers the RockOn object from the list of available rock-on (RockOnCollection fetched above) by matching the id from the install button with the id in the RockOnCollection. It then opens a new install wizard overlay by creating a new instance of the RockonInstallWizardVie…

It’s very detailed and well explained.

Well done on sorting out your issue, at least in part. Always best to use different names / references in your own custom Rock-ons than those in the default ones.

Hope that helps.