Upgrade infrastructure

[dalonsoa]

Among the many things, this PR

• Uses pyproject.toml for project management
• Upgrades docker image version
• Upgrades versions of other services (eg. Azurite, etc.)
• Uses our current setup for GitHub workflows
• Updates code to use modern dependencies way of doing things (eg. bootstrap)
• Replaces isort, flake8 and black with ruff
• Update pre-commit to use our current list of hooks

Close https://github.com/ImperialCollegeLondon/rse_maintenance_tasks/issues/10

[dalonsoa]

The vast majority of what appear as changed is the linters and formatters.

[AdrianDAlessandro]

Haven't had the chance to actually test it. It all seems good to me. I've made a couple of observations

[AdrianDAlessandro]

When I tried running this I got this:

Attaching to faraday-liionsden-azurite-1, faraday-liionsden-db-1, faraday-liionsden-web-1
faraday-liionsden-db-1       | 
faraday-liionsden-db-1       | PostgreSQL Database directory appears to contain a database; Skipping initialization
faraday-liionsden-db-1       | 
faraday-liionsden-azurite-1  | Azurite Blob service is starting at http://0.0.0.0:10000
faraday-liionsden-azurite-1  | Azurite Blob service is successfully listening at http://0.0.0.0:10000
faraday-liionsden-azurite-1  | Azurite Queue service is starting at http://0.0.0.0:10001
faraday-liionsden-azurite-1  | Azurite Queue service is successfully listening at http://0.0.0.0:10001
faraday-liionsden-azurite-1  | Azurite Table service is starting at http://0.0.0.0:10002
faraday-liionsden-azurite-1  | Azurite Table service is successfully listening at http://0.0.0.0:10002
faraday-liionsden-db-1       | 2024-09-06 16:10:48.223 UTC [1] FATAL:  database files are incompatible with server
faraday-liionsden-db-1       | 2024-09-06 16:10:48.223 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 15.8 (Debian 15.8-1.pgdg120+1).
faraday-liionsden-db-1 exited with code 1
dependency failed to start: container for service "db" exited (1)

It appears like this means this will not work with any existing databases. If there are no databases, then this isn't a problem.

[dalonsoa]

The whole of Liionsden resource group has been deleted, so there’s no database whatsoever.

…

---------------------------------- Dr Diego Alonso Álvarez (he/him) Head of Research Software Engineering [p.s If I send an email outside of your working hours please do not feel the urgency to respond until it is your working hours]

________________________________ From: AdrianDAlessandro ***@***.***> Sent: 06 September 2024 17:14 To: ImperialCollegeLondon/Faraday-liionsden ***@***.***> Cc: Alonso Alvarez, Diego ***@***.***>; Author ***@***.***> Subject: Re: [ImperialCollegeLondon/Faraday-liionsden] Upgrade infrastructure (PR #276) When I tried running this I got this: Attaching to faraday-liionsden-azurite-1, faraday-liionsden-db-1, faraday-liionsden-web-1 faraday-liionsden-db-1 | faraday-liionsden-db-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization faraday-liionsden-db-1 | faraday-liionsden-azurite-1 | Azurite Blob service is starting at http://0.0.0.0:10000 faraday-liionsden-azurite-1 | Azurite Blob service is successfully listening at http://0.0.0.0:10000 faraday-liionsden-azurite-1 | Azurite Queue service is starting at http://0.0.0.0:10001 faraday-liionsden-azurite-1 | Azurite Queue service is successfully listening at http://0.0.0.0:10001 faraday-liionsden-azurite-1 | Azurite Table service is starting at http://0.0.0.0:10002 faraday-liionsden-azurite-1 | Azurite Table service is successfully listening at http://0.0.0.0:10002 faraday-liionsden-db-1 | 2024-09-06 16:10:48.223 UTC [1] FATAL: database files are incompatible with server faraday-liionsden-db-1 | 2024-09-06 16:10:48.223 UTC [1] DETAIL: The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 15.8 (Debian 15.8-1.pgdg120+1). faraday-liionsden-db-1 exited with code 1 dependency failed to start: container for service "db" exited (1) It appears like this means this will not work with any existing databases. If there are no databases, then this isn't a problem. — Reply to this email directly, view it on GitHub<#276 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABOQHLURLZJFVCQZ37ZYO4DZVHIGRAVCNFSM6AAAAABNIW3HT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZUGM4TIMJWGI>. You are receiving this because you authored the thread.Message ID: ***@***.***>