onepercentclub/bluebottle

Bluebottle

bluebottle's Issues

Write a howto to setup Bluebottle

Django 3

I see there is lots of work going on for Python 3 support at #4292

I tried my hand at leveraging off that to see if I can get Django 3 working, and am mostly successful in getting it operational enough to explore the app locally. I am using django-compat-patcher to do a lot of the heavy lifting of cross-Django-version compatibility.

Latest CI result at https://travis-ci.org/github/jayvdb/bluebottle/jobs/732862786
Summary: of 1228 tests, 225 failures & 184 errors.

A lot of the errors are repetitive, and most are due to the dependencies being pinned to Django 1.x compatible versions. I'm trying to unpin only dependencies that really need unpinning, so-as to reduce the variability between Django 1.x and Django 3.x versions of bluebottle.

Other dependent PRs / branches

• #3387 Remove SaaS service salesforce (this isnt on any branch; it disappeared?)
• onepercentclub/django-tenant-extras#60 - Django 2 & 3 support with tests
• django-fluent/django-fluent-contents#107 - sort-thumbnail induced bug
• philippbosch/django-geoposition#110 - Django 2 & 3 support
• https://github.com/jayvdb/django-tenant-schemas/commits/migrate-fix (hack around conflict in --skip-checks, possibly caused by django-compat-patcher)
• https://github.com/jayvdb/bluebottle/commits/dj3-v2 - 60+ commits and counting, of varying messiness - most notably removing django-jet, which turned into a SaaS service for Django 2+. IMO their licensing fees are not money well spent, as similar exists in the OSS world.
• https://github.com/jayvdb/compat-patcher-core/tree/i1 - semi-complete fix for https://github.com/jayvdb/compat-patcher-core/tree/i1

Why Django 3?

1. Because most dependency projects are already dropping Django 2, so if there are problems with porting to Django 2 it would be harder to get help,
2. All top-tier distros have dropped Django 2 from their current or pending release, and
3. I expect the Django 3 effort to take a while to stablise and before existing bluebottle production systems would be ready to switch to Django 3, and by then Django 2 will be even more dead.
4. Creating migration across major Django versions is quite a bit of effort. May as well skip one.

Obviously most of this needs to wait until the Python 3 work lands, but I'd like to know the best way to structure this in order to get favourable reviews to get things merged early.

I'd like to eventually be running another Travis job for Django 3, so that Django 1.x and Django 3.x are co-existing in the repo until you're ready to switch off Django 1.x . Many of my patches are already able to co-exist on Django 1.x, using fallbacks where necessary. The Django 3 job could be allowed to fail, so that it doesnt halt ongoing development of the project.

Test

Testing webhook

Required packages

• Please add these packages as pre-requirement in Linux machines to README file:

libpqxx, graphviz

These are not installed on archlinux

• python2 setup.py test and virtualenv2 env

Is BlueBottle still under development?

Hi there

We're going to run a crowdfunding website. There are not many options out there, but there are some apps as in: Bluebottle, Goteo (php), Catarse (ruby), openTilt (ruby), Thrinica (SAAS).

Anyway, Bluebottle is one of them that we see have not been under heavy development for years. Would you work on it again?

Do you recommend it as base of our website?