Minor refactor on docker-compose and env file

[italovalcy]

Related to Issue #106

Description of the change

• Removing unnecessary variables from docker compose
• aggregating variables for RabbitMQ Host
• Using new endpoints for OXP provisioning URL (kytos so far)
• removing sdx-test container

[lmarinve]

centralizing all environment variable values into a single .env file. This approach can enhance the simplicity, security, maintainability, and scalability of the application’s configuration management. By adopting this practice, we can make it easier for new developers to onboard, improve security measures, and ensure quick updates without inconsistencies. By maintaining a single source of truth for environment settings, we can ensure that the project remains efficient and aligned with industry standards as it evolves.

[italovalcy]

centralizing all environment variable values into a single .env file. This approach can enhance the simplicity, security, maintainability, and scalability of the application’s configuration management. By adopting this practice, we can make it easier for new developers to onboard, improve security measures, and ensure quick updates without inconsistencies. By maintaining a single source of truth for environment settings, we can ensure that the project remains efficient and aligned with industry standards as it evolves.

Hi @lmarinve thanks for the comment and suggestion. I've pushed commit 5aabbc6 to move all variable definitions to the env file. Please let me know if you have additional comments.

[lmarinve]

Thank you