• Sort functions and configurations into separate pages.

• Authentication:

  • Login page and functionalities.
  • Add "db_controle" to basic.yml.
  • Configure "db_controle" while compiling.

• Functions:

  • Backups:
    • Add upload
  • Cloning (export-all)
    • Add feature.
    • Add download link to cloned installer.

• Configurations:

  • Networking:
    • Wheter to provide DHCP or not.
    • Wheter to provide DNS or not.
    • Manual IP.
  • Sync:
    • Remote install's address.

Programmable online synchronization.

The online sync process needs to be automated, programmable and reliable.

Transmission

• Study the required functionalities for secure and reliable packet transmission.
• Find out-of-the-box solutions if there are any.
• Implement the transmission functionality.

Automation

• Implement auto importing functionality.

Programming

• Implement the panel using the same interface for programming backups, cron-style.

Vendored code is actually downloaded by the compiler, this is not necessary after the changes made by resolving issue #26.

• Ship vendored code with controle.avapolos
• Ship vendored code with inicio.avapolos
• Ship vendored code with downloads.avapolos

Use git for tracking changes.

https://github.com/github/linguist

• Some PHP files detected as Hacklang: https://github.com/github/linguist#overrides
• Ignoring vendors: https://github.com/github/linguist#vendored-code
• Add .gitattributes correcting this issue.

Maybe put the project logo?
Estimated time of completion?

Com tudo que foi feito até aqui.
Adicionar "fatos" relevantes.

Students can't access the University's instance.
Professors can't access the Polo's instance.

DBMS: SQLite 3

• Specify what needs to be stored in a database.
• Specify what needs to be stored in a flags directory.

Files that need to be organised:

• $INSTALL_SCRIPTS_PATH/polo
• $INSTALL_SCRIPTS_PATH/interface
• version
• interface

Some big files are redownloaded every time.

wget supports the -N option, that enables time stamping.

• Use -N option while downloading installers while compiling http://downloads.avapolos.

The backend is working, but the php frontend needs a fix!

Reportar problemas no painel de controle.

O reporte de problemas pode ser feito do POLO para IES, e da IES para os Developers ou outro destinatário.

POLO -> IES -> CRIADORES OU ADMs

• Criação do formulário e página de reporte.
• Funcionalidade de enviar logs por ZIP.
• Enviar os logs para a IES
• Enviar os logs para os Developers ou um contato específico.

https://codepen.io/inital_a/pen/MKoKya

O campo "manual expression" é atualizado com a cron string selecionada pelo usuário. Precisamos enviá-la para o backend assim que o submit for clicado.

• Implementar o formulário com o seletor do codepen.
• Implementar uma opção de fazer backup para uma share NFS ao lado do botão de download.
• Implementar uma opção de manter os backups de X tempo atrás ( dias, meses, anos).

• Add noip.yml.
• Add a script to enable noip service.
• Add the command to the service daemon.
• Integrate the GUI with the service.
• Change the traefik URLs according to the new address.
• Change menu's URLs according to the new address.
• Change Moodle's URL according to the new address.
• Change wiki's URL according to the new address.
• Fix access_mode.sh.
• Add possibility to force a domain name without noip.
• Fix maintenance web page container

Test everything implemented so far.

Customização do Moodle

A única customização que falta fazer é inserir as logos do AVAPolos no Moodle:

• Identificar tabelas que contém os dados pertinentes às logos.

mdl_config_plugins:

plugin     | name             | value
---------------------------------------
core_admin | logo             | .png
core_admin | logocompact      | .png

• Encontrar uma forma de subir as logos e referenciá-las na base de dados.

• Monitor failing services on "controle.avapolos"

Upgrade security

Sort out the database and service passwords. Maybe generate one for each service on data compiling and store them somewhere safe?
/opt/avapolos/data/secrets

• Specify what services and or databases need a generated password.

On data compiling time, secrets file should be generated and sourced by the compiler:

• Create a secrets file on the data directory at compile time.
• Lock down the file using 600 permission
• Generate a hex number of size 16 for each password using opessl rand -hex 16 (50 nonillion years to break!)
• Update the compiling scripts of each service.
• Update the docker-compose.yml of each service.
• Update the connect-db-master and connect-db-sync commands.

• Add a function to update moodle's hosts file on service restart.

Logging needs an update.

Some changes need to be made to both optimize and provide good usability to the logging functionality.

• Implement max line count for each log file.
• Sort out the logger settings

Ensure usability for developers:

• LOGGER_LVL
• LOGFILE_PATH
• TIMESTAMP_SCHEME
• LOGFILE_MAXLINECOUNT

Sometimes it gives errors about docker networks.
Cannot stop the basic stack anymore.

Info about the last and next sync, and the interval configured.