Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add how-to post for handling Google Form responses #67

Merged
merged 1 commit into from Mar 4, 2019

Conversation

Projects
None yet
3 participants
@burtonr
Copy link
Member

burtonr commented Feb 7, 2019

Signed-off-by: Burton Rheutan rheutan7@gmail.com

Create an OpenFaaS function that handles responses from a Google Form to post welcome messages to Slack.

This post goes step-by-step in creating a Google Form, an OpenFaaS function for handling the responses, and creating a Slack app to allow posting messages to a channel

The background image chosen is free for commercial use with no attribution required. Downloaded from Pixabay

@burtonr burtonr force-pushed the burtonr:google-form-blog branch 4 times, most recently from 9fb31c8 to e8c3b90 Feb 10, 2019

@burtonr

This comment has been minimized.

Copy link
Member Author

burtonr commented Feb 11, 2019

@alexellis or maybe @rgee0 What date should I put for the post? I didn't see any pattern of when posts are published.

Also, let me know if you think it's too long. I tried to explain all the pieces involved to avoid confusion, but I may have too much detail in the Form creation part. Suggestions are welcome!

I'll remove the WIP once I know what date to put for the post.

@rgee0
Copy link
Member

rgee0 left a comment

some changes suggested.

I think the title needs some work & should include openfaas, as should the description.

can we get the usual footer items in too, please? How to get involved, etc?

We should aim to get this out on Thursday.

Show resolved Hide resolved _posts/2019-02-08-google-form-response.md Outdated
![New Form Template](/images/google-form-response/new-rsvp-template.png)

* So we don't forget, first update the settings so that anyone can sign up.
* Click the cog (or gear) icon in the top right menu bar to open the form settings menu

This comment has been minimized.

@rgee0

rgee0 Feb 11, 2019

Member

I think it's a cog.

This comment has been minimized.

@burtonr

burtonr Feb 13, 2019

Author Member

If it's alright, I'll leave this as is. I've seen it referenced both ways depending on the help you get. I believe in the US it's more commonly known as the "gear icon", even though technically it is a cog.

Google (in the Material Design) call it the "Settings" icon

Show resolved Hide resolved _posts/2019-02-08-google-form-response.md Outdated
Show resolved Hide resolved _posts/2019-02-08-google-form-response.md Outdated
Show resolved Hide resolved _posts/2019-02-08-google-form-response.md Outdated
Show resolved Hide resolved _posts/2019-02-08-google-form-response.md Outdated
Show resolved Hide resolved _posts/2019-02-08-google-form-response.md Outdated
* Copy your Slack API token into a new file `slack-token`
* This is so the token is not in the terminal history
* Create the secret with OpenFaaS CLI
* `faas-cli secret create slack-token --from-file ./slack-token`

This comment has been minimized.

@rgee0

rgee0 Feb 11, 2019

Member

are we running on localhost? Where is this targeting? We've assumed they already have a setup, what if it isnt localhost?

This comment has been minimized.

@burtonr

burtonr Feb 13, 2019

Author Member

I took the approach of adding the --gateway flag to the command. In the beginning, I mention that the reader should already have an OpenFaaS cluster running, so it should be good to add that in the command. If they are already using the environment variable, or other method of specifying the gateway, the additional flag won't hurt (or they would know enough to know they don't need it). Better safe than sorry!

I experimented with an additional bullet point, or a > tag, but it seemed a bit cluttered. Adding the --gateway flag seemed (to me) the most appropriate.

Show resolved Hide resolved _posts/2019-02-08-google-form-response.md Outdated
Show resolved Hide resolved _posts/2019-02-08-google-form-response.md Outdated

@burtonr burtonr force-pushed the burtonr:google-form-blog branch from e8c3b90 to a4e53e1 Feb 13, 2019

@burtonr burtonr changed the title [WIP] Add how-to post for handling Google Form responses Add how-to post for handling Google Form responses Feb 13, 2019

@burtonr

This comment has been minimized.

Copy link
Member Author

burtonr commented Feb 13, 2019

Thanks for the in-depth review @rgee0! Good eye spotting those typos!

I've updated all the places you pointed out and updated the date to the 14th (Thursday) ❤️

Let me know what you think

@burtonr

This comment has been minimized.

Copy link
Member Author

burtonr commented Feb 14, 2019

@alexellis What date should I set this to for release? Currently, it's today, 14 Feb, but I could quickly change it. Just let me know when you think is a good date to set the release to

@burtonr burtonr force-pushed the burtonr:google-form-blog branch from a4e53e1 to 4762ffb Feb 15, 2019

@burtonr burtonr force-pushed the burtonr:google-form-blog branch from 4762ffb to b0e6581 Feb 27, 2019

@burtonr

This comment has been minimized.

Copy link
Member Author

burtonr commented Feb 27, 2019

@alexellis I've just updated the release date to be this Friday, March 1st

Please let me know if there's anything you'd like me to change/adjust. If there are any changes requested, I will do that asap. Thanks!

Add how-to post for handling Google Form responses
Signed-off-by: Burton Rheutan <rheutan7@gmail.com>

@burtonr burtonr force-pushed the burtonr:google-form-blog branch from b0e6581 to 18d0dd7 Mar 3, 2019

@alexellis
Copy link
Member

alexellis left a comment

Approved, I'll merge and do a final pass from master.

@alexellis alexellis merged commit d3e9801 into openfaas:master Mar 4, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.