Backend Services Missing / Confusion

[larron]

Hello there,

I've been messing with your repositories for a couple of days, it looks like you guys have been hard at work.

I've managed to get core and app up and running but finding some intricate details missing.

I'll start with the first one.

On load, the web app attempts to pull from the api at path /config/web/v1 and in my case, this is mapping to a 502 bad gateway.
I tracked it down to the reverse proxy expecting some service to be running at http://config:8080

What is that service? (I do not see any direct mapping or correlation to the core services, docker-compose, etc...)

As a secondary follow-up. What services should be running on behalf of the captcha, stream, storage and referral as I also don't see a direct correlation upon browsing core.

Thank you for your help, tagging @fatemeh-i as I've seen you are the most recent editor of this repository :)

[fatemeh-i]

Dear @larron ,
We appreciate your interest in our repository.
Some of our services such as referral, stream, .... are not included in our open source version and have a price. For demo version you can check opex.dev and for more information, please contact [email protected].

[larron]

@fatemeh-i I see, we will be in contact.

In the time being, can you point me in the right direction as to the first issue I am seeing with /config/web/v1 not resolving? IE: No idea where http://config:8080 should be pointed to.

I'd also love some information (and sure everyone else would) in regards to which modules are not OSS and what add-ons they bring. Thank you.

[fatemeh-i]

@larron
In general, you are right about the service information. these days one of our priorities is to complete such documents. 💪🏋️‍♂️🏋️‍♀️
We will try to prepare it very soon. 😊
But specifically about your problem: Config service is one of our paid services where some general information of the system such as title, logo, default language, etc. is stored there to be used later in the system interfaces.

[larron]

@fatemeh-i documentation would be excellent! :)

The config issue is completely breaking the web-app. Is it fair to say that the web app is not built to be OSS in that case or is there some other way to run it without the config?

[fatemeh-i]

@larron
hi again,
We have investigated your issue and fixed it in our latest update to opex/web-app (opexdev/web-app#229), now you can run this project without needing to config service.