Skip to content
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

Add more explanation about CCSync and its components #1

Closed
its-me-abhishek opened this issue Sep 21, 2024 · 7 comments
Closed

Add more explanation about CCSync and its components #1

its-me-abhishek opened this issue Sep 21, 2024 · 7 comments

Comments

@its-me-abhishek
Copy link
Owner

  • Document more about the environment variables
@sternj
Copy link

sternj commented Sep 21, 2024

So in this case, what is the difference between origin from the flutter app and CONTAINER_ORIGIN in this container environment?

@its-me-abhishek
Copy link
Owner Author

its-me-abhishek commented Sep 21, 2024

the origin in the flutter app is a placeholder (atleast for now until we update the backend to have the container origin to be a parameter) so it can be anything but null as we need a parameter while making API calls.

The CONTAINER_ORIGIN refers to the taskchampion sync server containers' url that you're using to sync across all your devices.

@its-me-abhishek
Copy link
Owner Author

I've added comments about the variables in the index.md in the latest commit.

@SGI-CAPP-AT2
Copy link

Title: Getting Errors while setup

Hey @its-me-abhishek ,
I have done setup of ccsync and sync-server.
Also I have done with the installation of taskwarrior
following containers are running

[root@ShGI ccsync]# docker-compose up
[+] Running 3/0
 ✔ Container ccsync-syncserver-1  Running                                                                                         0.0s 
 ✔ Container ccsync-backend-1     Running                                                                                         0.0s 
 ✔ Container ccsync-frontend-1    Running                                                                                         0.0s 
Attaching to backend-1, frontend-1, syncserver-1

but when I add task or sync tasks its returning internal server error
I have also done with the setup of taskwarrior as

[root@ShGI ccsync]# task --version
3.2.0
[root@ShGI ccsync]# task config sync.encryption_secret ZZZZaee9076288e08ea13e3508580a99c1bdc120f8bae8fd5c0afb22ee1bXXXX
Are you sure you want to add 'sync.encryption_secret' with a value of 'ZZZZaee9076288e08ea13e3508580a99c1bdc120f8bae8fd5c0afb22ee1bXXXX'? (yes/no) yes
Config file /root/.taskrc modified.
[root@ShGI ccsync]# task config sync.server.origin http://localhost:8080/
Are you sure you want to add 'sync.server.origin' with a value of 'http://localhost:8080/'? (yes/no) yes
Config file /root/.taskrc modified.
[root@ShGI ccsync]# task config sync.server.client_id d542def4-XXXX-34a4-bd44-27efd5b71XXX
Are you sure you want to add 'sync.server.client_id' with a value of 'd542def4-XXXX-34a4-bd44-27efd5b71XXX'? (yes/no) yes
Config file /root/.taskrc modified.
[root@ShGI ccsync]# task sync init
sync.server.origin is deprecated. Use sync.server.url instead.
Syncing with sync server at http://localhost:8080/

getting following errors in react frontend
image
image

I dont know if this is correct place to ask for help as there is no slack channel for ccsync.

@its-me-abhishek
Copy link
Owner Author

sync.server.origin is deprecated. Use sync.server.url instead.

have u tried working on this? as I am unaware if this has recently got deprecated or not...
might be a simple fix if you could work it out on the Docker shell

@SGI-CAPP-AT2
Copy link

Sorry, I didn't tried on docker shell instead i was trying on my WSL.
Confused by this :
image
Sorry about that

@its-me-abhishek
Copy link
Owner Author

for these common issues, I think that the official Slack's #taskwarrior-flutter channel should suffice, until a new channel is created dedicated to CCSync

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants