ExternalVendorCode/onefuzz
1
0
Fork 0
mirror of https://github.com/microsoft/onefuzz.git synced 2025-06-15 11:28:09 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
a0b5d10c810dc3c5632a56e4fb88e112295c945f
onefuzz/src/api-service
History
Choongwoo Han a0b5d10c81 Add target_workers to TaskUnitConfig (#305)
2020-11-12 13:22:53 -05:00
..
__app__
Add target_workers to TaskUnitConfig (#305)
2020-11-12 13:22:53 -05:00
tests
Autoscale test: I (#278)
2020-11-11 10:53:47 -05:00
.flake8
initial public release
2020-09-18 12:21:04 -04:00
.gitignore
initial public release
2020-09-18 12:21:04 -04:00
dev-deploy.ps1
Adding version as a param to dev-deploy script (#239)
2020-11-02 14:05:13 -05:00
dev-deploy.sh
Remove use of batch in NodeMessages (#60)
2020-10-01 11:14:39 -04:00
mypy.ini
Add github issues integration (#110)
2020-10-07 11:54:43 -04:00
pytest.ini
initial public release
2020-09-18 12:21:04 -04:00
README.md
initial public release
2020-09-18 12:21:04 -04:00
requirements-dev.txt
re-add black to lint stages (#45)
2020-09-29 16:35:41 -04:00

README.md

If you are doing development on the API service, you can build and deploy directly to your own instance using the azure-functions-core-tools.

From the api-service directory, do the following:

func azure functionapp publish <instance>

While Azure Functions will restart your instance with the new code, it may take a while. It may be helpful to restart your instance after pushing by doing the following:

az functionapp restart -g <group> -n <instance>