actions-workflow-samples VS twurl

GitHub Actions for Azure (official examples): https://github.com/Azure/actions-workflow-samples

appcontent.yml - Used to deploy my app content to the Azure App Service. Using this sample provided by Microsoft, with very minor modifications.

It's using GitHub Secrets. This guide helps: https://github.com/Azure/actions-workflow-samples/blob/master/assets/create-secrets-for-GitHub-workflows.md

For this exercise we need a personal access token from github. To ensure that the action has access to the GitHub token which you, by the way, should never expose to the public - we will place it in the secrets of the repo.

First we'll need to make some repo secrets. Here's a nice guide from Azure explaining how to do just that. It isn't difficult at all.

Add Actions secrets for the FTPS credentials. In our example the secret names are WP_USER and WP_PASSWORD.

Yep. For the projects I’ve worked on, the Azure Functions for scheduling were in their own `functions` folder at the root of the repository. Upon successful deployment of the main app, we’d then deploy the functions. Aside from that deployment happening after the main app’s, we use the same deployment configuration as the official example for GitHub Actions with Python functions: https://github.com/Azure/actions-workflow-samples/blob/master/FunctionApp/linux-python-functionapp-on-azure.yml.

We have 1 user that we use for deployment. We keep the username and password of this user in a Secret (all platforms support some form of secrets, here is some docs on Github Actions specifically).

I followed the official documentation (Link) and used the pre-defined template and it worked out of the box.

After registering a Twitter App, make sure to enable Read/Write permissions in the App settings. Create an .env file in the root of the project based on .env.example. We can use this data in our file with an object like this:

Hello guys! I have spent a few hours now, trying to get my tweepy to work. I have made an app on developer.twitter.com, trying to post somwthing on twitter. I feel like I have tried everything, and I have even consulted my friend ChatGPT for help, but I keep getting lost in the documentation and GPT is of no help in this case!

Please visit developer.twitter.com to sign up to our new Free, Basic or Enterprise access tiers.

In the meantime, you can learn more about the Twitter API v2 and find resources on developer.twitter.com. We appreciate your continued interest in developing on the Twitter API.

As a prerequisite, you need a Twitter Developer account. With a Twitter account, it's easy: navigate to https://developer.twitter.com and register a new app. Make sure that you create a Twitter app that has read and write permissions!

This kind of has us scrambling a bit, actually. Not because we'd have to pay per se, but rather we've been using their API for so long on our website (and def still on v1.1) that now when we check the developer site it just funnels to a "Sign up" and no longer shows us our existing/old apps, so we cannot find/figure out which account was linked to our production credentials (and that's really on us for not staying on top of which account that was).

To start the process to become a "Twitter developer" visit developer.twitter.com, sign-in and start the process... It may be an annoying process with manually reviews.

Twitter API

2 - Create a developer account that you will associate with your Twitter account. To do this, go to https://developer.twitter.com. You click on Sign up, then you will have to follow the instructions and choose the Bot option for the use you will make of the API. Once you have created your account, you will be assigned a Bearer Token. Keep it safe, as you will need it to make your requests later.

To start using Twitter API, you need to register for a developer account (including phone number verification). Once you register, you will be prompted to create the first application. You will immediately receive API Key and API Key Secret – but ignore them, since these are only for OAuth 1.0. Instead, go to your project's dashboard, there go to the App Settings of the only application you created. In application settings, find User authentication settings and click Set up.