you are on the right track, sending logs to stdout instead of stderr would print them as info, can you please provide a minimal reproducible example for me to test

yeah i'll whip one up when i get back to my computer

sounds good!

ok i think this should do it

package main

import (
  "os"

  "github.com/charmbracelet/log"
)

func main() {
  log.Default().setOutput(os.Stdout)

  port := os.Getenv("PORT")
  if port == "" {
    port = "8080"
  }
  log.Infof("Listening on port: %s", port)
}

what version of go do you use

i tried both log.Default().setOutput() and log.setOutput() and both seem to send to stderr anyways

1.22

is cmp.Or a thing in that version?

it is indeed

little tip but it has nothing to do with logs - port := cmp.Or(os.Getenv("PORT"), "8080")
saves 3 lines haha

that's pretty nice. never used that before lol

okay ill get to testing now

thanks so much!

well not off to a good start

oh that's totally my bad

no lsp in discord code blocks

capitals for public methods is right. I've been writing too much rust

okay so it looks like you just can't set the default logger's output to stdout

i was just about to say that lol

but making a new logger with stdout as its output seems to fix the problem

so i'll just have to make that work

should be fine

i was also going to say that lol

thanks so much for your time on this lol

as a go dev myself, may i ask why charm?

pretty colors

if i'm being serious it's mostly that i appreciate them having a lot of different log levels that are visually differentiated instead of just either crashing the program or not

are you planning on using the json logger?

i wasn't aware there was going to be one

this was all done with stdlib slog

this is what can be done with json logging on railway

oh that's pretty interesting. I might look into implementing that down the line

this is just my personal site so right now I'm just trying to do basic request logging middleware that doesn't turn my whole log page red lol

sounds good

thanks for helping out again :)

no problem!

interesting postscript to this: it looks like my original fix actually was working for some logs but not others. I'll have to do some digging to see what's different between them

charm doing some weird stuff then eh

i figured it out

and this is incredibly silly

my original fix totally worked: it redirected all of the charm logs to stdout instead of stderr

but my logging middleware was using stdlib log instead of charm log, so it didn't apply to those

haha okay that's funny

just pushed the change and everything is showing up blue!

awesome