Skip to content

Conversation

shiroinekotfs
Copy link
Member

@shiroinekotfs shiroinekotfs commented Sep 16, 2025

What's new?

  1. New workflow to automatic build docker container (thanks to @SunsetMkt)
  2. Fix for VERBOSE=1 error (in Update GNUmakefile: Fix build error with VERBOSE=1 #14, thanks to @dbstf)

Further changes will be applied later.

Problems that are looking further

#11
#12
#13
#15

SunsetMkt and others added 4 commits August 26, 2025 00:13
Add a GitHub workflow to build project
* feat: ghcr publishing workflow

* feat: sign docker image

* chore: rename job

* fix: revert Dockerfile
Building with option VERBOSE=1 failed due to incorrect syntax/indentation in line 510.

Signed-off-by: Stefan <93658221+dbstf@users.noreply.github.com>
Co-authored-by: Shiroi Neko <shiroineko.tfs@theflightsims.com>
Update for systemd service for

* Documentation correctness
* ExecStart with logging into files (systemd logging only start and stop)

Signed-off-by: VLTA of @TheFlightSims <anhvlt.2006@outlook.com>
@anhvlt-2k6 anhvlt-2k6 linked an issue Sep 23, 2025 that may be closed by this pull request
[Service]
Type=simple
ExecStart=/usr/bin/vlmcsd -P 1688 -H 26100 -C 1033 -l /var/log/vlmcsd.log -T1 -e -D
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we leave verbose in file logging?

I mean, if each "request" take 1.5Kb, and let the service run for like, a year, I am not sure how big it can be.

Copy link
Member

@anhvlt-2k6 anhvlt-2k6 Sep 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, but you leave comment on the wrong segment. 🥺

Edit:

Well, I confirmed that this is the real issue. I will make a change at the lab later to see if there is any potential information that will be removed from the logging.

@anhvlt-2k6 anhvlt-2k6 linked an issue Oct 3, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested
4 participants