Closed dthaler closed 1 week ago
The changes involve updates to environment variables and properties in various workflow and publish profile files for a .NET Core application. The AZURE_WEBAPP_NAME
and AZURE_WEBAPP_PACKAGE_PATH
variables have been modified in both the publish.yml
and release.yml
files to reflect new naming conventions. Additionally, properties related to Azure resource identification have been removed, and the casing of application paths and usernames has been standardized in the publish profile files. The documentation has also been updated to correct URLs and improve clarity.
File Path | Change Summary |
---|---|
.github/workflows/publish.yml |
Updated AZURE_WEBAPP_NAME from OrcanodeMonitorStaging2 to orcanodemonitorstaging ; updated AZURE_WEBAPP_PACKAGE_PATH from OrcanodeMonitor2\published to OrcanodeMonitor\published . |
.github/workflows/release.yml |
Updated AZURE_WEBAPP_NAME from OrcanodeMonitor2 to orcanodemonitor ; updated AZURE_WEBAPP_PACKAGE_PATH from OrcanodeMonitor2\published to OrcanodeMonitor\published . |
OrcanodeMonitor/Properties/PublishProfiles/OrcanodeMonitor - Web Deploy.pubxml |
Removed <ResourceId> and <ResourceGroup> ; updated <DeployIisAppPath> from OrcanodeMonitor to orcanodemonitor ; updated <UserName> from $OrcanodeMonitor to $orcanodemonitor . |
OrcanodeMonitor/Properties/PublishProfiles/OrcanodeMonitorStaging - Web Deploy.pubxml |
Removed <ResourceId> and <ResourceGroup> ; updated <DeployIisAppPath> from OrcanodeMonitorStaging to orcanodemonitorstaging ; updated <UserName> from $OrcanodeMonitorStaging to $orcanodemonitorstaging . |
docs/Debugging.md |
Updated URLs for Azure SCM site and production/staging links for accuracy. |
docs/Design.md |
Updated URLs for hydrophone data and production/staging server links for consistency. |
AZURE_WEBAPP_NAME
and the package path are related to the updates in the .github/workflows/release.yml
file, which also modifies the AZURE_WEBAPP_NAME
and AZURE_WEBAPP_PACKAGE_PATH
for deployment, indicating a consistent naming convention across multiple deployment configurations.In the fields where bunnies play,
New paths are set for a bright array.
With names that hop and softly sway,
Our code now dances, come what may!
🐇✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Blocked on getting manual deployment to work
Addresses more of #133
Summary by CodeRabbit
New Features
Bug Fixes
Documentation