Local "CI server", site "WebHare backend" not published

9 views
Skip to first unread message

Wouter Hendriks

unread,
Nov 30, 2024, 7:41:57 AM11/30/24
to General WebHare developers discussion

I've created a local "CI server" to test my CI (see at the end how to do this, might be useful for others).

Problem is that my tests can't reach:

/testportal/?overridetoken=g69cFzCLF5ohpi_UV2mr9A&app=wvuaw%3Amain(isunittest)&openas=manager%40beta.webhare.net

It seems that on my local server, the "WebHare backend" site has an output (localhost:8000/), but it doesn't on my CI server. That's probably in part because the CI server doesn't have any webservers; the list in "Webservers" is empty. So yeah, can't output to anything then.

I can't imagine there isn't something in WebHare that would (or maybe even should) solve this, but what?


---- Steps for CI server ----

- create a server using https://gitlab.com/webhare/runkit:

runkit create-server ci

(notice the "Server created. To start: 'runkit @ci run-webhare' and access the server on http://127.0.0.1:23660/" message for the URL)

- there's no user yet, so you'll need to create one; in new terminal (or after 'Don't forget to run 'runkit-reload' to activate the 'wh-ci' command'):

wh-ci cli getoverride "First login"

Use the override token to login and create a user

- add some modules; you might do this by linking a couple of modules:

ln -s "$(wh getmoduledir example)" "$(wh-ci getdatadir)/installedmodules/"

Arnold Hendriks

unread,
Dec 1, 2024, 2:37:22 PM12/1/24
to General WebHare developers discussion
On Saturday, November 30, 2024 at 1:41:57 PM UTC+1 Wouter Hendriks wrote:

I've created a local "CI server" to test my CI (see at the end how to do this, might be useful for others).

Problem is that my tests can't reach:

/testportal/?overridetoken=g69cFzCLF5ohpi_UV2mr9A&app=wvuaw%3Amain(isunittest)&openas=manager%40beta.webhare.net

It seems that on my local server, the "WebHare backend" site has an output (localhost:8000/), but it doesn't on my CI server. That's probably in part because the CI server doesn't have any webservers; the list in "Webservers" is empty. So yeah, can't output to anything then.

I can't imagine there isn't something in WebHare that would (or maybe even should) solve this, but what?


CI inside docker containers (wh testdocker) works by setting WEBHARE_CI=1 which triggers a webserver on port 80. If you start a fresh webhare otherwise, nothing is configured, as it assumes you'll do so through the command line or using the 'rescue' webinterface on http://127.0.0.1:<webhare base port number>


Wouter Hendriks

unread,
Dec 2, 2024, 10:04:12 AM12/2/24
to General WebHare developers discussion, Arnold Hendriks
Reply all
Reply to author
Forward
0 new messages