diff --git a/Dockerfile b/Dockerfile
index 3145a2deb..9eac37ad5 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,5 +1,5 @@
-ARG BUILDER_IMAGE=node:12.22
-ARG RUNTIME_IMAGE=node:12.22-alpine
+ARG BUILDER_IMAGE=node:16.18
+ARG RUNTIME_IMAGE=node:16.18-alpine
ARG PHONE_NUMBER_COUNTRY=US
FROM ${BUILDER_IMAGE} as builder
diff --git a/app.json b/app.json
index 9495516b8..170e0cca7 100644
--- a/app.json
+++ b/app.json
@@ -181,12 +181,17 @@
"TWILIO_VALIDATION": {
"description": "Validate twilio message report links as well",
"value": "1"
+ },
+
+ "TWILIO_MESSAGE_SERVICE_SID": {
+ "description": "A twilio service message account SID",
+ "required": false
}
},
"addons": [
- "heroku-postgresql:hobby-dev",
+ "heroku-postgresql:mini",
{
- "plan": "heroku-redis:hobby-dev",
+ "plan": "heroku-redis:mini",
"options": {
"maxmemory-policy": "volatile-lru"
}
diff --git a/docs/HOWTO_AZURE_DEPLOY.md b/docs/HOWTO_AZURE_DEPLOY.md
index 929de3a62..24d60be06 100644
--- a/docs/HOWTO_AZURE_DEPLOY.md
+++ b/docs/HOWTO_AZURE_DEPLOY.md
@@ -125,11 +125,6 @@ YARN VERSION IS:
- Usually there is an IP White List for the different access for things
- It’s probably doing something wrong with the environment variables.
-
-## Heroku Deployment
-- Documentation update coming soon.
-
-
## AZURE AUTOMATED CONFIGURATION FILE
- Coming Soonish!
- Spotcheck
diff --git a/docs/HOWTO_HEROKU_DEPLOY.md b/docs/HOWTO_HEROKU_DEPLOY.md
index cdd002217..d05d4a3c9 100644
--- a/docs/HOWTO_HEROKU_DEPLOY.md
+++ b/docs/HOWTO_HEROKU_DEPLOY.md
@@ -5,8 +5,9 @@
- Do not start any of the processes/dynos besides `web` (see below for non-Twilio uses)
- The default setup is a free tier for processing and the database. See below for scaling and production requirements
-## Important Note for First Time Deployers:
+## Important Notes for First Time Deployers:
+- Due to the deprecation on this vendor's hobby/free resources, we wanted to inform folks that these instructions will guide you towards having successfully deploying through Heroku, but the monthly fee will be about ~$19 a month.
- There is a variable named `SUPPRESS_SELF_INVITE` in your configuration variables in Heroku. When this is set to nothing, anyone can visit your app and create an organization. When it is set to `true`, this changes login/signup behavior - when a person signs up and visits your app, they will not create an organization. On first deployment, it should be set to nothing to ensure that you have the ability to create an organization and view the full functionality of the application.
## Instructions for Auth0 configuration variable setup
diff --git a/src/containers/AdminCampaignList.jsx b/src/containers/AdminCampaignList.jsx
index aad132353..5714b89ee 100644
--- a/src/containers/AdminCampaignList.jsx
+++ b/src/containers/AdminCampaignList.jsx
@@ -4,6 +4,7 @@ import { StyleSheet, css } from "aphrodite";
import { withRouter } from "react-router";
import gql from "graphql-tag";
+import Button from "@material-ui/core/Button"
import Fab from "@material-ui/core/Fab";
import AddIcon from "@material-ui/icons/Add";
import ArchiveIcon from "@material-ui/icons/Archive";
@@ -64,7 +65,7 @@ export class AdminCampaignList extends React.Component {
archiveMultipleMenu: false
};
- handleClickNewButton = async () => {
+ createNewCampaignButton = async () => {
const { organizationId } = this.props.params;
this.setState({ isLoading: true });
const newCampaign = await this.props.mutations.createCampaign({
@@ -342,14 +343,15 @@ export class AdminCampaignList extends React.Component {
}
// add campaign button
return (
-
-
-
+
+
);
}