New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow omitting DB container #1490
Comments
Could you please say more about the environment in which you don't need a database please? |
TYPO3 with SQLite Database will not need a mariadb container. |
@maddy2101 Not a config option, but I asked how to do that on Stack Overflow before: https://stackoverflow.com/questions/54252928/running-ddev-without-database Just in case you need a solution until the issue is solved. |
Just a note about sqlite3: My own experience trying to use it in a multiuser environment with Drupal was dismal, not recommended. Hoping for better with TYPO3! |
+1 to this: I'm using ddev to run TYPO3 and symfony projects. Both run fine with sqlite, and some symfony projects don't even need a db at all. In those cases the db container is unused complexity. It would be great if it could be turned off by allowing 'db' as value for 'omit_containers' config option. |
Chiming in: https://contribkanban.com/ is D8 and run on SQLite for ~1 year without problems. |
It's not too terribly hard to omit the db container. The thing that gets more difficult is re-doing the automatic settings.ddev.php generation and such. And adding new config that tells it that stuff, etc. |
I wonder if the scope is important. a) The original request which is "My App simply does not need a database". Case A seems to be the more prominent one to me. Case B seems a bit like getting out of ddev's original scope - making things easy for developers. So while it's nice that you can run your CMS/App with SQlite or Postgres or Orcale or MSSQL in my opinion this gets out of hand. This is where I'd personally draw the line. |
@Lefaux @rfay |
Yeah, this is labeled "prioritized" for that same reason. People want it. It's not too hard, it's just that there's start code and stuff that's explicit about the db container. |
Let's make sure to solve the problem with leakage of omit_containers into project config.yaml when working on this, #1456. If we could solve that in a general way, too, we could put more things in global_config.yaml. |
For those of you who have been eager to get this, I'd love to have you try this out and see if it will meet your needs. The artifacts are posted at #1819 (comment) - @Lefaux @lolli42 @maddy2101 |
Is your feature request related to a problem? Please describe.
Not really a problem, just ecological and performance related concerns. I'd like not to boot up any database, if my project doesn't call for one.
Describe the solution you'd like
A config option, that allows to omit the configuration and creation of a DB container.
The text was updated successfully, but these errors were encountered: