Set up to run LexBox alongside LF in dev mode

[rmunn]

Language Forge port changed to port 8080 so that port 80 can belong to local LexBox.

Fixes sillsdev/languageforge-lexbox#708

Description

Add appropriate environment variables to docker-compose.yml so that Language Forge can be run alongside a locally-installed copy of LexBox.

Screenshots

Checklist

• I have labeled my PR with: bug, feature, engineering, security fix or testing
• I have performed a self-review of my own code
• I have reviewed the title & description of this PR which I will use as the squashed PR commit message
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• I have enabled auto-merge (optional)

Testing

To run:

• Check out LexBox and run task up
• Check out Language Forge and run make

To verify:

• Go to http://localhost:8080 to run Language Forge
• Click on "Get Project from Language Depot"
• Type in username manager and password pass
• Note the Sena-3 project is available
• Run docker logs -f lfmerge to watch the clone process
• Clone Sena-3
• Go to My Projects and click on Sena-3
• Check that all the entries are there

[github-actions]

Unit Test Results

362 tests   362 ✅  13s ⏱️
 37 suites    0 💤
  1 files      0 ❌

Results for commit bbd54f1.

[rmunn]

Tested on my machine and it works. Could clone a large project with embedded audio files, and verified that all entries were present and the audio files played correctly. Also tested with #1789 merged into this PR, which also cloned the same project correctly.

[myieye]

I can't access 8080 consistently. I have no idea why. After every make [dev] it was always a mystery as to whether it would be available or not 🤷. I'm guessing it has something do to with my machine. But maybe someone else should try this? @hahn-kev

But it did hit my local lexbox when it worked. That was cool.

[rmunn]

I actually had the same problem yesterday, tried 8081 and it didn't work, tried 8083 and it worked. Have not yet determined why: nothing was listening on port 8080 (I checked), so there wasn't a port conflict. But somehow, Docker Compose just would not hook up port 8080, and didn't give me an error message explaining why.

[rmunn]

More weirdness from Docker Compose. I'm not seeing any bind: address already in use messages, but somehow the port mapping just won't bind. Change to another port, and it usually (usually) works... as long as that's a port I haven't used recently. If it's been recently used, no dice. Various issues like https://www.github.com/docker/compose/issues/11572 are being reported, but all of them report error messages. I'm seeing no error messages at all, just a port that silently fails to bind.

At the moment, I'm inclined to hold off on merging this PR, because the port weirdness makes it nearly unmanageable to do LF development: every time you run make, you have to manually edit docker-compose.yml to change a port and then run make again. Not worth the effort, IMHO.

[megahirt]

These changes look good. I know that we're dealing with port mapping weirdness but honestly I don't think it's due to these changes but rather to buggy docker compose behavior that exists regardless. I'd rather get this merged and continue figuring out how to make the two repos working together. Merging is a step in the right direction.

One thing I'm sure about is whether SvelteKit or something Svelte related in LF was running on 8080 already. I couldn't find any reference in our code to 8080 but it's possible it's the default for something that is not spelled out in code.

[rmunn]

There are no other references to port 8080, and Svelte-Kit's default port is 5173 or 4173 depending on if you're running the dev server (default port 5173) or the preview server (default port 4173). So using port 8080 won't conflict with anything internal. It might possibly conflict with the defaults of some other tools, and if it does, we can easily accept a new PR to change it to some arbitrarily-chosen port number. But I think sticking with 8080 will be fine.