Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Installation issues #89
While trying to run\install Kiwi on my machine, I've met some issues:
Probably URL should be changed to https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/e/epel-release-7-11.noarch.rpm
OK, so the node_modules/ directory needs to be populated by
However Kiwi TCMS is supposed to be executed as a Docker container, not installed as a stand alone application.
The rest of the issues you are seeing are due to some changes in CentOS/EPEL repositories. Obviously they have changed their URL structure and also updated some of the RPM versions. Will update Dockerfile for that.
The ugly UI is because you are missing the node_modules/. This is a Django based project so you also need to execute collectstatic before the UI can find all of its images and CSS. See that the Dockerfile is doing and do the same.
Have you read chapter 2 "Running Kiwi TCMS as Docker container" ?
It describes everything you need in order to build a Docker container and start it.
The container binds to all addresses so just access the machine via its FQDN.
Even from Docker container UI is the same.
As I wrote, it's simple, but it's missing part "Install docker. Install docker-compose".
In "Contributing" part of the doc it's still about local environment without any Docker stuff.
One more issue is development flow. It took me a while before I realized that in the container all actual code is inside... ./venv/lib/python3.5/site-packages/tcms ! It makes development process... interesting... how do I deliver my changes to container? I heard that usually you should use volumes for bypassing actual code directory to the container, but looks like it's not the case here?
added a commit
Oct 30, 2017
referenced this issue
Oct 30, 2017
@GodfatherThe I actually didn't understand some of the previous comments but the last one makes things more clear for me. Please see #92. I think it covers your concerns. Please review it if possible.
About development flow:
you are supposed to be running Kiwi TCMS via ./manage.py runserver for local development and testing. This is the standard way of working on Django related projects. You don't need docker for development. I think my previous comments have confused you and I'm sorry for this.