645a55f19b
The idea is that after each feature spec example, we block all incoming requests at the Rack level, go to the 'about:blank' page, and wait until the current requests reach 0. This should solve the problem where a request would end after database cleaner performed the database truncation. The problem was that a GET request can still lead to records creation (e.g. namespaces or routes). Signed-off-by: Rémy Coutable <remy@rymai.me> |
||
|---|---|---|
| .. | ||
| environments | ||
| initializers | ||
| locales | ||
| routes | ||
| README.md | ||
| application.rb | ||
| aws.yml.example | ||
| boot.rb | ||
| database.yml.env | ||
| database.yml.mysql | ||
| database.yml.postgresql | ||
| dependency_decisions.yml | ||
| environment.rb | ||
| gitlab.yml.example | ||
| karma.config.js | ||
| license_finder.yml | ||
| mail_room.yml | ||
| no_todos_messages.yml | ||
| resque.yml.example | ||
| routes.rb | ||
| secrets.yml.example | ||
| sidekiq.yml.example | ||
| sidekiq_queues.yml | ||
| unicorn.rb.example | ||
| unicorn.rb.example.development | ||
| webpack.config.js | ||
README.md
Configuration files Documentation
Note that most configuration files (config/*.*) committed into
gitlab-ce will not be used for
omnibus-gitlab. Configuration
files committed into gitlab-ce are only used for development.
gitlab.yml
You can find most of GitLab configuration settings here.
mail_room.yml
This file is actually an YML wrapped inside an ERB file to enable templated
values to be specified from gitlab.yml. mail_room loads this file first as
an ERB file and then loads the resulting YML as its configuration.
resque.yml
This file is called resque.yml for historical reasons. We are NOT
using Resque at the moment. It is used to specify Redis configuration
values instead.