Closed SametSahin10 closed 4 years ago
Hi @SametSahin10
I used pmgo start my application in production env.
If you start your application that has built you can try this command:
pmgo start /path/to/your/binary/gofile appName true
For example in my case:
pmgo start /home/dev/project/scheduler/scheduler scheduler true
and i got this:
I've ended up using systemd to deamonize my application. When I think about this issue now, I think it might be due to application not finding environment variables where they supposed to be. This is just a thought. It's safe to close the issue At least for now.
I'm using
pmgo start ./work/src/github.com/sametsahin10/danef-dictionary-api/ danef-dictionary-api
to start my app. It does not give an error and it's visible when I executepmgo list
. However, I'm unable to send any requests to it. It looks like the app does not start. On the list thatpmgo list
outputs, the CPU column is always zero. What is the problem with this? I can successfully run the app bygo build && ./app-name
Output of
tail -f ~/.pmgo/main.log
I've tried stopping, deleting and starting the app to see if there's a mistake. That's why those logs are there.