gfolego / faas Goto Github PK

We should have some tests to validate API and UI functioning.

It would be nice to have some statistics displayed in the web interface, such as:

• Number of accesses/views in the past 10 days.
• Nuber of requests (PDFs processed) in the past time, including 10 days, 30 days, and always.

This should be persisted across restarts.

Commit 79bfcf7 added variation in time to backend. Now we need to propagate that to UI and API.

Find an appropriate way to log the input filename. It shouldn't be too hard to extract this information from Gunicorn, to be printed together with access log.

Currently, faas.sh checks for pdf extension (case sensitive). It should be case insensitive.

As any web application, we must enforce security. What can we do in this sense? How hard would it be to use HTTPS/SSL?
This might be related to #10.

Discussions are welcome.

Reference: http://flask.pocoo.org/docs/0.10/security/

This is required to satisfy the Sumula 338. I believe this is even more critical because FaaS is an automatic system.

Create and add a favicon to the web interface.

Current title takes two lines, which are overlaid.

The system does the automatic filling considering the "correct" times, but the user is the solely responsible for the veracity of the information. We need to change the web page and the readme to include a legal notice like the following:

A veracidade das informações contidas na folha de ponto é de total responsabilidade do empregado. Se os horários de entrada e saída preenchidos pelo sistema não condizem com os horários reais praticados, o empregado deverá preencher a folha de ponto manualmente.
Não nos responsabilizamos por danos decorridos pelo uso do serviço aqui oferecido.

O código standalone permite definir o texto a ser colocado nas colunas de hora de início e hora de fim do PDF. Precisamos modificar o serviço REST para aceitar esses parâmetros.

Com isso também será possível definir esses parâmetros através da interface web.

Our current processing pipeline is less than ideal. Converting faas.sh to Python would greatly improve that, reducing the need for temporary files writing and reading.

We should improve how we handle and propagate error throughout the processing pipeline. And, particularly, how this error is displayed to the user and logged in the backend.

Users should be able to drag and drop the file, rather than browsing their systems.

We should clearly state that this is still in beta, and susceptible to bugs.

We should not sign non working days, such as weekends and holidays.
We could add a slash to these days, making signing easier and faster.

PR #17 added functionality to process.py to add a slash in non-working days. Now we need to propagate that option throughout our API processing pipeline.

I believe a good deployment option would be to use Docker, and Gunicorn.
Docker should be able to isolate software requirements, avoiding possible conflicts.
Flask states: "Do not use the builtin development server in production". We could consider Gunicorn and/or uWSGI with nginx.

Discussions are welcome.

Reference: http://flask.pocoo.org/docs/0.10/deploying/

We should have an API documentation, specifying parameters and accepted values.