Engineering Thesis
For production environment, you need to have an oracle database.
If you didn't create oracle database yet, run script database/install.sql.
(run the application to instantiate mock users via SecurityConfig)
swagger - to run application with Swagger
dev - to run application with H2 database (for offline development)
mock-oci- to run application with mock connection to oci object storage (for offline development)
mock-mail- to run application with mock mail service (mail won't be sent, instead it will be printed in the console)
To run swagger use swagger profile.
Link to swagger documentation: http://localhost:8080/swagger-ui/index.html
To develop application offline please use dev profile - it uses h2 database instead of oracle database that is used on production.
No other configurations are needed.
To develop application offline with mock connection to OCI object storage please use mock-oci profile.
With this profile, you can test file upload/download without connecting to OCI object storage - the method will return a mock url and save it to database.
Of course, it will not save the file to OCI object storage and the mock url will not work on frontend side.
DB_URL - database url
DB_USERNAME - database username
DB_PASSWORD - database password
JWT_SECRET - secret key for JWT token
JWT_EXPIRATION_MS - expiration time for JWT token in milliseconds
MAIL_ADDRESS - mail address
MAIL_PASSWORD - mail password
MAIL_HOST - mail host
MAIL_PORT - mail port
MAIL_PROTOCOL - mail protocol
MAIL_SMTP_AUTH - mail auth flag (true/false)
MAIL_SMTP_AUTH_STARTTLS - mail starttls enable flag (true/false
With production environment, you need to set all of these variables.
To connect to OCI object storage you need to add config and private-key files to resources directory.
On creation of the API key in Oracle Cloud User Settings, you will get contents of the config and generate a private-key.
Of course, you need to have an account in Oracle Cloud and have created a bucket for object storage there first.