Please describe your (network) setup (in private if you want), and
I'll send you the config.


On 21 August 2018 at 21:38, Viktor <[email protected]> wrote:
> Thanks for your help,
>
> Still struggling to get this to work (perkeepd is behind a reverse proxy, so
> I do not want the publisher and perkeepd to communicate over localhost, the
> config you suggested doesnt work when chaning serverListen to the localhost
> perkeepd is listening to)
>
> Anyway, my problem - digging through the sources to understand how it is
> wired up and what the config properties mean - need to learn that at some
> point anyway :-)
>
> Thanks for you help again.
>
> On Tuesday, August 21, 2018 at 8:35:43 PM UTC+2, mathieu.lonjaret wrote:
>>
>> Do you need to control the port on which the publisher is running?
>>
>> If not, you don't need to set any of apiHost, ilsten and backendURL.
>> Just set the correct server values, depending on where you're
>> reverse-proxying to (or not), such as:
>>
>> "handlerArgs": {
>>   "appConfig": {
>>     ...
>>   },
>>   "prefix": "/img/",
>>   "program": "publisher",
>>   "serverBaseURL": "https://example.com";,
>>   "serverListen": "example.com:3179"
>> }
>>
>> By the way, you can see what low-level config is generated, from a
>> running server, by going to /debug/config. Or you can use 'pk
>> dumpconfig'.
>> So whenever you have this kind of problem, you can try to get things
>> running with a high-level config, and see what the correct low-level
>> config looks like, and then use it in your prod server.
>>
>>
>> On 21 August 2018 at 19:59, Viktor <[email protected]> wrote:
>> > Hi again,
>> >
>> > Thanks for all the help yesterday - I have one more question I was
>> > hoping to
>> > get some pointers on.
>> >
>> > I have (almost) managed to set up the gallery publisher using the guide
>> > at
>> > https://perkeep.org/doc/publishing/README in that it is running, talking
>> > to
>> > perkeepd and after creating the camliRoot form "camliPath:test" to an
>> > image
>> > permanode i can access https://example.com/img/test.
>> >
>> > However, the gallery page only shows the name of the image, and looking
>> > at
>> > the network request the gallery pages tries to do a request to
>> > https://localhost:3179/img/search instead of my
>> > https://example.com/img/search (which is what I assume it should be
>> > connecting to?) - which obviously fails since there is nothing running
>> > on
>> > localhost on my laptop.
>> >
>> > Since there was no information on how to set up a low-level config
>> > (which i
>> > need for syncing the blobs to different remote targets) for publisher in
>> > the
>> > guide I have tried to put it together myself, ending up with:
>> >
>> >  "prefixes": {
>> >         "/img/": {
>> >             "handler": "app",
>> >             "handlerArgs": {
>> >             "program":"publisher",
>> >             "apiHost": "http://localhost:3179/";,
>> >             "listen": ":3155",
>> >             "backendURL": "http://localhost:3155/";,
>> >             "appConfig":{
>> >                 "camliRoot":"imgshare",
>> >                 "cacheRoot":"/home/vron/perkeep/cache",
>> >                 "goTemplate":"gallery.html"
>> >             }
>> >         }
>> >
>> > Is there something obviously wrong with this config that explains this,
>> > or
>> > is it a bug?
>> >
>> > Thanks in advance / Viktor
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Perkeep" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an
>> > email to [email protected].
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Perkeep" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Perkeep" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to