@dkayiwa is there anything I need to change in the atom feed config files?
@irenyak1 did the patients get created on the second server?
@dkayiwa No they did not, because when I search for the patient I registered on the parent, It is not reflected in the child even after sync showing that it was successful.
Can you create a ticket about sync displaying a success message when it actually failed? Do not forget to include links to the child and parent logs.
1 Like
@dkayiwa ok let me do that. As I do this, depending on the screen shots i have shared, I there anything I could have not done right? Did you look at this error in the details of the audit log?
@irenyak1 should add that it’s to do with authorization
@reagan have you got the same error before?
I posted my paste bin link earlier in the comments
Is that a link to the ticket or board?
Now i would want to suggest some few things.
-
Its over a week and its like no one has been able to sync succesfully between local servers ,especially for windows users, and am seeing we are spending much time on setting up a local testing env.
-
Now regarding the Remote servers(nginx) , do we have the priviledges to upload and unload modules? if not, to save time , can we have one or two members be given privileges to load and unload modules so that we can make the remote servers the testing enviroment for reproducing bugs and fixing the bugs??
NB I proposed one or two so that we can have a control over uploading the modules, not to have a clash between different devs trying to test out their changes at the same time.
- We can start out a talk thread where whoever wants to test out, pings that dev with privileges , he uploads the module in testing , and then some one can test out his her changes . Just a quick solution to this whole local testing enviroment issues. it is becoming a night mare for windows users
I would not recommend releasing work which you cannot test locally to confirm if all is well. Remember that the product owners are not going to use those remote testing servers. They are instead going to locally set up their instances. Therefore, the focus should be on making it easier to set up. It is a good thing that you, the developers, are getting this pain. That way, you will get down to fixing it, as part of the sprint. 
3 Likes
That true , but in actual production , theres no such thing as having two local instances on the same machine 
. I think Sync has a problem with that(especiall on windows). Because even in my previous replies , i complained about Sync invalidating sessions for the other locally running server instances, so one has to login every minute in the other server whenever an action takes place on one of the servers
@mozzy that also needs to be fixed as part of the sprint. Anything that makes developers more productive is worth doing.
2 Likes
I have as well gotten some observation, not sure whether its what @irenyak1 discovered.
I first created two instances, one parent and the other child 1 and they seemed to be sharing data amongst themselves however on adding another child 2, it could draw patients from the parent when I click on the pull tab but then fail to push data (new patients) to the parent even when it indicates Pushing successful. I again created child 3 to confirm this but on my dismay it couldn’t do neither of the two operations (push and pull) although it was displaying a success alert message. Am wondering whether its the same case to other or i have something not well fixed. Cc. @dkayiwa
1 Like
Thank y’all Team Hope we can include all this ( Pain )in Sync2 User Documentation.
1 Like
wow this is good @mozzy have you tried thia, let me also try this and see, @irenyak1, any successful technical about sync to parent
@sharif thanks but it is still failing to pull from the parent.
@dkayiwa I have tried to set up two instances using the SDK and I have succeeded but the atomfeed omod can not be uploaded as it throws this error.
I wanted to try out with the SDK not the standalone.
@irenyak1 are you using windows ??