Skip to content
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

Platform needs to log in console for easy docker logs access #180

Closed
richard-julien opened this issue Aug 4, 2019 · 2 comments
Closed
Assignees
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@richard-julien
Copy link
Member

Description

Platform needs to log in console for easy docker logs access

Expected

In production the platform will logs in standard output

@richard-julien richard-julien self-assigned this Aug 4, 2019
@richard-julien richard-julien added this to the Release 1.1.2 milestone Aug 4, 2019
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Aug 4, 2019
@richard-julien
Copy link
Member Author

Version 1.1.1 released this 25 days ago --> August 4
Commit of @SamuelHassine and me --> July 22 on documentation already introduce this concept.
So this one is already covered

export const DEV_MODE = environment !== 'production';
logger.add(
  new winston.transports.Console({
    format: winston.format.simple(),
    level: DEV_MODE ? 'debug' : 'warning'
  })
);

If you are agree @SamuelHassine , you can just close the issue.

@SamuelHassine
Copy link
Member

SamuelHassine commented Aug 29, 2019

@richard-julien yes I know we already implemented this issue but it is not working, when launching in production mode, no log are displayed in the console (even error).

@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Sep 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants