-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature limit resources #561
Conversation
…r issues and warnings.
…o the GUI docker container. Added a small script that exchanges the two xml files in case the UI authentication flag is set to false.
…odel using PROV-O properties.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe a better name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, that file shouldn't have been uploaded 😅
config/db/storage-init.sh
Outdated
@@ -1,9 +1,6 @@ | |||
# Initialization script for the Storage of the HOBBIT Platform. | |||
# Controls access rights for Platform-specific RDF graphs. | |||
|
|||
echo "Waiting for port to open..." | |||
while ! nc -q 1 localhost 1111 </dev/null; do sleep 5; done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was waiting for Virtuoso to initialize in case it still didn't, does it cause any problems?
docker-compose-dev.yml
Outdated
volumes: | ||
- ./config/jetty/web-without-ui-auth.xml:/var/lib/jetty/webapps/ROOT/WEB-INF/web.xml | ||
#volumes: | ||
#- ./config/jetty/web-without-ui-auth.xml:/var/lib/jetty/webapps/ROOT/WEB-INF/web.xml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just remove this line, as the situation without auth is now handled differently?
DEPLOY_ENV: "testing" | ||
GITLAB_USER: "${GITLAB_USER}" | ||
GITLAB_EMAIL: "${GITLAB_EMAIL}" | ||
GITLAB_TOKEN: "${GITLAB_TOKEN}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did this cause any problems? Having variables here by default makes it possible to just add .env
file without making any additional changes.
No description provided.