Skip to content

mystamps-candidate.war shouldn't write logs to a production log file #1604

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
php-coder opened this issue Dec 19, 2022 · 0 comments
Open

Comments

@php-coder
Copy link
Owner

Candidate WAR shouldn't write to a production log file (only to stdout):

$ grep candidate /data/logs/mystamps.log
2022-12-19 07:48:02.661 [user:  ]  INFO 26615 --- [main] r.m.w.s.s.boot.ApplicationBootstrap      : Starting ApplicationBootstrap v0.4.7-SNAPSHOT on my-stamps.ru with PID 26615 (/data/mystamps/mystamps-candidate.war started by mystamps in /data/mystamps)

Relate to #383

@php-coder php-coder added this to the next milestone Dec 19, 2022
@php-coder php-coder modified the milestones: next, 0.4.8 Jul 27, 2023
@php-coder php-coder modified the milestones: 0.4.8, 0.4.9 Dec 29, 2023
@php-coder php-coder modified the milestones: 0.4.9, next Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant