1.
Managing users, passwords and privileges (grants) is all done in SQL. In fact all phpmyadmin does is add a pretty interface on top of the SQL itself. But SQL is pretty easy to learn and all documentation you might need is online.
An example
Create a database "trainingdb",
Create a user training with password letmein (a very bad password to use in real life)
And give that user all rights on the above database (too much, but it means the user has no rights on other databases - You can be much more granular)
[pre]
CREATE DATABASE trainingdb DEFAULT CHARACTER SET = `utf8`;
GRANT ALL ON trainingdb.* TO 'training'@'localhost' IDENTIFIED BY 'letmein';
[/pre]
You can also create a user and grant privileges in separate commands, manage passwords etc. The above is the quick way to do it all in a couple of SQL statement.
Ref:
[
dev.mysql.com...]
[
dev.mysql.com...]
[
dev.mysql.com...]
2.
I'm not entirely sure what you mean by "Secondly, if a website does not offer PHP Admin".
IMHO phpmyadmin should not be on production systems.
The question more to the point is however; does your server have (on the same or on a different machine) mysql available for your use ? If so and I'll assume that you 're not going to be managing that mysql: aks those who manage it for the details.
Once you have created a table on your test/home machine, use
SHOW CREATE TABLE tablename;
That shows you the CREATE TABLE command you can use on your production database to create the table (without content) without a gui to help you.
Running a webserver that has a backend database that's at home (I'll assume over a typical connection) doesn't sound like a success formula to me. Too much can go wrong.
