* TO 'foobar'@'%' IDENTIFIED BY 'foobar';
GRANT ALL ON foobar_test.* TO 'foobar'@'%' IDENTIFIED BY 'foobar';
GRANT ALL ON foobar_prod.* TO 'foobar'@'%' IDENTIFIED BY 'foobar';
FLUSH PRIVILEGES;
It??™s important that this database isn??™t exposed to the Internet. If it will be exposed, make
sure that you use other passwords to make them less obvious to guess.
This is all the knowledge about MySQL administration that you??™ll need for this book. In
most cases, ActiveRecord migrations will take care of the rest for you.
CHAPTER 2 ?– GETTING STARTED 17
Summary
We??™ve installed Java and JRuby, we??™ve installed all needed Gems, and we??™ve installed and configured
a MySQL database engine. We now have everything we need to have in our environment to
be able to start creating JRuby on Rails applications from scratch. One thing I haven??™t mentioned
is the question of where to write your code. I won??™t give you a recommendation about this,
because it??™s a highly inflamed topic. Suffice it to say, everyone chooses different solutions. What??™s
important is that you write your code yourself right now??”don??™t use code generators that write
code for you that you won??™t understand. I usually use Emacs for writing Ruby code; I know many
people love TextMate for Rails development. NetBeans, Eclipse, IntelliJ, and JBuilder all have
solutions for writing Ruby code. In the end, you??™ll have to choose for yourself, but for most of
the book, Notepad or vi will work fine.
Pages:
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76