Maybe a quick one for @brianteeman's efforts of one PR a day?
Labels |
Added:
?
|
I actually thought I changed this in a PR years ago, maybe that was something else...
Really, local installs should not use the "root" mysql user either - but developers (just like me) are lazy and use root all the time during development - Its still bad practice for all the same reasons as using the linux root user ... but then I dont need to educate you on that :) (and yes, I ALWAYS login as root on linux servers too haha).
It should be something along the lines of "This is the username of the user that has read/write permissions on the database"
I also think the database name should come before the user/pass :-) but thats just me :)
On 27 Jan 2015 22:34, "Phil Taylor" notifications@github.com wrote:
I actually thought I changed this in a PR years ago, maybe that was
something else...
That was prefilling admin as the super user name
Really, local installs should not use the "root" mysql user either - but
developers (just like me) are lazy and use root all the time during
development - Its still bad practice for all the same reasons as using the
linux root user ... but then I dont need to educate you on that :) (and
yes, I ALWAYS login as root on linux servers too haha).It should be something along the lines of "This is the username of the
user that has read/write permissions on the database"
I will write something tomorrow. Probably a bit less techy than that
I also think the database name should come before the user/pass :-) but
thats just me :)
I will check and see what others do
—
Reply to this email directly or view it on GitHub.
I indeed use root
all the time locally.
I guess we can indeed change this, explicitely explaining that, even locally, it is a good idea to change settings to not use root
but keep that word in the tip.
Be aware though that this change would require all installation ini files to be updated.
As we are in language string freeze for anything that would need translation this will have to be done after the 3.4 release.
Category | ⇒ | Installation Language & Strings |
Milestone |
Added: |
So I guess this will not make 3.4.1 if the language is already frozen again? :-(
Specially if no PR was made... Also, installation ini files changes requires a specific freeze to get as many as possible ready before the next release.
@infograf768 - Well I cant make a PR as:
I dont know which files, in what languages, you wish me to change, last time I tried to change a language it ended up in a million different people asking for a million different tiny changes
Probably best for @brianteeman to provide some non developer fluffy english words instead of anything I could come up with
@PhilETaylor @brianteeman please have a look into #6721
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-04-09 12:59:44 |
Status | Closed | ⇒ | New |
Status | New | ⇒ | Closed |
Closed_Date | 2015-04-09 12:59:44 | ⇒ | 2015-04-09 23:51:49 |
I am trying to think of the right wording that is appropriate for local and
remote installs
On 27 January 2015 at 22:27, Phil Taylor notifications@github.com wrote:
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/