Re: Proposal: provide postgresql powered full-text search in djangoproject.com

2017-05-08 Thread Marc Tamlyn 
I'm not sure I see the benefit here. The strength and purpose of postgres
FTS is that you can combine some FTS behaviour with some relational queries
easily at the same time. I'm pretty sure our search requirements on dp.com
need that, so using a dedicated search provider is a better option.

On 7 May 2017 at 13:22, Florian Apolloner  wrote:

> On Sunday, May 7, 2017 at 12:45:27 PM UTC+2, Adam Johnson wrote:
>>
>> I guess we'd also have the benefit of not having to keep elasticsearch
>> running.
>>
>
> On the contrary, putting it into postgres means we have to care about it.
> Putting it into Elasticsearch means we can let our hoster take care about
> that.
>
>
>> But I'm afraid I'm not familiar with Postgres. Is the FTS in Postgres
>> mostly equivalent to ES, or will some kinds of search queries be affected?
>>
>
> For the queries we use I think we can get pretty much equivalent results.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-developers/ecd3a1ea-63d9-430c-af79-
> 951022fec138%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMwjO1GFKbXyebkqmok_RYv3Hywq%3DfwXrfzXcgFxtZU7-Ez5%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: provide postgresql powered full-text search in djangoproject.com

2017-05-08 Thread Adam Johnson 
>
>  I'm pretty sure our search requirements on dp.com need that,


s/need/don't need/ ? 😉

On 8 May 2017 at 13:59, Marc Tamlyn  wrote:

> I'm not sure I see the benefit here. The strength and purpose of postgres
> FTS is that you can combine some FTS behaviour with some relational queries
> easily at the same time. I'm pretty sure our search requirements on dp.com
> need that, so using a dedicated search provider is a better option.
>
> On 7 May 2017 at 13:22, Florian Apolloner  wrote:
>
>> On Sunday, May 7, 2017 at 12:45:27 PM UTC+2, Adam Johnson wrote:
>>>
>>> I guess we'd also have the benefit of not having to keep elasticsearch
>>> running.
>>>
>>
>> On the contrary, putting it into postgres means we have to care about it.
>> Putting it into Elasticsearch means we can let our hoster take care about
>> that.
>>
>>
>>> But I'm afraid I'm not familiar with Postgres. Is the FTS in Postgres
>>> mostly equivalent to ES, or will some kinds of search queries be affected?
>>>
>>
>> For the queries we use I think we can get pretty much equivalent results.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-developers+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/django-developers/ecd3a1ea-63d9-430c-af79-951022fec138%
>> 40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-developers/CAMwjO1GFKbXyebkqmok_RYv3Hywq%
> 3DfwXrfzXcgFxtZU7-Ez5%3DA%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Adam

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM2w90gRXxLwJ30Bz1sutQxM%3DFdZWpQgNcsmp5DemOSvFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: provide postgresql powered full-text search in djangoproject.com

2017-05-08 Thread Marc Tamlyn 
Yes, don't need that sorry.

On 8 May 2017 at 14:40, Adam Johnson  wrote:

>  I'm pretty sure our search requirements on dp.com need that,
>
>
> s/need/don't need/ ? 😉
>
> On 8 May 2017 at 13:59, Marc Tamlyn  wrote:
>
>> I'm not sure I see the benefit here. The strength and purpose of postgres
>> FTS is that you can combine some FTS behaviour with some relational queries
>> easily at the same time. I'm pretty sure our search requirements on
>> dp.com need that, so using a dedicated search provider is a better
>> option.
>>
>> On 7 May 2017 at 13:22, Florian Apolloner  wrote:
>>
>>> On Sunday, May 7, 2017 at 12:45:27 PM UTC+2, Adam Johnson wrote:

 I guess we'd also have the benefit of not having to keep elasticsearch
 running.

>>>
>>> On the contrary, putting it into postgres means we have to care about
>>> it. Putting it into Elasticsearch means we can let our hoster take care
>>> about that.
>>>
>>>
 But I'm afraid I'm not familiar with Postgres. Is the FTS in Postgres
 mostly equivalent to ES, or will some kinds of search queries be affected?

