Prod Servers are an Amazon Web Services cloud architecture consisting of
- Load Balancer
- Prod Server Instance cluster
- MySQL Relational Database
What you can do
- Deploy JRapid apps
- Scale your architecture on demand, adding as many instances as you need
Prod servers are configured by JRapid using Amazon Web Services (AWS):
- Elastic Load Balancing (ELB)
- Amazon Elastic Compute Cloud (EC2)
- Amazon Relational Database Service (Amazon RDS)
- Administrators, which can
- Create Deployments to it
- Not administrators
- Just Deploy
According to the generated architecture. Available types:
According to server type:
- Fixed monthly fee (permanent ELB, RDS, IP)
According to Prod Server Instance use:
- Variable monthly fee
- Prod Server Instances are created using the JRapid Prod Instance AMI, and host in its app server all applications related through Deployments.
Create Prod Server
- Prod Server name (unique), will be used for the URL
- Choose type
- Choose Billing Responsible
Project creation will reserve Amazon Web Services resources, creating again ELB, acquiring a new dedicated IP, and starting RDS (recovering from saved snapshot).
- Prod Server main information
- Prod Server Instances
- Choose type of invitation (admin or not)
- Enter email message
- Enter email addresses
- If existing users, they will be confirmed after writing the address
- If new users, the invitation will include invitation to join JRapid
Change Billing Responsible
- Billing responsible list shows B.R.'s where the current user is administrator.
- User must be a server admin to change billing responsible.
Prod servers may be Archived. This blocks the prod server in order to prevent edition and prevents the project from generating any new billing charges.
It also releases Amazon Web Services resources, terminating all instances, deleting ELB, releasing dedicated IP, and shutting down RDS (saving a snapshot, so as to be used when restoring during unarchive).
Unarchive prod server to allow users to deploy to this prod server.
It also reserves Amazon Web Services resources, creating again ELB, acquiring a new dedicated IP, and starting RDS (recovering from saved snapshot).