@@ -20,6 +20,7 @@ You are ready to run gphotos-sync for the first time, either locally or
20
20
inside of a container. The first run will require a user login see
21
21
`Login `
22
22
23
+ .. _Container :
23
24
24
25
Execute in a container
25
26
======================
@@ -35,17 +36,18 @@ Hence the typical way to launch the container with docker runtime would be::
35
36
36
37
$ CONFIG=$HOME/.config/gphotos-sync
37
38
$ STORAGE=$HOME/My_photos_backup
38
- $ docker run --rm -v $CONFIG:/config -v $STORAGE:/storage --net=host -it ghcr.io/gilesknap/gphotos-sync /storage
39
+ $ docker run --rm -v $CONFIG:/config -v $STORAGE:/storage -p 8080:8080 -it ghcr.io/gilesknap/gphotos-sync /storage
39
40
40
- The options --net=host -it are required for the first invocation only, so that the
41
- browser can find authentication service.
41
+ The options `` -p 8080:8080 -it`` are required for the first invocation only,
42
+ so that the browser can find authentication service.
42
43
43
44
Note that the authentication flow uses a redirect url that sends authentication
44
- token back to the process. The default redirect is localhost:8080 you can
45
- adjust these with ``--host <HOSTNAME> --port<PORT_NUMBER> ``. At present the
46
- flow only accepts localhost for host so I'm not sure what the option is for.
45
+ token back to the process. The default redirect is localhost:8080 and you can
46
+ adjust the port with ``--port<PORT_NUMBER> ``. The
47
+ flow only allows localhost for security reasons so the first run must always
48
+ be done on a machine with a browser.
47
49
48
- Note that if you are running on a NAS or other headless server you will first
50
+ If you are running on a NAS or other headless server you will first
49
51
need to run locally so that you can do initial login flow with a browser.
50
52
Then copy <TARGET>/.gphotos.token to the server. For this
51
53
first run you could use the following options so that no backup is performed:
0 commit comments