>>>
>>> For the queries we use I think we can get pretty much equivalent results.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django developers (Contributions to Django itself)" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to django-developers+unsubscr...@googlegroups.com.
>>> To post to this group, send email to django-developers@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/django-developers.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/django-developers/ecd3a1ea-63d9-430c-af79-951022fec138%4
>>> 0googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-developers+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/django-developers/CAMwjO1GFKbXyebkqmok_RYv3Hywq%3DfwXrfz
>> XcgFxtZU7-Ez5%3DA%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Adam
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-developers/CAMyDDM2w90gRXxLwJ30Bz1sutQxM%
> 3DFdZWpQgNcsmp5DemOSvFQ%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMwjO1Egq8xasdZ2eRxvX2Qb6mH7ygv2xcx0FmUXQyc4kjW5WA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: provide postgresql powered full-text search in djangoproject.com

2017-05-08 Thread Tobias McNulty 
I'm no FTS expert, but based just on the facts raised in this thread, if
using Postgres FTS

   1. would not break existing nor potential search needs (in fact it might
   expand the functionality available) and
   2. would allow eliminating an entire service from the infrastructure

that seems like a net win to me and as such at least worth exploring
further. That is not to say I think we should commit to switching, but if
we have volunteers who are excited to flesh out this proposal with some
code and understand there's no guarantee it will actually get merged, I
don't (yet) see a reason to say no.

Tobias


*Tobias McNulty*Chief Executive Officer

tob...@caktusgroup.com
www.caktusgroup.com

On Mon, May 8, 2017 at 10:07 AM, Marc Tamlyn  wrote:

> Yes, don't need that sorry.
>
> On 8 May 2017 at 14:40, Adam Johnson  wrote:
>
>>  I'm pretty sure our search requirements on dp.com need that,
>>
>>
>> s/need/don't need/ ? 😉
>>
>> On 8 May 2017 at 13:59, Marc Tamlyn  wrote:
>>
>>> I'm not sure I see the benefit here. The strength and purpose of
>>> postgres FTS is that you can combine some FTS behaviour with some
>>> relational queries easily at the same time. I'm pretty sure our search
>>> requirements on dp.com need that, so using a dedicated search provider
>>> is a better option.
>>>
>>> On 7 May 2017 at 13:22, Florian Apolloner  wrote:
>>>
 On Sunday, May 7, 2017 at 12:45:27 PM UTC+2, Adam Johnson wrote:
>
> I guess we'd also have the benefit of not having to keep elasticsearch
> running.
>

 On the contrary, putting it into postgres means we have to care about
 it. Putting it into Elasticsearch means we can let our hoster take care
 about that.


> But I'm afraid I'm not familiar with Postgres. Is the FTS in Postgres
> mostly equivalent to ES, or will some kinds of search queries be affected?
>

 For the queries we use I think we can get pretty much equivalent
 results.

 --
 You received this message because you are subscribed to the Google
 Groups "Django developers (Contributions to Django itself)" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to django-developers+unsubscr...@googlegroups.com.
 To post to this group, send email to django-developers@googlegroups.com
 .
 Visit this group at https://groups.google.com/group/django-developers.
 To view this discussion on the web visit https://groups.google.com/d/ms
 gid/django-developers/ecd3a1ea-63d9-430c-af79-951022fec138%4
 0googlegroups.com
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django developers (Contributions to Django itself)" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to django-developers+unsubscr...@googlegroups.com.
>>> To post to this group, send email to django-developers@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/django-developers.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/django-developers/CAMwjO1GFKbXyebkqmok_RYv3Hywq%3DfwXrfz
>>> XcgFxtZU7-Ez5%3DA%40mail.gmail.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Adam
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-developers+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/django-developers/CAMyDDM2w90gRXxLwJ30Bz1sutQxM%3DFdZWpQ
>> gNcsmp5DemOSvFQ%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> T

Re: Proposal: django.contrib.mysql

2017-05-08 Thread Adam Johnson 
Update: I decided not to try merge django-mysql as django.contrib.mysql
because I think it's an advantage to have it as a separate package. As it
stands, it supports Django 1.8 to 1.11 for all features, so people who
aren't on cutting edge Django can still use all its features. Contrast that
with django.contrib.postgres, where new features are only available on new
Django versions, with their fixed release cycle.

Sérgio, django-mysql already fully supports MySQL 5.7's JSON type with its
JSONField:
https://django-mysql.readthedocs.io/en/latest/model_fields/json_field.html
. Try that.

On 4 May 2017 at 18:41, johannes mtwengi  wrote:

> i would like to be part and start foundations coding giving back
>
> On Friday, March 4, 2016 at 1:09:00 AM UTC+2, Adam Johnson wrote:
>>
>> The *django.contrib.postgres* docs state:
>>
>> There is no fundamental reason why (for example) a contrib.mysql module
>>> does not exist
>>
>>
>> *Well...* over the past year and a bit I've been developing
>> Django-MySQL. It has a ton of features specific to MySQL and/or MariaDB.
>> For a quick tour of the features, see the exposition in the documentation:
>> https://django-mysql.readthedocs.org/en/latest/exposition.html (it's not
>> all suitable for Django core, some is kinda hacky (but well tested!))
>>
>> At DUTH in November I talked with Josh Smeaton about posting a suggestion
>> here for *django.contrib.mysql*. Since then, I've simply been
>> lazy/forgetful, but now I'm here getting round to it.
>>
>> I'm also a bit motivated by my recent completion of its *JSONField* for
>> MySQL 5.7+ which is very similar to the *contrib.postgres* one, copying
>> and adapting large parts of code from Marc Tamlyn's work. We all know how
>> much everyone loves JSON these days. If anything, this could be a core
>> field rather than a *contrib* one - Oracle and SQLite also have JSON
>> capabilities now. JSON everywhere!
>>
>> Anyway... what's the interest in *django.contrib.mysql*? And where woudl
>> we go from here...
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/django-developers/sAgYOqBUvgI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-developers/274f0162-f345-4946-ad56-
> 328c20bdafff%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Adam

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM38mE4xiepXuFiR3cdmeqsXjyPZeZuvgibCyWtutkuDNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: A New Design for the "Congratulations!" Page

2017-05-08 Thread Darius 
Hi Tim,

Here are my thoughts:


   1. The main message "it worked" has given his placement to a log, 
   leaving the user to focus on the image when the page loads. This can 
   leave the user wondering if it worked until they see the lwords "The 
   Install Worked". Congratulations. reload the page, what is the first thing 
   your eyes will focus on? 
   2. The simple (it worked) message is now a longer "The Install Worked", 
   congratulations. Keep in mind the word "Worked" is the main message
   3. The current design delivers the message clearly. It worked. Nothing 
   more, nothing less.
   

The new design offers additional info and links in the bottom of the page 
which is really nice and helpful for the new users. So well done there.

I would keep the current simple message "it worked" and also, more 
importantly, its placement. As a new user, nothing is more rewarding to 
immediately see it worked message as soon as the page loads.

And thank you for all your efforts.

Darius


On Tuesday, 18 April 2017 11:44:13 UTC-4, Tim Allen wrote:
>
> I've had the privilege of introducing Django to many people over the past 
> several years. A recurring theme I have noticed is that once a new Django 
> developer reaches the "It Worked!" page, the inevitable next question is, 
> "now what?"
>
> It struck me that this page is valuable real estate for the newcomer. 
> Since my eye for design is practically non-existent, I worked with a 
> talented colleague and we came up with an idea to replace the "It Worked!" 
> page. Here is a link:
>
> https://chadwhitman.github.io/congrats/django/
>
> Some of the goals we wanted to achieve:
>
>- Provide a friendly design using the same themes as the Django 
>Project website.
>- Ensure the developer is using the current version of Django. Many 
>tutorials found through Google are for older versions of Django.
>- Provide links to the current versions of the documentation, 
>introductory polling tutorial, and community.
>- Include the release notes for the current version of Django.
>- Focus on the new Django developer, as many seasoned Django 
>developers will using other methods for starting projects.
>
>
> While it is doubtful that many would see this screen on a small device, it 
> is fully responsive as well. It is self-contained, with minified CSS and 
> SVG icons, and a total size of 20k, so it shouldn't provide much bloat at 
> all.
>
> We're looking for feedback, and if the community thinks it is an 
> improvement, we'll be happy to work on a pull request. A big hat tip to my 
> colleague Chad Whitman for his design talents.
>
> Regards,
>
> Tim
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/020af4a6-4cd2-4489-8eb2-1de211bf54e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: provide postgresql powered full-text search in djangoproject.com

2017-05-08 Thread Tim Graham 
I agree that eliminating elasticsearch could be a simplification win from a 
maintenance perspective. For example, I spent some hours a few months ago 
debugging a problem with a new version of elasticsearch that caused our 
cluster to run out of memory and lock up every ~24 hours. Also, not having 
to set up elasticsearch to contribute to the docs.djangoproject.com search 
is nice. On the other hand, I wonder how moving the search load to 
PostgreSQL will effect server load, disk usage, etc. 

On Monday, May 8, 2017 at 11:14:58 AM UTC-4, Tobias McNulty wrote:
>
> I'm no FTS expert, but based just on the facts raised in this thread, if 
> using Postgres FTS
>
>1. would not break existing nor potential search needs (in fact it 
>might expand the functionality available) and
>2. would allow eliminating an entire service from the infrastructure
>
> that seems like a net win to me and as such at least worth exploring 
> further. That is not to say I think we should commit to switching, but if 
> we have volunteers who are excited to flesh out this proposal with some 
> code and understand there's no guarantee it will actually get merged, I 
> don't (yet) see a reason to say no.
>
> Tobias
>
>
> *Tobias McNulty*Chief Executive Officer
>
> tob...@caktusgroup.com 
> www.caktusgroup.com
>
> On Mon, May 8, 2017 at 10:07 AM, Marc Tamlyn  > wrote:
>
>> Yes, don't need that sorry.
>>
>> On 8 May 2017 at 14:40, Adam Johnson > wrote:
>>
>>>  I'm pretty sure our search requirements on dp.com need that,
>>>
>>>
>>> s/need/don't need/ ? 😉 
>>>
>>> On 8 May 2017 at 13:59, Marc Tamlyn > 
>>> wrote:
>>>
 I'm not sure I see the benefit here. The strength and purpose of 
 postgres FTS is that you can combine some FTS behaviour with some 
 relational queries easily at the same time. I'm pretty sure our search 
 requirements on dp.com need that, so using a dedicated search provider 
 is a better option.

 On 7 May 2017 at 13:22, Florian Apolloner >>> > wrote:

> On Sunday, May 7, 2017 at 12:45:27 PM UTC+2, Adam Johnson wrote:
>>
>> I guess we'd also have the benefit of not having to keep 
>> elasticsearch running.
>>
>
> On the contrary, putting it into postgres means we have to care about 
> it. Putting it into Elasticsearch means we can let our hoster take care 
> about that.
>   
>
>> But I'm afraid I'm not familiar with Postgres. Is the FTS in Postgres 
>> mostly equivalent to ES, or will some kinds of search queries be 
>> affected?
>>
>
> For the queries we use I think we can get pretty much equivalent 
> results.
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to django-develop...@googlegroups.com .
> To post to this group, send email to django-d...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/ecd3a1ea-63d9-430c-af79-951022fec138%40googlegroups.com
>  
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

 -- 
 You received this message because you are subscribed to the Google 
 Groups "Django developers (Contributions to Django itself)" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to django-develop...@googlegroups.com .
 To post to this group, send email to django-d...@googlegroups.com 
 .
 Visit this group at https://groups.google.com/group/django-developers.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/django-developers/CAMwjO1GFKbXyebkqmok_RYv3Hywq%3DfwXrfzXcgFxtZU7-Ez5%3DA%40mail.gmail.com
  
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> -- 
>>> Adam
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Django developers (Contributions to Django itself)" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to django-develop...@googlegroups.com .
>>> To post to this group, send email to django-d...@googlegroups.com 
>>> .
>>> Visit this group at https://groups.google.com/group/django-developers.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/django-developers/CAMyDDM2w90gRXxLwJ30Bz1sutQxM%3DFdZ