Question: I want the ParticleSystem in top of all QML stuff. But some QML Items seems to be not part of the normal z ordering. Like in following example, PopUp is always drawn in top of the particleSystem.

* z property seems not to work
* particleSystem as child of PopUp is no option

thx for help and suggestions

```qml
import QtQuick 2.6
import QtQuick.Layouts 1.3
import QtQuick.Controls 2.2
import QtQuick.Window 2.0
import QtQuick.Particles 2.0

ApplicationWindow {
    id: mainWindow
    visible: true
    Component.onCompleted: app.quickLoadGame();
    Button {
        onClicked:      popUp.open();
    }
    Popup {
        id: popUp
        x: ( mainWindow.width  - width  ) / 2
        y: ( mainWindow.height - height ) / 2
        width:      mainWindow.width  * 0.8
        height:     mainWindow.height * 0.8
        modal: true
        closePolicy: Popup.CloseOnEscape | Popup.CloseOnPressOutside
    }
    ParticleSystem {
        anchors.fill:   parent
        ImageParticle {
            source:                 "qrc:/png/icon/xp.png"
        }
        Attractor {
            pointX:                 mainWindow.width / 2
            pointY:                 0
            strength:               1000
            affectedParameter:      Attractor.Velocity
            proportionalToDistance: Attractor.Constant
        }
        Emitter {
            x:                      mainWindow.width / 2
            y:                      mainWindow.height
            lifeSpan:               3000
            velocity:               AngleDirection { angleVariation: 180; magnitude: 100 }
        }
    }
}

```

Answer: 
the `./manage.py runserver` requires to Allocate a pseudo-TTY. You can pass it to docker-compose.yml this way

```
services:
  web:
    tty: true
    command: ./manage.py runserver 0:3000

```
In my case, I faced this problem only on the very first `docker-compose up` run. It happened because DB initialization took too long. So just press `Ctrl-C` and run `docker-compose up` again.

`depends_on` does not really monitor the DB-server status — it monitors container status. So it starts your web app before the DB is really ready for connection.

And yes, `tty: true` suggested by Mazel Tov is very useful. Without it, you won't see the Django error message (I don't know why) which would help you to understand the issue.