Use sqlite backend by default to make installation easier

Installing PostgreSQL and setting up its authentication can be in some cases tricky. This is a problem for new contributors, who want to contribute a small fix, but the time and complexity to set up the environment is too high.

By using sqlite by default, we could make the installation of a local python.org version trivial and facilitate contributors from people new to the project.

This could be done by using a sqlite connection in the DATABASES section of pydotorg/settings/local.py. This shouldn’t affect production or other servers afaik (can you please confirm @berkerpeksag ?)

There is one part of the jobs board that depends on features only available in the PostgreSQL backend. For now, we could simply add a message if this part is accessed with a sqlite database, warning the user that this feature is only available with PostreSQL.

[berkerpeksag]

Yeah, I’m personally not fan of the container option too, but if it makes someone’s life easier I’d be willing to offer it as an alternative to the Vagrant based and/or manual installation options.

[lingster]

Why not setup a docker file so postgres can be spun up with minimal effort?