delta/gitlab/gitlab-ce.git/app/controllers/explore/projects_controller.rb, branch docs/autodeploy-refactor

Use Prev/Next pagination for exploring projects

2017-08-14T11:53:42+00:00

This changes the pagination of the "Explore" pages so they use a simpler
pagination system that only shows "Prev" and "Next" buttons. This
removes the need for getting the total number of rows to display, a
process that can easily take up to 2 seconds when browsing through a
large list of projects.

Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/27390

Enable Style/DotPosition Rubocop :cop:

2017-06-21T13:48:12+00:00

ProjectsFinder should handle more options

2017-04-06T05:11:37+00:00

Extended ProjectFinder in order to handle the following options:
 - current_user - which user use
 - project_ids_relation: int[] - project ids to use
 - params:
   -  trending: boolean
   -  non_public: boolean
   -  starred: boolean
   -  sort: string
   -  visibility_level: int
   -  tags: string[]
   -  personal: boolean
   -  search: string
   -  non_archived: boolean

GroupProjectsFinder now inherits from ProjectsFinder.
Changed the code in order to use the new available options.

Eager load route & namespace in `Explore::ProjectsController`

2017-03-16T11:31:27+00:00

Fix /explore sorting (trending)

2017-01-26T18:01:06+00:00

Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/27044

Precalculate trending projects

2016-10-10T10:27:08+00:00

This commit introduces a Sidekiq worker that precalculates the list of
trending projects on a daily basis. The resulting set is stored in a
database table that is then queried by Project.trending.

This setup means that Unicorn workers no longer _may_ have to calculate
the list of trending projects. Furthermore it supports filtering without
any complex caching mechanisms.

The data in the "trending_projects" table is inserted in the same order
as the project ranking. This means that getting the projects in the
correct order is simply a matter of:

    SELECT projects.*
    FROM projects
    INNER JOIN trending_projects ON trending_projects.project_id = projects.id
    ORDER BY trending_projects.id ASC;

Such a query will only take a few milliseconds at most (as measured on
GitLab.com), opposed to a few seconds for the query used for calculating
the project ranks.

The migration in this commit does not require downtime and takes care of
populating an initial list of trending projects.

Refactor TrendingProjectsFinder to support caching

2016-10-05T14:39:03+00:00

== Public Projects

This finder class now _only_ returns public projects. Previously this
finder would also return private and internal projects. Including these
projects makes caching data much harder and less efficient. Meanwhile
including this data isn't very useful as very few users would be
interested in seeing projects they have access to as trending. That is,
the feature is more useful when you want to see what _other_ popular
projects there are.

== Caching

The data returned by TrendingProjectsFinder is now cached for a day
based on the number of months the data should be restricted to. The
cache is not flushed explicitly, instead it's rebuilt whenever it
expires.

== Timings

To measure the impact I changed the finder code to use the last 24
months instead of the last month. I then executed and measured 10
requests to the explore page. On the current "master" branch (commit
88fa5916ffa0aea491cd339272ed7437c3f52dc7) this would take an average of
2.43 seconds. Using the changes of this commit this was reduced to
around 1.7 seconds.

Fixes gitlab-org/gitlab-ce#22164

Use the configured Kaminari "per page" default

2016-03-19T21:37:54+00:00

Allow filtered dashboard/explore results to be paged. Fixes #14104

2016-03-10T02:03:28+00:00

Add option to show archived projects on dahsboard

2016-03-04T18:25:28+00:00

Signed-off-by: Dmitriy Zaporozhets