You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
when i deploy a lager stack via portainer, e.g. from repository (or a long web-editor session)
i can hit the deploy button, it has a endless spinner and gets greyed out.
but infact i cannot see no where what is going on.
Describe the solution you'd like
when i hit the deploy button i should be able to watch the build and deploy process below.
easiest could be the log output of the upcoming stack while doing the deploy.
Describe alternatives you've considered
when i hit the deploy button i can switch to a "deploy process" log window.
Additional context
if you run portainer on a headless machine somewhere and deploy a stack, u sometimes just wait very long with an error in the end. it's very hard to track down the error and what was really going on as the log is just a very very huge error sometimes.
having a logging output while deploying could help to track the error and makes it much more understandable while waiting for the deploy...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Is your feature request related to a problem? Please describe
when i deploy a lager stack via portainer, e.g. from repository (or a long web-editor session)
i can hit the deploy button, it has a endless spinner and gets greyed out.
but infact i cannot see no where what is going on.
Describe the solution you'd like
when i hit the deploy button i should be able to watch the build and deploy process below.
easiest could be the log output of the upcoming stack while doing the deploy.
Describe alternatives you've considered
when i hit the deploy button i can switch to a "deploy process" log window.
Additional context
if you run portainer on a headless machine somewhere and deploy a stack, u sometimes just wait very long with an error in the end. it's very hard to track down the error and what was really going on as the log is just a very very huge error sometimes.
having a logging output while deploying could help to track the error and makes it much more understandable while waiting for the deploy...
thanks
also https://github.com/orgs/portainer/discussions/11477
for this would be very very awesome !!!!
Beta Was this translation helpful? Give feedback.
All reactions