Refactor: move the application directory up a level

[thekaveman]

There are two directories with application code:

• run/ is created by this image and contains the default nginx and gunicorn configuration
• app/ is created by the consuming image (benefits or eligibility-server) and contains the application code

This image defines these two directories under /home/calitp/ (the Docker $USERs home).

This PR moves them to the top-level /calitp/ (again, from the Docker $USER).

This change is part of addressing cal-itp/benefits#2153. When we enable the setting WEBSITES_ENABLE_APP_SERVICE_STORAGE=true, /home will be a directory managed by the Azure App Service, so we need the application code out of that directory.

Post-merge

Merge the following PRs

• Refactor: move the application directory up a level benefits#2156
• Refactor: move the application directory up a level eligibility-server#463

[angela-tran]

Do we need to update this path too or no?

docker-python-web/appcontainer/Dockerfile

Lines 37 to 38 in 5f949ca

	# update PATH for local pip installs
	ENV PATH "$PATH:/home/$USER/.local/bin"

[thekaveman]

Do we need to update this path too or no?

docker-python-web/appcontainer/Dockerfile

Lines 37 to 38 in 5f949ca

	# update PATH for local pip installs
	ENV PATH "$PATH:/home/$USER/.local/bin"

I don't think so, because pip install as the $USER is still going to install packages into the user's home directory (which does still exist).

You can test this by building the image:

docker compose build app

Then running the container, and running pip freeze inside the container, which should print that gunicorn is installed:

$ docker compose run app
calitp@90b7dd99b3f3:/calitp/app$ pip freeze
gunicorn==22.0.0
packaging==24.1