-
Notifications
You must be signed in to change notification settings - Fork 52
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
How to start a connect container with pre-configured channels? #9
Comments
It would be great to be able to set the NextGen Connect admin user/pass with Docker variables like the ones for database access
Can I just write user/pass into the database or is there a command line tool I can use? |
After further research I found in the User Guide the instructions on page 460 to set the password to the default "admin".
Is there no method to set a new password from CLI? |
…om feature/update-tests-to-use-different-pg-username-password to master * commit '09842ddcb72b6416f0504cd4c38b92ba2382de42': Update tests to use different database username and password to ensure they test that the entrypoint script is fixed.
If the CLI is proving inadequate, you could try switching over to the rest API (https://:8443/api/). The rest API is guaranteed to support all functionality since that is what the Administrator UI uses to configure Connect servers. |
@cturczynskyj I have the same wish as @bluepuma77:
I am aware that the most stable way of getting this functionality is changing the |
@aristotelos I think it would be worth making the second request in the main repo, as it is not specific to docker and could be useful with other install methods. I mentioned the problems with the first request on this issue #5 Since then, there has been some discussion in Slack, and probably the best way to achieve what you want is with a custom plugin that will activate after the mirth server has completed configuring the new database and started up. It can then acquire the channel definitions and import them automatically. This is also not docker specific, but it works well with the docker container because the plugin loading mechanism allows you to have them installed on first run rather than installing them after the server is running and rebooting. |
@tonygermano Thank you, created nextgenhealthcare/connect#6037. |
nextgenhealthcare/connect
works great so far, I have started the container with some open TCP-Ports, changed the password and deployed some channels to receive HL7v2 messages over MLLP.Now with everything stable, I would like to automate the full configuration and start of connect and the channels. What's the best practice to do this programatically when starting a new container?
The text was updated successfully, but these errors were encountered: