kallithea Files · rhodecode/tests/scripts/create

Files @ fc63a1d93803

Branch filter:

Location: kallithea/rhodecode/tests/scripts/create_rc.sh - annotation

fc63a1d93803 1.3 KiB text/x-sh Show Source Show as Raw Download as Raw

Marcin Kuzminski

Switched order of actions when doing repo rescan.

doing invalidation after repository scan is not optimal.
In case of big repository we first create an instance then invalidate
cache that we don't actually need. Reversing this order prevents that

d753f2da69f2
d753f2da69f2
29630805893d
d753f2da69f2
d753f2da69f2
92822bd2e88a
92822bd2e88a
92822bd2e88a
92822bd2e88a
92822bd2e88a
92822bd2e88a
92822bd2e88a
92822bd2e88a
92822bd2e88a
92822bd2e88a
92822bd2e88a

psql -U postgres -h localhost -c 'drop database if exists rhodecode;'
psql -U postgres -h localhost -c 'create database rhodecode;'
paster setup-rhodecode rc.ini --force-yes --user=marcink --password=qweqwe --email=marcin@python-blog.com --repos=/home/marcink/repos
API_KEY=`psql -R " " -A -U postgres -h localhost -c "select api_key from users where admin=TRUE" -d rhodecode | awk '{print $2}'`
echo "run those after running server"
paster serve rc.ini --pid-file=rc.pid --daemon
sleep 3
rhodecode-api --apikey=$API_KEY --apihost=http://127.0.0.1:5001 create_user username:demo1 password:qweqwe email:demo1@rhodecode.org
rhodecode-api --apikey=$API_KEY --apihost=http://127.0.0.1:5001 create_user username:demo2 password:qweqwe email:demo2@rhodecode.org
rhodecode-api --apikey=$API_KEY --apihost=http://127.0.0.1:5001 create_user username:demo3 password:qweqwe email:demo3@rhodecode.org
rhodecode-api --apikey=$API_KEY --apihost=http://127.0.0.1:5001 create_users_group group_name:demo12
rhodecode-api --apikey=$API_KEY --apihost=http://127.0.0.1:5001 add_user_to_users_group usersgroupid:demo12 userid:demo1
rhodecode-api --apikey=$API_KEY --apihost=http://127.0.0.1:5001 add_user_to_users_group usersgroupid:demo12 userid:demo2
echo "killing server"
kill `cat rc.pid`
rm rc.pid