There was only one issue, my tests would not work due to permission issues! I don’t set up new databases like that every day, so I looked up some tutorials and followed this one. I’m presenting you three stories of my database migration struggles with some valuable lessons learned along the way. Well… it wasn’t an entirely smooth transition. I’ve been working on my open source side project Invertimoįor a while and at some point I decided toĬhange the db engine from SQLite to PostgreSQL. At some point it’s time to pick up a DB like MySQL or PostgreSQL that is more suitable for this purpose. It’s a great choice for initial development and for testing,īut not if you want to run multiple app servers, e.g. Either way, there ARE going to be services that only support SQLite or only MySQL/Postgres, so 100% DB consolidation is not a factor, but there are far more services that support only SQLite than those that don't support SQLite at all.Django - growing up from SQLite to PostgreSQLĭjango by default comes with SQLite as a database. consolidate as much usage as possible in case you have applications that don't support SQLite? you can manage multiple databases in "one place", 2. Or should you stick with MySQL/Postgres anyway for the services that DO support it because 1. easy backup & restore (with MySQL/Postgres, I need to dump, upgrade, then restore the database should I need to update its version), and 3. So the question is, should you? Should you ditch MySQL/Postgres and just use SQLite files for 1. Thus, even when you self-host blogs like me, you can realistically just use SQLite as the backing database for ALL of your services. even ones that aren't, can easily be cached to hell (e.g. most self-hosted services are meant to be only used across a limited number of people (maybe just you or your family), and 2. not SQLite) "scale" better across concurrent accesses however, given that 1. Obviously, client/server models of databases (i.e. ![]() With this in mind, whether you choose MySQL or Postgres, when you have a number of services backed by databases, you're likely to have some that use MySQL/Postgres but others that use SQLite (because it doesn't support anything else). ![]() Some may use MySQL, some may use Postgres, but almost all of them support SQLite. What Is SelfHosted, As it pertains to this subreddit?Īlmost all of the projects (let alone self-hosted ones) out there use one or more of the three above databases as the "source of truth". Also include hints and tips for less technical readers. We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Service: Blogger - Alternative: WordPress Service: Google Reader - Alternative: Tiny Tiny RSS ![]() Service: Dropbox - Alternative: Nextcloud While you're here, please Read This FirstĪ place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |