We recommend Default Deployment if your app is not yet running within AWS.
Sign up to get a license key here - you’ll need to enter this key into the Quick Setup flow later in the process.
To deploy within an existing VPC click here.
For our default deployment strategy we will spin up Pipebird within a default subnet. In case you don’t have a default subnet, follow the below steps to create one.
First, install the aws-cli
brew install awscli
Next, configure your aws account locally
Then, create a default subnet
aws ec2 create-default-subnet --availability-zone us-east-1a
Pipebird’s server will be running on port 3000 of the newly created instance. You can find the code for the server in your absolute path: /pipebird.
After creating your EC2 instance, you will need to use the following command to create your pipebird-secret-key:
scp -i ~/Downloads/test-datawarehouse-bastion.pem firstname.lastname@example.org:~/pipebird/.env pipebird-secret-key && clear && cat pipebird-secret-key | grep "^SECRET_KEY" && rm pipebird-secret-key
You can use this secret key bearer token defined in this file to make authorized requests against your Pipebird instance.
Check your CloudFormation stack and CloudTrail logs for details on why a build may have failed.
Still having issues? Feel free to shoot us an email at email@example.com
Required environment variables are specified in
.env.example - make sure to fill out
DATABASE_URL before attempting to
Pipebird requires Node >= 16, a running Postgres instance, and a running Redis server to function.
You can also run Pipebird locally after cloning the repo by running the following:
npm install npm run build npx prisma migrate deploy npm start