You seem to be editing production deployed files. You shouldn’t do that. Depending on what you do, you may need to rebuild the assets and that could get tricky as it’s already been deployed to filesystems owned by root.
You should instead do what we do - develop the dashboard in your local $HOME directory
- The link above may be the only docs we have on extending/developing the dashboard.
- They are random for each version/build. It’s a mechanism to cache bust. That is, if 3.1 has new assets - they have a new unique id so they’ll get pulled by browsers and the 3.0 assets that have been cached won’t be used.
- CSS is compiled into a global/single file. So separation for it is really only for developers organization of files. JS compilation is a little more involved, but is basically the same convention.
- You can see how we do this for file uploads. We embed the configuration in the HTML so that javascript libraries can pull the values from the same.
<%= content_for?(:title) ? yield(:title) : \"Dashboard - #{@user_configuration.dashboard_title}\" %> - I rely on the CI (continuous integration) on github to catch any mistakes. You can run the same tests locally, though you don’t need to do e2e (end to end) tests, unit tests are good, system tests are better.
- We use document ready a lot, I think that’s fine depending on what you’re trying to do.
All that said - if you opened a pull request against the main OnDemand repository, even if it’s draft/work in progress I’m happy to take a look and provide feedback. Even if you don’t want to provide it upstream I can help you manage it so that you can merge it to your fork and build a new RPM for your site.