dmitry-mightydevops/request-new-env.md

Last active March 12, 2026 10:32

Star (0) You must be signed in to star a gist
Fork (0) You must be signed in to fork a gist

Select an option

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/dmitry-mightydevops/e60c6b47948d8b6260fbed311477f3eb.js"></script>
Save dmitry-mightydevops/e60c6b47948d8b6260fbed311477f3eb to your computer and use it in GitHub Desktop.

Download ZIP

request new client environment

Raw

request-new-env.md

This doc contains template that you (PM/TM) should paste in the JIRA task and answer inline.

questionnaire

are we creating staging and prod OR only the prod env?

do we have the SLA contract for this client? (yes/no)

have you approved $500/mo per env with the client?

what domain name should be used for the production env?

how to access the godaddy or registrar to update the NS records of the domain?

If they bought the domain in godaddy - pls invite our account (devops+godaddy@saritasa.com) to manage their domain

what database you want to use?

what caching server you want to use?

do we send outgoing emails from the server?

I.e. do you need sendgrid to act as email gateway for outgoing emails?

If yes, do they have their own sendgrid account?
- If they have an existing account - ask them to invite our devops team using the following pattern of the email: devops+CLIENTNAME@saritasa.com, i.e. devops+trivver@saritasa.com.

If they don't have an existing sendgrid account - we will create one on their behalf.

do we use AWS S3 buckets?

list git repos that should be deployed in the eks cluster?

stakeholders of the project?

client name:
client email:
PM:
TM:
QA:
Lead backend dev:
Lead frontend dev:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment