Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
steering
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
AURA
steering
Commits
f75037c7
Commit
f75037c7
authored
2 years ago
by
Ernesto Rico Schmidt
Browse files
Options
Downloads
Patches
Plain Diff
Clarify the loading the fixtures
parent
6a9e9690
No related branches found
No related tags found
No related merge requests found
Pipeline
#1785
passed
2 years ago
Stage: build
Stage: release
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.rst
+19
-5
19 additions, 5 deletions
README.rst
with
19 additions
and
5 deletions
README.rst
+
19
−
5
View file @
f75037c7
...
@@ -25,15 +25,25 @@ Then, you can setup the database::
...
@@ -25,15 +25,25 @@ Then, you can setup the database::
$ docker compose run django ./manage.py migrate
$ docker compose run django ./manage.py migrate
And load the fixtures::
You can the load all the fixtures. This loads data for the authentication
(users, groups and permissions) and for the program app (categories, funding
categories, hosts, languages, music focus, recurrence rules, shows, topics and
types).
This provides enough data to get started::
$ docker compose run django ./manage.py loaddata fixtures/*/*.json
$ docker compose run django ./manage.py loaddata fixtures/*/*.json
Or
, if you prefer, you can just create a super user after setting up
the
Alternatively
, if you prefer, you can just create a super user after setting up
database::
the
database::
$ docker compose run django python manage.py createsuperuser
$ docker compose run django python manage.py createsuperuser
The only required fixtures are the recurrence rules, these are needed to create
schedules::
$ docker compose run django ./manage.py loaddata fixtures/program/rrule.json
Then, you can create a RSA Key and the clients for `dashboard` and `tank`::
Then, you can create a RSA Key and the clients for `dashboard` and `tank`::
$ docker compose run django ./manage.py creatersakey
$ docker compose run django ./manage.py creatersakey
...
@@ -65,7 +75,6 @@ venv
...
@@ -65,7 +75,6 @@ venv
If you really don't want to use Docker, you can install `steering` using a
If you really don't want to use Docker, you can install `steering` using a
virtual environment.
virtual environment.
Create and activate a virtual environment::
Create and activate a virtual environment::
$ python3.9 -m venv venv
$ python3.9 -m venv venv
...
@@ -80,7 +89,6 @@ Then, you can setup the database::
...
@@ -80,7 +89,6 @@ Then, you can setup the database::
(venv) $ ./manage.py migrate
(venv) $ ./manage.py migrate
And load the fixtures::
And load the fixtures::
(venv) $ ./manage.py loaddata fixtures/*/*.json
(venv) $ ./manage.py loaddata fixtures/*/*.json
...
@@ -90,6 +98,11 @@ database::
...
@@ -90,6 +98,11 @@ database::
(venv) $ manage.py createsuperuser
(venv) $ manage.py createsuperuser
The only required fixtures are the recurrence rules, these are needed to create
schedules::
$ docker compose run django ./manage.py loaddata fixtures/program/rrule.json
Then, you can create a RSA Key and the clients for `dashboard` and `tank`::
Then, you can create a RSA Key and the clients for `dashboard` and `tank`::
(venv) $ ./manage.py creatersakey
(venv) $ ./manage.py creatersakey
...
@@ -99,3 +112,4 @@ Then, you can create a RSA Key and the clients for `dashboard` and `tank`::
...
@@ -99,3 +112,4 @@ Then, you can create a RSA Key and the clients for `dashboard` and `tank`::
Finally, you can start the development server::
Finally, you can start the development server::
(venv) $ ./manage.py runserver
(venv) $ ./manage.py runserver
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment