When a new application deployment is to be created we always need the same set of information.
If possible, please supply all the information listed below and send them via E-Mail to ops@makandra.de.
This helps us, the makandra Operations Team, to configure your new deployment.

If some points need further clarification you should also drop us a line, we are happy to help!

Type of deployment

The deployment is ..

• Ruby on Rails
• Elixir
• PHP
• A static page
• Other

General Information

• When is the deployment planned go live?
• How much traffic do you expect?
• Who shall get E-Mails regarding this deployment?
  • Who should get (cron) fail mails (interesting mostly to developers)?
  • Who should get maintenance mails (interesting mostly for project managers)?
• This deployment is part of which contract? (link to the proposal if you have one)

Basic deployment information

• Name of the deployment
  • Keep in mind, the application name is used as part of the user name, database and config files)
• Database backend (MySQL or PostgreSQL)
• Database extensions (e.g. postgis)
• SSH keys for deployment
• Configuration file content (e.g. production.yml, secrets.yml)
• Additional packages to be installed (e.g. yarn, node, ruby-rmagick, wkhtmltopdf, ...)

Additional services for your deployment

• Redis
• Elasticsearch
• memcached
• ClamAV (This requires at least a m2.8 server. See ClamAV Sizing)

Specific deployment information

Rails

Optional:

• Ruby version
  • Or if you want to manage the Ruby version yourself (see here)
• Rubygems version
• Do you need NodeJS?
  • Which version or unmanaged?
  • System wide installation or per deployment?
• Is there a reason you can not use jemalloc Show archive.org snapshot (usually there is not)?

PHP

• Which PHP version?

Elixir

• Appname
• DB extensions
• Elixir/Erlang version
• Is the application built on our appserver or on another machine (locally on your PC, on a CI server)?

Loadbalancer / Proxy configuration

DNS

• Have you already registered a domain?
• Is DNS already configured ?
• Which domains/subdomains shall be configured?
• Is there some kind of "main" domain to which shall be redirected?

HTTPS/SSL configuration

• Enable HTTPS/SSL?
• Optional SSL (HTTP and HTTPS possible), forced SSL (HTTP redirected to HTTPS) or SSL only?
• On forced SSL: rewrite flag 301 or 302 (default)? See here
• Enable HSTS Show archive.org snapshot ?(default: on)
• Certificate: Let's Encrypt (default), self-provided, Extended Validation Show archive.org snapshot

Monitoring

• Is there a specific monitoring endpoint for our monitoring to be checked?
• Can we implement Loadbalancer HTTP checks?
• E-Mail notification contact (optional)

Common Loadbalancer configuration

• Are there any specific routes with non-default behavior? (e.g. separated asset vhost)
• Redirects for some URIs?
• Can we enable caching?