Sudo command not found

Use a different hosting service.

By default sudo is not installed on Debian, but you can install it. First enable su-mode: su -

Install sudo by running:

apt-get install sudo -y

After that you would need to play around with users and permissions. Give sudo right to your own user.

usermod -aG sudo yourusername

Make sure your sudoers file have sudo group added. Run: visudo to modify sudoers file and add following line into it (if it is missing):

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL

You need to relogin or reboot device completely for changes to take effect.

@tykus Not the answer I was looking for. Since now it is not an option.

@saurabhd I said I do not have apt-get command available either.

Are you currently logged in as a normal user or as root? Which dist of linux is it?

@Cruorzy I assume normal user. I noticed that there is an alias for su. When I try to call it it says permission denied. We use dedicated server, if that helps.

@imre08 when you reply try to tag the user.

Also the hardware doesn't matter, in my experience when you hire a dedicated server you should have access to the root user to indeed install 'sudo' and configure it if you like to.

If you don't have access to the root user you are way to limited and i'll also suggest moving, because you are simply restricted from doing almost anything.

So ask how you can find the root credentials.

@tykus Not the answer I was looking for. Since now it is not an option.

Perhaps not, but it doesn't seem that the current solution gives you the degree of control that you want. Sometimes, we just have to accept that and move on.

@tykus and @Cruorzy If you are suggesting to change service provider, then what are your recommendations. Note that I have basic knowledge of managing servers. I looked into AWS and for me it seemed pretty complicated.

Digital Ocean through Forge is reasonably intuitive.

I guess if there is no other way I will accept @tykus first answer.

@tykus I think I found another workaround, uncheck 'Restart FPM After Deployments'. That made Envoyer deployment hooks pass. Why would I need to restart fpm?