You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to spin my own App Sync server as I'm in need of applying similar technology in a project I'm working on now, and since the current repo doesn't include a [cloud-?]docker-ready setup, I went ahead and forked the repo and prepared a commit that works up until hitting login button, where the login POST call on the web interface would fail with error 500, although the daemon log is showing it is failing at a mysql query that it can be run directly on the mysql server (using maria) without any issues.
Help me get past login in order to use the service.
Consider my work and whether it is worth merging into this project in order to make it possible for others who are in need of this project to spin their own as the official instance seems to be (is it?) abandoned.
Considerations:
I wrote and tested this on aarch64 device and I'm using mariadb instead of mysql as the later isn't supported well on aarch64. I'm also using podman instead of docker. Though, I'm having these differences, I'm expecting the login issue not to be related to either of them. Since I could be wrong, the issue can be isloated by changing the db service image to mysql:8 and then start the services using docker-compose up --build.
Reacted by Juan de Dios Martínez Vallejo and wardourdigital
Hi @mahmoudajawad.
I have tried on a clean machine with ubuntu, I have left the default port: 3306 and I have the same error. What operating system are you launching it on?
@vallemar, so this is crazy. I started working on this using podman on fedora, but then continued to work on it using docker on macos, and all the way it was working for me. After your last comment, I tried and attempted to run it on docker on macos only to find that docker is broken for some reason and no matter what I did it refused to work, so I went back to podman on fedora and I could see the same error you reported, so I needed to spend little time on this and finally got it to work, although I was sure it worked for me before.
One thing, I might also need your k8s setup out of this docker-compose, as I want to use it and I'm not sure how I will end-up using it, so having the option for k8s is going to be good.
Activity
mahmoudajawad commentedon Mar 1, 2021
With the second comment to this PR, the
docker-composenow is ready and working and can be used across the architectures.vallemar commentedon Mar 15, 2021
Hi @mahmoudajawad,
I'm interested in mounting this with kubernetes and it's a lot like docker-compose. Could you contribute your docker-compose file please? Thank you!
vallemar commentedon Mar 15, 2021
ok, I have entered here and I have seen your repo. I have downloaded and run it with docker-compose up --build and I have the following error:
I have changed the public port of MySql to
but I understand that this should not affect
mahmoudajawad commentedon Mar 18, 2021
Did you also change
MYSQL_PORTvalue forappsyncservice?https://github.com/mahmoudajawad/nativescript-app-sync-server/blob/master/docker-compose.yml#L46
vallemar commentedon Mar 18, 2021
Hello @mahmoudajawad,
If I have changed that too, I have tried it on my PC in windows and in the ubuntu terminal and I have the same error.
vallemar commentedon Mar 19, 2021
Hi @mahmoudajawad.
I have tried on a clean machine with ubuntu, I have left the default port: 3306 and I have the same error. What operating system are you launching it on?
Can there be a mistake here?:
https://github.com/mahmoudajawad/nativescript-app-sync-server/blob/master/config/config.js#L6-L15
and I think it is this line that breaks everything:
https://github.com/mahmoudajawad/nativescript-app-sync-server/blob/master/models/index.js#L11
Thanks a lot
mahmoudajawad commentedon Mar 22, 2021
@vallemar, so this is crazy. I started working on this using podman on fedora, but then continued to work on it using docker on macos, and all the way it was working for me. After your last comment, I tried and attempted to run it on docker on macos only to find that docker is broken for some reason and no matter what I did it refused to work, so I went back to podman on fedora and I could see the same error you reported, so I needed to spend little time on this and finally got it to work, although I was sure it worked for me before.
One thing, I might also need your k8s setup out of this docker-compose, as I want to use it and I'm not sure how I will end-up using it, so having the option for k8s is going to be good.