6

17 comments

[–] 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

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

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.

That's really good to know!

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

I loved it. As a start, I'm taking screen shots as I go and I plan up to come up with some sort of Installation guide (IG) for noobs like me - though I don't have any timeline for this. The notes in your pastebin is really going to help in extending the IG.