Server error - with latest addition of content files (even after fixing YAML)

[lisad]

 Traceback (most recent call last):
  File "/layers/google.python.pip/pip/lib/python3.11/site-packages/django/core/handlers/base.py", line 197, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/google.python.pip/pip/lib/python3.11/site-packages/django/utils/decorators.py", line 134, in _wrapper_view
    response = view_func(request, *args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/google.python.pip/pip/lib/python3.11/site-packages/django/views/decorators/cache.py", line 62, in _wrapper_view_func
    response = view_func(request, *args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/google.python.pip/pip/lib/python3.11/site-packages/django/contrib/admin/sites.py", line 242, in inner
    return view(request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/srv/portmap/core/admin.py", line 55, in populate
    get_content_files()
  File "/srv/portmap/core/articles.py", line 51, in get_content_files
    raise RuntimeError("Failed to generate index file")
RuntimeError: Failed to generate index file 
ERROR:root:Error generating index file: [Errno 30] Read-only file system: 'staticviews/index.html'

The error of "Read-only file system" is interesting: sometimes it's not read-only, but sometimes it is. Could it be that this only happens during deploy when the deploy isn't quite finished?

I'd call this a low priority, except that we might have to fix this when we move portmap to "cloud run" from appengine. The right fix for Google Cloud architecture is probably to stash the pre-calculated index.html file in a Google Cloud Storage bucket instead of in the instance storage.