launcher logs shows the whole log for the container, which can take a while to finish. How about changing the launcher logs command to take --tail the way that docker logs does?
While I’m at it:
./launcher status app
returning:
Postgres: Up and running, unreachable.
Version: Up to date, behind, updating.
Web: Up, down, starting.
Sidekick; Up, down
Email:Up, Down
Last error: Date/time of last Major error
The idea being that ./launcher becomes a one stop, “What is going on?” tool. Just enough to give a quick health check.
3 Likes
And another thing…
How about presenting the same sort of status information via the web, similar to the way that admin/upgrade#/processes
Again, a single point of reference giving “What is going on?” type of information.
And another thing…
I’m just walking through removing the plugins one after the other to try and isolate this problem.
It just occurred to me, there is no way to do ./launcher rebuild app without pulling the latest image from docker, right?
I’m trying to narrow in on a local problem, making local changes, but I am also pulling remote changes at the same time.
Any way to do something like ./launcher rebuild app --local_only ?
No, and nothing like this is planned for the forseeable future.