Hello, @EddyVerbruggen.
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.
The commit: master...mahmoudajawad:master
Could you please:
- 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.
Hello, @EddyVerbruggen.
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
POSTcall 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.The commit: master...mahmoudajawad:master
Could you please:
Considerations:
I wrote and tested this on
aarch64device and I'm usingmariadbinstead ofmysqlas the later isn't supported well onaarch64. I'm also usingpodmaninstead ofdocker. 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 thedbservice image tomysql:8and then start the services usingdocker-compose up --build.