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

LaTeX template refinements #221

Closed
4 of 8 tasks
danielfdsilva opened this issue Mar 19, 2020 · 3 comments
Closed
4 of 8 tasks

LaTeX template refinements #221

danielfdsilva opened this issue Mar 19, 2020 · 3 comments

Comments

@danielfdsilva
Copy link
Collaborator

danielfdsilva commented Mar 19, 2020

LaTeX template refinements
Alyssa is finalizing some documentation around current status and what is missing. This will be use to spec out the refinements to be implemented.

subtasks

@danielfdsilva danielfdsilva changed the title Prototype feature improvements LaTeX template refinements Mar 26, 2020
@danielfdsilva
Copy link
Collaborator Author

danielfdsilva commented Apr 14, 2020

Relevant issues:

Other improvements:


Although not directly related to the latex generator, the whole process could be improved. Currently:

  • client gets a serialized json from server
  • client puts json in s3 bucket
  • serializer converts json to latex and then to html/pdf

We can simplify by having the server put the json in the bucket or sending it directly to the serializer.

@guidorice guidorice self-assigned this Apr 30, 2020
@sharkinsspatial
Copy link
Contributor

sharkinsspatial commented May 5, 2020

I agree with @danielfdsilva here #221 that this approach should be simplified. There are a few options each with their own issues and caveats

  1. A Lambda which takes the apt id as a parameter, makes the db request for the document and sends it to the serialization ECS task for processing. This is nice since you don't have a service running idle all the time but probably won't work since most of the serialization requests would exceed the API Gateway's 30s request timeout.
  2. As @danielfdsilva described running as service we can modify the serialization task to also handle the db request and http request/response and run it as an ECS service on the same instance as the PostgREST container. There may be some difficulty with service port usage and you will need to increase the request timeout configuration for the ELB but this should work as needed.

@guidorice
Copy link
Contributor

Please be sure to see my notes about xelatex and unicode support in #176.

@guidorice guidorice removed their assignment Jul 1, 2020
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