Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
E
ensembl-k8s-manifests
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
2
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
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
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ensembl-web
ensembl-k8s-manifests
Commits
677ffc3c
Commit
677ffc3c
authored
1 year ago
by
Andres Veidenberg
Browse files
Options
Downloads
Patches
Plain Diff
Update secret.yaml
parent
f19bdd5b
No related branches found
No related tags found
1 merge request
!33
- No need for secrets.yml for ensembl-client
Pipeline
#460365
failed
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ensembl-web-track-api/secret.yaml
+4
-3
4 additions, 3 deletions
ensembl-web-track-api/secret.yaml
with
4 additions
and
3 deletions
ensembl-web-track-api/secret.yaml
+
4
−
3
View file @
677ffc3c
...
...
@@ -7,11 +7,12 @@ data:
#Django settings
DJANGO_ALLOWED_HOSTS
:
"
*"
DJANGO_SECRET_KEY
:
<DJANGO_SECRET_KEY>
#DJANGO_DEBUG: "True"
#Database access (filled & applied manually)
ALLOWED_METHODS
:
get
DJANGO_DEBUG
:
False
#Database access
DATABASE_HOST
:
ensweb-trackapi-db-svc
DATABASE_PORT
:
"
5432"
DATABASE_USER
:
<DATABASE_USER>
DATABASE_PASS
:
<DATABASE_PASS>
DATABASE_NAME
:
<DATABASE_NAME>
kind
:
ConfigMap
\ No newline at end of file
kind
:
ConfigMap
This diff is collapsed.
Click to expand it.
Preview
0%
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