Skip to content

Limit access for Database and Backend Servers for developer environment #376

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 21, 2024

Conversation

amoghjalan
Copy link
Contributor

Linked Issue(s)

Fixes security issue for developers so that people on same network are not able to access backend servers and database

Acceptance Criteria fulfillment

  • Task 1
  • Task 2
  • Task 3

Proposed changes (including videos or screenshots)

Further comments

@amoghjalan amoghjalan merged commit cec6e6d into main May 21, 2024
1 check passed
@amoghjalan amoghjalan deleted the limit-access branch May 21, 2024 13:22
@@ -37,7 +37,8 @@ RUN mkdir -p /etc/cron.d && mv /app/setup_utils/cronjob.txt /etc/cron.d/cronjob
RUN chmod +x /app/setup_utils/start.sh /app/setup_utils/init_db.sh /app/setup_utils/generate_config_ini.sh
RUN mv /app/setup_utils/supervisord.conf /etc/supervisord.conf
RUN mv /app/database-docker/db/ /app/ && rm -rf /app/database-docker/
RUN echo "host all all 0.0.0.0/0 md5" >> /etc/postgresql/15/main/pg_hba.conf
RUN echo "host all all 127.0.0.1/32 md5" >> /etc/postgresql/15/main/pg_hba.conf
RUN echo "host all all 192.168.65.1/32 md5" >> /etc/postgresql/15/main/pg_hba.conf
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants