Installation issues

[kiwitcms]

Installation issues

[atodorov]

OK, so the node_modules/ directory needs to be populated by npm install patternfly. I agree that this needs to be documented b/c it is missing.

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.

Before all the magic, one need Docker (ok, this was simple) and docker-compose, but it's not written anywhere

Have you read chapter 2 "Running Kiwi TCMS as Docker container" ?
http://kiwitcms.readthedocs.io/en/latest/installing_docker.html

It describes everything you need in order to build a Docker container and start it.

I was not able to locate manual for production run, so how do I make it accessible not only for localhost, but for the network?

The container binds to all addresses so just access the machine via its FQDN.

[okainov]

Even from Docker container UI is the same.
Upd: after following the process from scratch it was fixed. Probably I messed up something during first tries.

It describes everything you need in order to build a Docker container and start it.

As I wrote, it's simple, but it's missing part "Install docker. Install docker-compose".

However Kiwi TCMS is supposed to be executed as a Docker container, not installed as a stand alone application.

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?

[atodorov]

@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.