Hi @yoavst, I recently thought about how to make running Graffiti locally even easier (because I wanted to use it but the webserver in the network didn't work and I didn't have the time to check why and fix it, so I just ran Graffiti locally).
Currently to run you unzip the zip to a folder, and serve a webserver from it (e.g. python -m http.server), and also run the .pyz server.
The things that bothered me are having to keep the unzipped folder around and remember to delete when I'm done, and a little bit, keeping track that I have the webserver and .pyz processes running.
What do you think about having a small docker image with python and the graffiti folder that runs the webserver and .pyz server?
It makes running locally just docker load -i graffiti_image.tar && docker run <flags> graffiti.
No folder to keep track of, and keeping track of a container is a little bit cleaner than the 2 processes.
Theoretically we also can upload the image to a registry and remove the docker load part, also, it might be a nice way to deploy even a "production" graffiti server.
Hi @yoavst, I recently thought about how to make running Graffiti locally even easier (because I wanted to use it but the webserver in the network didn't work and I didn't have the time to check why and fix it, so I just ran Graffiti locally).
Currently to run you unzip the zip to a folder, and serve a webserver from it (e.g.
python -m http.server), and also run the .pyz server.The things that bothered me are having to keep the unzipped folder around and remember to delete when I'm done, and a little bit, keeping track that I have the webserver and .pyz processes running.
What do you think about having a small docker image with python and the graffiti folder that runs the webserver and .pyz server?
It makes running locally just
docker load -i graffiti_image.tar && docker run <flags> graffiti.No folder to keep track of, and keeping track of a container is a little bit cleaner than the 2 processes.
Theoretically we also can upload the image to a registry and remove the
docker loadpart, also, it might be a nice way to deploy even a "production" graffiti server.