Closed engeir closed 1 year ago
Hi, it actually depends a bit on how you want to use photo-stream. It looks like you want to use it via docke, so there usually is no need to fork the project to begin with. Basically it should be as follows:
.env
file according to your needs. Make sure that PHOTO_PATH
is set correctly or no photos will be shown.docker compose up -d
.http://localhost:4000
.Then every time you add or delete photos in the folder defined in PHOTO_PATH
the site should be rebuild automatically.
Okay, thanks, got it!
I have been using this for a while and been very happy about the simplicity of the website. However, every time I have wanted to upload new photos I've had a hard time getting it to work. (My repo and website.)
Following docker
When trying to follow the docker approach, this is how I understand it should be done:
The other alternative as I understand it would be:
Then there is the
docker-compose build
command mentioned in the section about raspberry-pi, so it seems like this is not relevant unless one is using a raspberry-pi?Manually
Installing from a release:
But the above results in an error also mentioned in #77.
All approaches mentioned in the README are a bit confusing to me, so it would be very helpful to have a "step-by-step preferred installation and usage" laid out.