See files generated deployment
I was able to get my site deployed on railway but I'm trying to access a file that is generated after deployment. Is it possible to see it (maybe with Railway CLI)?
37 Replies
Project ID:
N/AN/A
To elaborate, when executing supervisord, all the logs of the child processes will be in a seperate file generated after starting supervisord
im wondering if its possible to view the contents of those files
for all intensive purposes, it's not possible.
configure supervisord to log to stdout/stderr
oh yea the second part would also be useful
what exactly is stdout/stderr through
is that the deploy log?
I can already see the output of supervisor here though
i just want to see the output of the child processes run by supervisor
I'm sure there's some results from Google that could explain it far better than I could
configure supervisord to forward the logs of the child process to stdout/stderr
oh i see
and how do I view stdout/stderr from railway?
the deployment logs
ok great
thanks i will research into this
ok i figured out the command but what would be the directory I should forward the logs to?
I need to set
stderr_logfile```
i dont know off the top of my head, that would be something you could look up though
me telling you would just be me googling it 🤣
ah ok
ill try lol
it seems like supervisor only has an option to redirect stderr ðŸ˜
theres no option for redirect_stdout
i googled it
stdout_logfile=/dev/stdoutwait what
where did you find that information
uh in the second link of my google search
hmm my stdout is just completely empty now
oh i just realized this is actualyl the original code i had
so thats why I was able to see this
new ideas:
- take my original advice and run two railway services, forego supervisord
- use parallel instead of supervisord
- use multirun instead of supervisord
I'm trying to get the sdtout of the child processes
🙂
will that allow me to view the stdout of child processes from the deployment log?
all those options will
the first option being the best
hmm wdym by two railway services
what processes am I splitting up
the things you are trying to get supervisord to run
hmm ok i will try
currently its just huey (celery) and the flask app
yeah a railway service for the flask app and a railway service for the huey thing
wait but then I wouldn't need supervisor anymore
correct
since i would just be starting each seperatly
ahh
therefore no issues with logs
i see what you mean
thanks!
to make it easy, i would have a
Dockerfile.huey and a Dockerfile.flask that hopefully are self explanatory, then specify the appropriate dockerfile via the RAILWAY_DOCKERFILE_PATH service variablebut just for future reference its not possible to view files deployed inside railway?
so for example I wouldn't be able to see the contends of childlogdir
unless you build that kind of functionality into your app, no
ok i see
thanks again!