chore: fix deploy urls (#2115)

.github/workflows/deploy.yml

@@ -58,6 +58,8 @@ jobs:
       - name: Deploy Web App
         id: deploy_web
         run: |
+          # Delete old deployment (otherwise we get a spawn EBUSY error when running the workflow again)
+          az staticwebapp environment delete --name jabref-online --environment-name ${{ github.event.pull_request.number }} --yes || true
           # Workaround for https://github.com/Azure/static-web-apps-cli/issues/557 and https://github.com/Azure/static-web-apps-cli/issues/565
           $output = yarn swa deploy .output\public --env ${{ github.event.pull_request.number }} --verbose=silly 2>&1 | Out-String
           Write-Host $output
@@ -129,16 +131,17 @@ jobs:
     if: github.event_name == 'push'
 
     strategy:
+      fail-fast: false
       matrix:
         include:
           - environment: Test
-            url: https://mango-pebble-0224c3803-dev.westeurope.1.azurestaticapps.net
+            url: https://dev.www.jabref.org
             deployment_environment: dev
           - environment: Staging
-            url: https://mango-pebble-0224c3803-staging.westeurope.1.azurestaticapps.net
+            url: https://staging.www.jabref.org
             deployment_environment: staging
           - environment: Production
-            url: https://mango-pebble-0224c3803.1.azurestaticapps.net/
+            url: https://www.jabref.org
             deployment_environment: default
 
     environment:
@@ -182,6 +185,9 @@ jobs:
 
       - name: Deploy Web App
         run: |
+          # Delete old deployment (otherwise we get a spawn EBUSY error when running the workflow again)
+          az staticwebapp environment delete --name jabref-online --environment-name ${{ matrix.deployment_environment }} --yes || true
+
           yarn swa deploy .output\public --env ${{ matrix.deployment_environment }}
         env:
           SWA_CLI_DEPLOYMENT_TOKEN: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN_MANGO_PEBBLE_0224C3803 }}

README.md

@@ -4,15 +4,15 @@ This repository contains the source of the [JabRef homepage](https://www.jabref.
 
 ## Servers
 
-- Production server: https://mango-pebble-0224c3803.1.azurestaticapps.net
+- Production server: [www.jabref.org](https://www.jabref.org/)
   This server runs the last released version with data provided by the production database.
-- Staging server: https://mango-pebble-0224c3803-staging.westeurope.1.azurestaticapps.net
+- Staging server: [staging.www.jabref.org](https://staging.www.jabref.org/)
   This server runs the latest version of the main branch with data provided by the production database.
   Usually, you do not want to target this server. Its main purpose is to test the main branch before a release.
-- Test server: https://mango-pebble-0224c3803-dev.westeurope.1.azurestaticapps.net
+- Test server: [dev.www.jabref.org](https://dev.www.jabref.org/)
   This server runs the latest version of the main branch with test data that is usually reset on redeployment.
   The main use of this server is for developers to test the latest version against their application without the fear to delete user data.
-  In particular, you can [log in](https://mango-pebble-0224c3803-dev.westeurope.1.azurestaticapps.net/user/login) using `[email protected] / EBNPXY35TYkYXHs`.
+  In particular, you can [log in](https://dev.www.jabref.org/user/login) using `[email protected] / EBNPXY35TYkYXHs`.
 - PR previews:
   Every pull request is deployed to a (temporary) server, which uses the same test data as the "Test server".