Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
AKPlanning
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
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
KIF
AKPlanning
Commits
62b87e15
Commit
62b87e15
authored
3 years ago
by
Benjamin Hättasch
Browse files
Options
Downloads
Patches
Plain Diff
Apply 2 suggestion(s) to 1 file(s)
parent
81b9b420
No related branches found
Branches containing commit
No related tags found
1 merge request
!91
Add Dockerfile and dependencies
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
INSTALL.md
+2
-2
2 additions, 2 deletions
INSTALL.md
with
2 additions
and
2 deletions
INSTALL.md
+
2
−
2
View file @
62b87e15
...
@@ -208,7 +208,7 @@ On the first start, the database must be initialized (the Tables created and so
...
@@ -208,7 +208,7 @@ On the first start, the database must be initialized (the Tables created and so
When updating the project the database must be migrated.
When updating the project the database must be migrated.
Both are done using the
`migrate`
command.
Both are done using the
`migrate`
command.
This can be done manually by runningthe following command after the container has started:
This can be done manually by running
the following command after the container has started:
`docker-compose exec -it akplanning-server ./manage.py migrate`
`docker-compose exec -it akplanning-server ./manage.py migrate`
It can also be done automatically on each container start by setting
`AUTO_MIGRATE_DB`
to the string
`true`
It can also be done automatically on each container start by setting
`AUTO_MIGRATE_DB`
to the string
`true`
...
@@ -227,7 +227,7 @@ Using the environment variables `DJANGO_SUPERUSER_{USERNAME,EMAIL,PASSWORD}`.
...
@@ -227,7 +227,7 @@ Using the environment variables `DJANGO_SUPERUSER_{USERNAME,EMAIL,PASSWORD}`.
The second way is to run the following command after the container has started:
The second way is to run the following command after the container has started:
`docker-compose exec -it akplanning-server ./manage.py createsuperuser`
`docker-compose exec -it akplanning-server ./manage.py createsuperuser`
### Extra dj
n
ago settings
### Extra dja
n
go settings
For simple cases you can pass environment variables starting with
`EXTRA_DJANGO_SETTING`
.
For simple cases you can pass environment variables starting with
`EXTRA_DJANGO_SETTING`
.
The content of such variables is written into python files, which are loaded as settings.
The content of such variables is written into python files, which are loaded as settings.
...
...
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