You'd probably want some mechanism here to take a "snapshot" of the current storage mounted into the container before fucking with it. Because if you change it then you have to rebuild the container to get it working. So, you might bork your container later down the line when you deploy again.
You'd probably want some mechanism here to take a "snapshot" of the current storage mounted into the container before fucking with it. Because if you change it then you have to rebuild the container to get it working. So, you might bork your container later down the line when you deploy again.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This means that you kinda bork your setup on the host side.
Not sure how that can be reversed from the client side.
Worth thinking about.
You'd probably want some mechanism here to take a "snapshot" of the current storage mounted into the container before fucking with it. Because if you change it then you have to rebuild the container to get it working. So, you might bork your container later down the line when you deploy again.