6

17 comments

[–] curious [OP] 0 points (+0|-0) Edited

Thank you so much @E-werd.

So, to conclude.

  1. I won't touch the said file (debian.cnf)

  2. Run the script below as you have mentioned.

mysql -u root -p
CREATE DATABASE throat;
CREATE USER 'throat'@localhost IDENTIFIED BY 'Pass1234';
GRANT ALL PRIVILEGES ON throat.* TO 'throat'@localhost;
exit

One last question: Is the mysql password the same as the root password? It's asking me for a password when I run mysql -u root -p. Sorry if you found the question stupid. I'm really dumb in this.

[–] E-werd 2 points (+2|-0)

There's linux root (as defined in /etc/passwd, the super user account on the system) and there's the mysql/mariadb root. They're two different things, the latter being specifically for mysql/mariadb.

[–] curious [OP] 0 points (+0|-0) Edited

Thanks again @E-werd. Got it.

I'm almost there.

cd scripts
./install.py
cd ..
nano wsgi.py
#socketio.run(app, debug=True, host='0.0.0.0')

When I run ./install.py, I get bash: ./install.py: No such file or directory. The install.py isn't there obviously as can be seen here.

These are the only files available in the scripts directory.

__fix.py admins.py clean_subs.py defaults.py migrate.py

  • What should I do now? It's a clean install btw.

  • EDIT: Would it be save to make a copy of the install.py file?

[–] E-werd 1 points (+1|-0)

So what you're running into now is a dated form of the guide. The file install.py has been replaced with migrate.py and can be used in the same way. This also gets used later on if and when the structure of the database changes. You'll know to use it if you see errors relating to missing fields.

Here's the most up-to-date guide I have specifically for mysql/mariadb. Note that I've started using Alpine Linux now as that will ultimately be what I use if/when I finally get around to learning Docker as it's a tried-and-true linux distribution for this purpose. https://pastebin.com/Pdqh2Ji9

Also, if you're interested in using MySQL/MariaDB, Postgresql, or SQLite, then you might want to look at this link. We recently moved to Postgresql for the live site for performance and data integrity reasons, and while we were at it we made sure SQLite was working as well. SQLite is actually a great way to get a quick test or development instance running without configuring a database. https://pastebin.com/zFfLuMV6