If Kolo can't write to .kolo (or wherever your KOLO_PATH is), Django exits with this message:
Error: You don't have permission to access that port.
I came across this in Docker, because while my code is mounted inside the container, it doesn't have write access. I can obviously account for this, but it took me a while to figure out what the problem was. Maybe Kolo could detect this and log something before Django exits to give users a hint.
First of all, loving your work! ❤️
If Kolo can't write to
.kolo
(or wherever yourKOLO_PATH
is), Django exits with this message:I came across this in Docker, because while my code is mounted inside the container, it doesn't have write access. I can obviously account for this, but it took me a while to figure out what the problem was. Maybe Kolo could detect this and log something before Django exits to give users a hint.
Thanks!