[ikk157]

@ikk157

you are right there .. though even for a very experienced user , there are some ways to mess things up. I mean I am not talking about working straight for days without sleep here ..

I am simply saying things that is beyond your control. Like some incompatibility or some package conflict or holdback or experimenting with source compilation and install and doing something wrong... These are the things I face..

I understand what you said there .. it seems you have found what you want to do and how to do them and keep doing those very things. YOu are more focussed on deployment and utilisation. You dont experiment with system config. may be like to work on the site rather than the underlying system.. That is very good of you..

But for silly people fooling around ( @>ME ), there is a real need of scripts doing weird things.

Thanks for your input

also,

there is always a provision for an alternative port for ssh access indicates that things can go wrong... it is not a reflection on the user doing the upgrade. You always succeed and have found ways to do things you like to do, that is very good.

The idea is that if there are any package conflicts or incompatibility issues, I would’ve found them out on my testing machines way before doing the same on my VPS 9.

However, You are very right that not everyone is as careful or has other machines to test stuff before using them on the VPS. That’s where the script you’re writing comes into play!

If you manage to make it work (which I don’t see why you won’t), that will pretty much solve your and many other holders’ problems. If you or anyone else messes the VPS up, you can just use the script to get your VPS back in business!