-
Notifications
You must be signed in to change notification settings - Fork 24
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
Login/redirect problem for containerized OpenDB instance #95
Comments
UrsusExplorans
changed the title
Login problem for containerized OpenDB instance
Login/redirect problem for containerized OpenDB instance
Sep 25, 2017
I have not had much time for opendb and I don't use it anymore myself. If
I get a chance next week I will take a look.
I love the idea of docker opendb though.
…On 25 Sep. 2017 3:54 am, "UrsusExplorans" ***@***.***> wrote:
Playing around with Docker and trying to containerize OpenDB, I'm having
trouble using the resulting image. When logging in with correct
credentials, I always get redirected to the login page, again with the
message
You will be redirected to welcome page once you have successfully logged
in.
With wrong credentials, it additionally says
Login failure.
You can find the Dockerfile, here at GitHub: https://github.com/
UrsusExplorans/opendb-docker/blob/master/Dockerfile (image is on
DockerHub: https://hub.docker.com/r/ursusexplorans/opendb-docker/).
I linked the container to a database container instantiated with the
current mysql:latest image, running a MySQL server version 5.7.19. The
database connection is apparently working correctly, as the installer can
create the needed tables.
I just added my own tables.sql with the only modification in line 334, as
MySQL did not accept '0000-00-00' as correct default value. (maybe worth
an additional issue)
Though my experiments are still quite simple, I hope you like the idea to
containerize OpenDB for easier deployment. So I'd appreciate you help on
this issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#95>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAQyLmoo4Nkv32iM7gtxkeaN1tM0I8Bbks5slpdYgaJpZM4Ph-AU>
.
|
Thanks for your note. I'm glad you like the idea of containerizing openDB. |
I don't collect DVDs anymore so I don't use open db for that reason. I put
it onto github so community could continue its maintenance if desired
…On 3 Oct. 2017 11:45 pm, "UrsusExplorans" ***@***.***> wrote:
Thanks for your note. I'm glad you like the idea of containerizing openDB.
You say, you don't use openDB anymore. Can you recommend alternatives, in
case there is no solution to my problem?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#95 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAQyLpcBlm2wsBrYWpyhxS_mFNOzMW7pks5soixZgaJpZM4Ph-AU>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Playing around with Docker and trying to containerize OpenDB, I'm having trouble using the resulting image. When logging in with correct credentials, I always get redirected to the login page, again with the message
With wrong credentials, it additionally says
You can find the Dockerfile, here at GitHub: https://github.com/UrsusExplorans/opendb-docker/blob/master/Dockerfile (image is on DockerHub: https://hub.docker.com/r/ursusexplorans/opendb-docker/).
I linked the container to a database container instantiated with the current
mysql:latest
image, running a MySQL server version 5.7.19. The database connection is apparently working correctly, as the installer can create the needed tables.I just added my own
tables.sql
with the only modification in line 334, as MySQL did not accept'0000-00-00'
as correct default value. (maybe worth an additional issue)Though my experiments are still quite simple, I hope you like the idea to containerize OpenDB for easier deployment. So I'd appreciate you help on this issue.
The text was updated successfully, but these errors were encountered: