Make production ready

[sternj]

Good work on this so far!

I think this needs just a bit of work to get it production-ready-- right now, the only deployment instructions are for the development environment. I have some ideas--

• Clarify in the documentation the relationship between the taskchampion sync server and ccsync-- I put a copy of my .taskrc in a container, but I think it'd be super convenient if there was a way of specifying it in an environment variable
• Put up a docker image on Dockerhub!
• Document the environment variables more-- FRONTEND_ORIGIN_DEV is a bit ambiguous

This is more along the lines of a tracking issue-- I might have a few minutes to make some PRs in the next few weeks.

[sternj]

The taskchampion server is actually sent in as a parameter, as per one of your posts on the flutter app repo

[its-me-abhishek]

Hi! CCSync is just an API to fetch and add or update tasks to your taskwarrior clients by running commands. It's like another PC client that uses Docker and takes command inputs from a GUI like the app, instead of being another PC CLI.

I put a copy of my .taskrc in a container, but I think it'd be super convenient if there was a way of specifying it in an environment variable

Did you do this to get the same tasks on both cli and the app/web?

Put up a docker image on Dockerhub!

This is a great idea, I'll figure out how to upload docker compose based images to docker hub and try doing it by this week.

FRONTEND_ORIGIN_DEV is ambiguous

FRONTEND_ORIGIN_DEV is the web frontend url as I've implemented cors on the backend for Web. We need not configure if we are only using the app. I'll document more about the environment vars and other stuff in the website.

The taskchampion server is actually sent in as a parameter, as per one of your posts on the flutter app repo

Currently it's just a placeholder as the backend is still retrieving the container url from .env.. But I've planned to make a feature in the app using which users can be able to use their own Docker Taskchampion container for syncing, and use our API once it's deployed.

[its-me-abhishek]

I've opened a new thread for the documentation part on the docs website. Please check it out and feel free to suggest any new ideas for documentation here.