Disappointed whilist trying to set up a development instance to contribute.

[configari]

Spent 5 hours trying to set up with and without docker got errors and couldn't succeed and apparently the developers wouldn't help basically I'm disappointed. I'm asking the community if they have an answer.

[sudokoko]

I don't see the problem with the developers not providing support directly. According to the license (AGPLv3), the software is provided as-is with no warranty. We aren't obligated to provide support. What you can do is open an issue and provide the errors you're getting. What would also help is if you provided the errors you're receiving in this thread and maybe I can see about pointing you in the right direction.

[Slendy]

This is a side effect of having everything in docker, basically everything is segregated to it’s own network so if you haven’t already rename the lighthouse.yml.configme to lighthouse.yml and for the db and redis connection strings, the ip should be db or redis instead of 127.0.0.1 or localhost. The same applies for the listenUrls and the addresses will coincide with the name of the service in the compose file

[maximmax42]

Okay, website works. Now, I assume we also have to set up nginx as well? Using localhost:16001 instead of localhost:10060/LITTLEBIGPLANETPS3_XML won't work? Because currently localhost:16001 spits out 404. And so does localhost:16002.

[Slendy]

Yeah, by default none of the containers should be accessible from outside your local machine unless you’ve modified your firewall settings. There is an example nginx config in the repository that should work for reverse proxying though.

[maximmax42]

Well, I can't access server and api on my local machine either, unlike the website. Also, don't I have to set up nginx in docker too, or should that be done on the host?

[maximmax42]

Oh, hold on. localhost:16001/LITTLEBIGPLANETPS3_XML/status returns 200. Wait but... If I set up proxy as

location /LITTLEBIGPLANETPS3_XML/ {
                proxy_http_version 1.1;
                proxy_pass http://127.0.0.1:10061;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        }

wouldn't that mean that example.com/LITTLEBIGPLANETPS3_XML equals to localhost:16001 and not to localhost:16001/LITTLEBIGPLANETPS3_XML? So that means if I need to get the patching url, it'd be example.com/LITTLEBIGPLANETPS3_XML/LITTLEBIGPLANETPS3_XML? Or am I confusing myself?

[Zaprit]

The ports from the lighthouse containers are forwarded by default, you can either set up nginx in a container or on the host, it’s up to you, either should work On 21 Feb 2023, at 18:36, Max ***@***.***> wrote: Well, I can't access server and api on my local machine either, unlike the website. Also, don't I have to set up nginx in docker too, or should that be done on the host? — Reply to this email directly, view it on GitHub <#684 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AENIF6BIGDHCGPFBCCCV5BTWYUDMPANCNFSM6AAAAAAVDFFNMA> . You are receiving this because you commented. <https://github.com/notifications/beacon/AENIF6APY4KEDRE4HVF6E2TWYUDMPA5CNFSM6AAAAAAVDFFNMCWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAJVKVU.gif> Message ID: ***@***.***>