Hi Peter,

Am 31.10.25 um 20:33 schrieb Peter Kovacs:

Am 31. Oktober 2025 20:22:20 MEZ schrieb Matthias Seidel 
<[email protected]>:
Hi Peter,

At the moment the test server gives me a 503.
I missed a change when I copied my local config to the server.
The deployment process is a bit sketchy. 😇
I restart opengrok once the index of trunk is done.

Just FYI:

Still no trunk.

And indexing doesn't work since I still see code I removed days ago (AOO42X).

Regards,

   Matthias

Regards,

    Matthias

Am 31.10.25 um 20:16 schrieb Peter Kovacs:
Hi Damjan, all,

I am able now to add config stuff. But so far no luck with the tab size.
The indexing failed on a view other things I hope I have that out of the way.

Once the indexing works I would like to get the update into production we can 
search for that tab size solution in the meantime. I don't think it is a 
blocker.

Am 30. Oktober 2025 03:44:14 MEZ schrieb Damjan Jovanovic <[email protected]>:
On Sat, Oct 25, 2025 at 6:28 AM Peter Kovacs <[email protected]> wrote:

Am 25.10.2025 03:39 schrieb Damjan Jovanovic:

It works well, but trunk is missing, and tabs size is still 8 spaces
instead of 4.
i added trunk, should appear after some time.
I check with the tabsize. The config is reset by some reason and to set
it in the dockerconfig was ignored too. I keep searching.


I've become more familiar with Docker lately, so I could also try to help.
Of course. I pushed a branch in Dec tools repo called 
migration-translation-opengrok

You need to adjust the .env file to your local setup. For the config path you 
need to copy the custom config to opengrok_config path and rename it to 
read-only.xml

Then a docker compose up should spin up the opengrok and once the initial scan 
is through you can play around.
Regards
Damjan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to