@kageurufu Hello again.
Re:
Try starting from a source install. But note that updates are not supported and all rpms are considered an update from an source install. And this in turn will necessarily wipe the db as a source/developer install is by default an unknown version. Hence the heavy handedness.
See: Built on openSUSE dev notes and status
Although we have had an upstream issue re pypi changes I think it was that we have yet to update that page to reflect. @Flox found a work around that we have yet to pop into those docs and our other developer docs actually.
It may well be worth opening a new thread to report where this rebuild is failing for you. I know the rpm for example strips our, for size, many of our test. But I think you should be able to rebuild the templates using what’s distributed. Take a look at the following doc section also:
https://rockstor.com/docs/contribute/contribute.html#change-test-cycle
The docs are a current focus, ready for our first v4 Stable release, so we should get to these updates soon hopefully.
If you made any javascript, html or css changes, you need to collect static files with this command:
[root@build_vm ]# /path/to/build_dir/bin/buildout -c /path/to/build_dir/buildout.cfg install collectstatic
Further to what @kageurufu & @Flox have already stated. Rockstor is Django, all-be-it an old one. We have the following ongoing issue to drag us into the next testing channel so we can in turn also update our Python 2 to 3:
https://github.com/rockstor/rockstor-core/issues/2254
That issue will soon be removed from the indicated GitHub milestone as we juggle things towards the official Stable release. I now think that is too much of a change to cram into our current release candidate run.
Hope that helps.