Change the deploy script to save the logs to a file and transfer them that way.
Now that we're logging each HTTP response, the logs are much larger in general. Since I didn't deploy during WYWAE, that made them longer still. So, the first deploy I did post-WYWAE caused "docker logs mb2" to take long enough that mb2 was down longer than normal, even though there's considerable buffering going on.
The solution is to simply create a file and then rsync the file across.
ctm
commented
5 months ago
Change the deploy script to save the logs to a file and transfer them that way.
Now that we're logging each HTTP response, the logs are much larger in general. Since I didn't deploy during WYWAE, that made them longer still. So, the first deploy I did post-WYWAE caused "docker logs mb2" to take long enough that mb2 was down longer than normal, even though there's considerable buffering going on.
The solution is to simply create a file and then rsync the file across.