-
Notifications
You must be signed in to change notification settings - Fork 0
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
245 integration environment for didcomm mediator server deployment e6 #264
245 integration environment for didcomm mediator server deployment e6 #264
Conversation
…into 245-integration-environment-for-didcomm-mediator-server-deployment-e6
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.
Wonderful 🚀
…into 245-integration-environment-for-didcomm-mediator-server-deployment-e6
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.
Looks good to go
target/ | ||
**/target/ |
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.
The excluded files should be more than just these.
SERVER_PUBLIC_DOMAIN="http://didcomm-mediator.com" | ||
SERVER_LOCAL_PORT="8080" | ||
STORAGE_DIRPATH="crates/generic-server/target/storage" | ||
MONGO_DBN="mediator-coordination" |
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.
Why choose 'mediator-coordination' as the database name? A straightforward name like 'mongodb' might make more sense.
why is this ticket closed? |
No description provided.