-
Notifications
You must be signed in to change notification settings - Fork 2
Render Web Service Tabs
This shows the deployment status and history of the server. If the current state is 'Deploy Started' the service will be down until the status returns to 'Deploy Live'.
This shows the stdout log. You can make it more informative for troubleshooting by adding a VERBOSE=true environment variable in the Environment tab.
We store the uploaded spreadsheets at the disk location specified here: 'Uploads.' In this directory there is a sub-directory called 'treasury' which contains the quarterly Treasury Reports generated by the system. These directory names are referenced by the UPLOAD_DIRECTORY and TREASURY_DIRECTORY environment variables.
The project configuration is specified here:
AWS_ACCESS_KEY_ID
, AWS_SECRET_ACCESS_KEY
, SES_REGION
, NOTIFICATIONS_EMAIL
these are for system notifications like login authentication and new user welcome emails - see Setting Up Email Notifications.
COOKIE_SECRET
This is just a nonce - you can put anything there.
POSTGRES_URL
This the PostgreSQL instance at Render.com for this web service.
REPORTING_TEMPLATE
This is just a default - an admin user can change the reporting template in the Reporting Periods tab of the Cares-Reporter UI.
SITE_URL
This is the public URL at which Render exposes this service.
TREASURY_DIRECTORY
This is where all the versions of the quarterly Treasury Reports and Audit Reports are stored.
TREASURY_TEMPLATE
This xlsx template contains the tab names and column names for the output Treasury Reports.
UPLOAD_DIRECTORY
All versions of the agency/project spreadsheets are stored here.
VALIDATION_TEMPLATE
This template contains the permitted values for the dropdown fields and the tab names for the uploaded agency/project spreadsheets.
This is just a bash shell for the server instance. You can't SSH to the server, so this is the only shell you can use for it. If you need to transfer files up or down, consider using Magic Wormhole. You can't install it with apt-get, but you can use pip to install it on both the Render server and your development system.
This tab just shows what's happening on GitHub.
Authorize users for this Render web service here.
This is useful for troubleshooting. If you see it clipping in the CPU or Memory graphs, consider upgrading your Render Plan in the Settings tab.
This is where you change your plan to increase memory or CPU capacity, and where you specify which branch of the GitHub repo to trigger deployments on. There are several other useful settings here for you to explore.