https://github.com/jsturtevant/timed-funktor
Manage, Monitor and Create scheduled Azure Functions
https://github.com/jsturtevant/timed-funktor
azure azure-functions nodejs react
Last synced: about 1 month ago
JSON representation
Manage, Monitor and Create scheduled Azure Functions
- Host: GitHub
- URL: https://github.com/jsturtevant/timed-funktor
- Owner: jsturtevant
- License: mit
- Created: 2017-07-28T18:12:39.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2017-08-07T18:17:32.000Z (almost 8 years ago)
- Last Synced: 2025-03-25T15:32:36.344Z (about 2 months ago)
- Topics: azure, azure-functions, nodejs, react
- Language: JavaScript
- Size: 378 KB
- Stars: 5
- Watchers: 4
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Introduction
Manage, Monitor and dynamically Create scheduled Azure Functions.
# Getting Started
In order to run the sample you will need to download the [Azure](https://azure.github.io/projects/clis/) and [Azure Function](https://github.com/Azure/azure-functions-cli) CLIs. To install these run the following lines of code:
- `curl -L https://aka.ms/InstallAzureCli | bash`
- `npm i -g azure-functions-core-tools`
## Setting up Subscription
- `az account set --subscription `
- `az login`
## Create Azure Storage Account and Azure Function
- `az storage account create --name --location westeurope --resource-group myResourceGroup --sku Standard_LRS`
- `az functionapp create --name funkDemo2 --storage-account funkstorage --resource-group demoTest2 --consumption-plan-location eastus2`
If at any point you see this error: `Sequence contains no elements` try logging out and logging in using `az func logout` and then `az func login` and enter your Azure credentials..
## Update Application settings
You will need to create a service principal to access your Function app at the resource group level. Create a new service principle:
```bash
az ad sp create-for-rbac -n --scopes /subscriptions//resourceGroups/ --role Owner
```
Your output will look like:
```
{
"appId": "xxxxxx-xxxx-xxxx-xxxx-6efb73bdxxxx", //client id
"displayName": "funkysp",
"name": "http://funkysp",
"password": "7408xxxx-xxxx-xxxx-xxxx-xxxxxx246cee", //client secret
"tenant": "4648xxxx-xxxx-xxxx-xxxx-xxxx229cxxxx" // domain
}
```
You'll need to use that output to set your function app's application settings in order to connect to your desired function app. You can find an example settings file in `api/functions/example.settings.json`.
You can make a copy of ```example.settings.json``` to ```local.settings.json``` by:
```
cp example.settings.json local.settings.json
```
Enter the following credentials in `local.settings.json`:
+ `FUNCTION_APP_NAME` - the name of your function app
+ `FUNCTION_APP_RESOURCE_GROUP` - the resource group of your function app
+ `SUBSCRIPTION_ID` - the subscription id of your function app
+ `CLIENT_ID` - the application id of the service principal when it was created
+ `CLIENT_SECRET` - the password property returned to you when the service principal was created
+ `DOMAIN` - the tenant property returned to you when the service principal was created
## Upload funktor file
There is a template file that is used to dynamically create the Functions. The app expects the file to be in your Function app storage as `funktor/functorConfigTemplate.txt` where funktor is the container name. You should be logged into the cli subscription from the previous steps, then do:
```bash
az storage container create --name funktor
az storage blob upload --container-name funktor --file './templates/functorConfigTemplate.txt' --name functorConfigTemplate.txt
```
# Running API
To start the backend api locally:
1. `cd api`
2. `npm install`
3. `npm test` (all tests should pass)
4. `func host start`
Now you can make requests to the endpoints (ex. `http://localhost:8080/api/functions`). You can also start the frontend and use the UI.
# Building and running the frontend
The frontend runs on Webpack bundling. There are some npm scripts you can run while developing.
To build:
1. `cd frontend`
2. `npm install`
3. `npm run build`
If you'd like to actively develop the frontend, use `npm run watch` instead, which will recompile all javascript every time you make a change in any frontend javascript file.
In an additional terminal pane / window / tab, run a local server instance to serve the index.html file and the assets. I use `http-server` as it's quick to run, but python's `SimpleHTTPServer` will also do if you prefer that.
To use `http-server`:
1. `npm install -g http-server`
2. `cd frontend`
3. `http-server`
4. Open a browser and navigate to the url output in the terminal after running `http-server` and you should see the app running.
### Run the test sample
This is the prototype to see if it would work before we began coding. You do not need to do anything with this folder but instructions to run it are here just incase.
- `cd api\test\sample`
- `func azure functionapp fetch-app-settings `
- `func host start`