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!
You can do this in a lot less steps
Deu tudo certo mas, no phpmyadmin estar aparecendo esta mensagem A extensão mcrypt não está presente. Por favor, verifique a configuração do PHP.´´
em fim, não sei se isso tem a ver com a configuração pois não consigo achar o erro ,se alguém poder me ajudar eu agradeço desde já,abrç
Following the tutorial and getting the following issue:
ubuntu@host:~$ sudo mysql_install_db FATAL ERROR: Could not find my-default.cnf
If you compiled from source, you need to run ‘make install’ to copy the software into the correct location ready for operation.
If you are using a binary release, you must either be at the top level of the extracted archive, or pass the --basedir option pointing to that location.
Any ideas on what basedir should be?
@robertoramospereira: You need to install the mcrypt extension. Run:
<pre> sudo apt-get install php5-mcrypt sudo php5enmod mcrypt </pre>
See: https://www.digitalocean.com/community/articles/how-to-install-and-secure-phpmyadmin-on-ubuntu-14-04
I’d strongly recommend that you use the default mysql-server package, and not the mysql-server-5.6 one.
@andrewsb, any particular reason for the recommendation, other than to work with the instructions provided? I’m keen to have 5.6 for innodb with full text search, and 5.6 is the only way to get it right now…
@rich: 5.6 is in Ubuntu’s “universe” repository while 5.5 is in “main.” That means that 5.5 will receive updates and security support for the life of Ubuntu 14.04. 5.6 is maintained by the community and only will receive updates on a best effort basis. I’ve been able to reproduce your problem using 5.6, and I believe it is a bug in the package.