Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
beat.web
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
54
Issues
54
List
Boards
Labels
Milestones
Merge Requests
2
Merge Requests
2
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
beat
beat.web
Commits
73873c60
Commit
73873c60
authored
Apr 23, 2016
by
André Anjos
💬
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[readme] Some clean-up w.r.t. the scheduler removal
parent
885320af
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
24 deletions
+9
-24
README.rst
README.rst
+9
-24
No files found.
README.rst
View file @
73873c60
...
...
@@ -105,7 +105,7 @@ Documentation
Our
documentation
project
is
divided
in
3
parts
.
The
user
guide
is
the
only
one
which
is
automatically
built
as
part
of
the
``
buildout
``
procedure
.
The
API
and
administrators
guide
need
s
to
be
manually
compiled
if
required
.
administrators
guide
need
to
be
manually
compiled
if
required
.
To
build
the
API
documentation
,
just
do
::
...
...
@@ -142,7 +142,8 @@ For a simple (development) web server, the default settings on
working
directory
*
Run
with
full
debug
output
*
It
sets
the
working
BEAT
prefix
to
``./
prefix
``
*
A
single
user
,
called
``
admin
``
will
be
setup
into
the
system
*
A
single
user
,
called
``
user
``
(
password
``
user
``)
will
be
setup
into
the
system
If
you
need
to
tweak
these
settings
,
just
edit
the
file
``
beat
/
web
/
settings
/
settings
.
py
``.
You
may
consult
the
`
Django
documentation
`
_
...
...
@@ -240,9 +241,9 @@ Now start the localhost system::
You
may
inspect
this
programs
help
message
for
details
on
its
usage
and
options
.
Once
the
localhost
system
is
started
and
the
scheduler
is
properly
configured
,
you
may
open
a
browser
window
to
your
`
localhost
,
port
8000
<
http
://
127.0.0.1
:
8000
>`
_
,
to
get
started
with
your
locally
installed
platform
.
Once
the
localhost
system
is
started
you
may
open
a
browser
window
to
your
`
localhost
,
port
8000
<
http
://
127.0.0.1
:
8000
>`
_
,
to
get
started
with
your
locally
installed
platform
.
Localhost
with
``
DEBUG
=
False
``
...
...
@@ -255,35 +256,19 @@ development server with slightly different settings::
$ ./bin/localhost.py -v --settings=beat.web.settings.nodebug
Triggering a Scheduler Reconfiguration
======================================
If you modify the queue configuration on the Django administrative panel,
you'
ll
need
to
notify
the
scheduler
of
those
changes
.
You
can
trigger
a
scheduler
(
hot
)
re
-
configuration
using
the
following
command
-
line
program
::
$
./
bin
/
django
qconf
..
note
::
Optionally
,
you
may
also
visit
`
your
local
scheduler
page
<
http
://
127.0.0.1
:
8000
/
backend
/
scheduler
>`,
and
hit
the
(
green
)
button
that
says
"Send configuration to Scheduler"
.
It
has
the
same
effect
.
Unit Testing
------------
After installation, it is possible to run our suite of unit tests. To do so,
use::
$
./
bin
/
django
test
--
settings
=
beat
.
web
.
settings
.
test
-
v
2
$ ./bin/django test --settings=beat.web.settings.test -v
1
You may pass filtering criteria to just launch tests for a particular set of
``beat.web`` applications. For example, to run tests only concerning
``beat.web.toolchains``, run::
$
./
bin
/
django
test
--
settings
=
beat
.
web
.
settings
.
test
-
v
2
beat
.
web
.
toolchains
.
tests
$ ./bin/django test --settings=beat.web.settings.test -v
1
beat.web.toolchains.tests
To measure coverage, you must set an environment variable for nose::
...
...
@@ -300,7 +285,7 @@ Or, to generate an HTML report::
database from run to run. In order to do this, just specify the flag
``--keepdb`` when you run your tests::
$
./
bin
/
django
test
--
settings
=
beat
.
web
.
settings
.
test
-
v
2
--
keepdb
$ ./bin/django test --settings=beat.web.settings.test -v
1
--keepdb
In this case, Django will create and keep a test database called
``test.sql3`` on your current directory. You may delete it when you'
re
done
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment