Problem with Heroku Push about multi_logger HOT 7 OPEN

Didn't an error the first time I pushed, did the second time. Taking the multi logger line out of my initializer got me past the problem. If you can give me a few hints I'd be happy to patch this one.

from multi_logger.

Hi there. I have never used Heroku, so I can only assume this is because Heroku tries to prevent apps from creating files (because it want to be a static system). In heroku, how do you view your log files? Do you SSH in to the machine and then CD into the log directory and view the log file?

from multi_logger.

You view the log files using the heroku client, as you don't have direct access to the filesystem. A similar problem in another gem recommended adding the file in question to version control (one deploys to heroku using git) but this also did not fix the issue..

from multi_logger.

So I see that you type heroku logs to access logs. What command do you expect to use access custom logs?

from multi_logger.

honestly haven't gotten that far with it yet, was going to loo at redirecting multi logger to stdout for heroku. the main thing was just being able to push to heroku without disabling the log i had set up, but you may be on the right rack - how could i simply redirect multi logger to stdout for a certain environment ?

from multi_logger.

I guess you can wait for #7 pull request. It will add a way to change logging file path. Then I can add one extra conditional check on top of that, so passing :stdout symbol would actually mean redirecting t to STDOUT

from multi_logger.

Thanks. I think that what would make the most sense would to be log to STDOUT and also be able to prepend the logfile name to the log output for heroku. I have started looking into how this would be accomplished, not too familiar with the ActiveSupport codebase though.

from multi_logger.