delta/gitlab/gitlab-ce.git/app/controllers/explore, branch replace_explore_projects.feature

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

Merge branch 'tc-fix-private-subgroups-shown' into 'security'

2017-05-10T14:48:18+00:00


Use GroupsFinder to find subgroups the user has access to

See merge request !2096

Merge branch 'snippets-finder-visibility' into 'security'

2017-05-10T14:48:18+00:00

Refactor snippets finder & dont return internal snippets for external users

See merge request !2094

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

Add filter and sorting to dashboard groups page

2017-03-01T13:39:59+00:00

Signed-off-by: Dmitriy Zaporozhets

Don't perform Devise trackable updates on blocked User records

2017-02-10T16:51:14+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.