Skip to content
This repository has been archived by the owner on Mar 1, 2020. It is now read-only.

The test environments are not closed to the outside world #14

Open
zadigus opened this issue May 11, 2019 · 2 comments
Open

The test environments are not closed to the outside world #14

zadigus opened this issue May 11, 2019 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@zadigus
Copy link

zadigus commented May 11, 2019

All the test environments need to be only accessible from the Jenkins environment.

@zadigus zadigus self-assigned this May 11, 2019
@zadigus zadigus added the enhancement New feature or request label May 11, 2019
@zadigus
Copy link
Author

zadigus commented May 16, 2019

Because some of the standard ports are open by default and can't be closed (e.g. 80 and 443), my guess is that we just need to expose the applications in our environments to another port and close that port (that works). We just need to be careful with the databases. There are environment variables to set according to Jelastic's advice:

ADMIN_MONGO=enabled/disabled

and

REDIS_COMMANDER=enabled/disabled

We need to figure out what environment variable will do the job for a postgresql database. There will be an environment variable ADMINPANEL_ENABLED available soon (before July 2019). Until then, we can just use the following command

sudo service httpd stop 

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant