Improve setup task, by making it less dangerous

Created by: riyad

• adds a warning prompt before actually running the setup task
• rename gitlab:app:setup to gitlab:setup
• remove setup task from maintenance docs (setup is not maintenance!)

In succession of #2338 Actually fixes #1844 (closed)

Created by: dzaporozhets

Nice one

By Administrator on 2013-01-17T20:40:53 (imported from GitLab project)

By Administrator on 2013-01-17T20:40:53 (imported from GitLab)

Created by: arosenhagen

can we please still pass a variable to explicitly run the db-setup to

bundle exec rake gitlab:setup

otherwise the setup is not scriptable (with chef in my case) because of the prompt. In such cases it's save to wipe an existing db.

By Administrator on 2013-01-25T19:29:26 (imported from GitLab project)

By Administrator on 2013-01-25T19:29:26 (imported from GitLab)

Created by: lboynton

to adding an option to bypass this check so that I can use puppet.

By Administrator on 2013-01-28T14:14:34 (imported from GitLab project)

By Administrator on 2013-01-28T14:14:34 (imported from GitLab)

Created by: pfiled

I worked around this in my puppet manifest by running the 3 tasks gitlab:setup runs instead of the umbrella task:

bundle exec rake db:setup db:seed_fu gitlab:enable_automerge RAILS_ENV=production

By Administrator on 2013-03-18T17:09:40 (imported from GitLab project)

By Administrator on 2013-03-18T17:09:40 (imported from GitLab)