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
It’s possible that Harvey has a memory/CPU leak and eventually kills Docker
Is this only a problem on macOS? Does this occur on Linux?
List the remote address so you can see if a repo is using git urls or https urls
Can’t we just listen on the docker socket and run Harvey in a container?
Use sqlite for Harvey UI to pull user logins from now that we can point a laravel project to it easily
Provide an interface where we can git log quickly and select a commit to deploy so we can “rollback” a bad deploy
Show commit messages in logs
Failed deployments aren’t showing runtimes
Add monorepo support, a config file that listed the dirs to deploy and how (server-infra)
If we can’t do a fail fast “git status” on the project remotely then fail, don’t wait for the 300s timeout because an SSH key isn’t loaded
Harvey CLI
Move away from killing off workers and having multiple workers as they do not respect in-flight deployments. Move to docker and replicate containers for better redundancy
Pull deployments aren’t showing runtimes
Harvey UI real-time page updates via Ajax and a cute little spinner to convey a deploy in progress
The text was updated successfully, but these errors were encountered:
git log
quickly and select a commit to deploy so we can “rollback” a bad deployThe text was updated successfully, but these errors were encountered: