Best practices

Here are a few best practices to follow when using OneOps. Lots of these are suggested by the OneOps team in their official documentation. I have tried to provide justification for some of them where possible:

• Follow a set naming convention for assembly names. OneOps sets some rules as to how you can name an assembly, such as no spaces. Also remember that your assembly name will become part of your FQDN after deployment, so choose a good assembly name.

• Always add owner's e-mail ID to your assembly and enable watching. Be responsible for your own deployments. That's what DevOps is all about!

• Be cognizant of the default values and tune them accordingly. Sometimes, the defaults will trip you up.

• Choose good and descriptive platform names. A good suggestion is name them according to the platform you are adding, that is, if you are adding Postgres, then call it Postgres or Postgres-middleware.

• Do not make changes directly to an instance, even if you can. You will cause configuration...