On 9/29/24 00:59, Odhiambo Washington via Mailman-users wrote:
Could you allow me to revisit this issue since I haven't solved it? First, I bypassed CloudFlare DNS proxying just to ensure I have nothing is coming in between my browser and the web server. That did not help with the issue of the "missing" CSS files.
Then you have som other issue in your configuration.
Ideally, I should not be creating these symlinks, right? On my old server the symlinks weren't necessary.
That is correct.
I have created some symlinks and that appears to help with Apache. I will test with Nginx and see how it goes.
root@eu:/opt/mailman/mm/static/CACHE/css# ls -al total 196 drwxr-xr-x 2 mailman mailman 4096 Sep 29 10:40 . drwxr-xr-x 4 mailman mailman 4096 Mar 21 2024 .. lrwxrwxrwx 1 mailman mailman 23 Sep 29 10:40 output.ac23d5f5127c.css -> output.d29798365ddb.css lrwxrwxrwx 1 mailman mailman 23 Sep 29 10:31 output.bacec526ec98.css -> output.e69dbb26da3b.css -rw-r--r-- 1 mailman mailman 1209 Mar 21 2024 output.d29798365ddb.css -rw-r--r-- 1 mailman mailman 569 Mar 21 2024 output.e68c4908b3de.css -rw-r--r-- 1 mailman mailman 180904 Mar 21 2024 output.e69dbb26da3b.css root@eu:/opt/mailman/mm/static/CACHE/css#
My question though: What is the source of truth for the files that should be in /opt/mailman/mm/static/CACHE/css/ ??
When you run django-admin collectstatic --clear ...
it removes all the
old files from the static/ directory and installs new ones. At this
point static/CACHE/ contains no files. Then when you run django-admin compress
it creates three output.*.css files in static/CACHE/css and
one output.*.js file in static/CACHE/js and creates a
static/CACHE/manifest.json file that points to those four files and
which is what Django uses for the paths to put in the relevant <script
...> and <link rel="stylesheet" ...> tags in the pages it serves. I.e.
static/CACHE/manifest.json is the source of truth.
Maybe that is what I need to focus on. If need be, then I should *fix* the contents of that file so that it doesn't contain the nonexistent files, no?
I very much doubt that it does contain the nonexistent files since it is
built by the same django-admin compress
that creates the output* files.
Lastly, why is it that my https://mm3-lists.kictanet.or.ke/archives/ does not display content similar to what https://lists.mailman3.org/archives/ does? What change should I make in which settings.py?
This is a clue. I presume you actually have archived lists. There is something very wrong in your configuration if HyperKitty is not finding those lists. Possibly you have more than one WSGI server running and you aren't always proxying to the correct one. That seems far fetched to me, but without seeing all your web server, WSGI server and Django configurations, I have no idea what the issue could be.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan