Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Just for future reference, it’s often better to use
#!/usr/bin/env bash
Over
#!/bin/bash
This is for portability since paths often vary from one OS to another depending on how the package maintainer has it setup at installation. Debian & Ubuntu will likely always use the same paths, much like how CentOS and Fedora most likely will, though when you bounce from one OS to an entirely different one, that’s when the differences make a difference :-).
IIRC, you should be able to use it in a cronjob script as well.