- KPIs and OKRs
- Remote Work
- Access Control Policy
- Data Management Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Information Security Policy and Acceptable Use Policy
- Secure Development Policy
- Cryptography Policy
- Development & Design Practices
- Front End
- How We Work
- Markdown How-To
- Using Git
- Website A/B Testing
- Internal Operations
- People Ops
- Sales & Marketing
- Boiler Plate Descriptions
- Content Channels
- Content Types
- Marketing - Website
# Staging Environment
We have a staging environment running on AWS which is a scaled down replica of our managed FlowForge offering, with a separate domain. Staging URL and sign in details can be found in the Developer Vault in 1Password.
# AWS Account
It uses a separate AWS account ending in ..9937
Ben or ZJ can provision a user account for this account.
The services are running in EU-West-1.
The staging environment uses one node running on a t2.small for the management app and a pair of t2.small nodes for the projects cluster. t2.small is the smallest instance that can be used with EKS.
Amazon SES is setup on staging however it is still running in sandbox mode which means only verified address & domains can RECEIVE emails from it, this is currently limited to flowforge.com email addresses and a small set of pre-approved disposable emails.
There is no intention to move this from sandbox as this helps to limit access to staging.
If you need to use another email address with staging then you should verify the address through SES in the AWS Console.
# Test Email accounts
We have enabled a small list of mailinator.com based email addresses for the purposes of short-lived testing of sign-up and user management.
The inboxes for these email addresses are publicly accessible if known, so the list is available on this private issue: https://github.com/flowforge/CloudProject/issues/135
Currently there is no auto deployment to staging, this should be rectified in the future so that staging is running the code in the main branches of the respective repos.
# Using staging
When setting up a team you'll need to enter billing details. For credit card details, use the Stripe mock data.
# Using the FlowForge Device Agent with staging
Staging uses pre-release npm packages stored in a GitHub npm repository. To be able to use these packages you will need to authenticate with the repository.
You will need to create a GH Personal token
- Go to your classic personal access tokens
- Click Generate New Token (and again pick the classic option)
- You will probably be prompted for 2FA now
- Give the token a meaningful name
- Pick an expiration. I went with no expiration so I don't have to do this again and I'm going to limit the scope
- Tick the box next to
- Click generate token button at bottom of page
Store the token in your private 1Password vault
Create the following .npmrc file:
ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxx is the token you just generated.
You need to place this in the project directory, e.g.
/opt/flowforge-device/project or if you are running it in the dev env
flowforge-device-agent/var/project (assume starting with
node index -d ./var -c ./var/device.yml)