Skip to content

Added async task into the GuestRegistrySource class to diverge from using the...

Bryan Granda requested to merge issue_328_Moving_the_registration_database_from_a_local_database_to_a_remote_database into main

License and Copyright Notice

By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).

Branch Name

issue_328_Moving_the_registration_database_from_a_local_database_to_a_remote_database

Related Issues

#348 (closed) #349 (closed) #339 (closed) #369 (closed)

Description

This merge request will allow users to register their data onto the remote database and be stored there instead of the local database, sqlite. This merge request also includes ways to work with credentials so they are not being exposed to the GitLab repository.

Steps to Test

  1. Run the app and in the root directory, check if a credentials.properties file was created.
  2. Replace the values inside the GUEST_REGISTRY_DB_USERNAME and the GUEST_REGISTRY_DB_PASSWORD fields with the Guest Registry database credentials.
  3. Terminate the app and run it again.
  4. Click on GUEST FORMS.
  5. Click on GUEST REGISTRATION.
  6. Go through the entire registration form.
  7. Once the form is completed and the success message is displayed, check the remote database to see if the data was actually stored in the remote database.

Relevant Screenshots

(Post any relevant screenshots here.)

Relevant Logs

(Paste any relevant logs here.)

Developer Notes

(List any notes you have about what you did here using bullets, for ex:)

  • Note 1
  • Note 2
  • Note 3

Merge request reports