Sprockets::FileNotFound @primer/css/color-modes in development #2049
Comments
|
Just in case this is relevant, here's how Precious is configured in Precious::App.set(:gollum_path, Dir.pwd)
Precious::App.set(:default_markup, :markdown)
Precious::App.set(:wiki_options, {
ref: 'main',
page_file_dir: 'pages',
allow_uploads: 'dir',
bare: true,
js: true,
css: true,
emoji: true,
h1_title: true,
critic_markup: true,
redirects_enabled: false
}) |
|
Thanks for reporting this. I haven't been able to reproduce the issue yet, and I also haven't seen the styling a little off when To try to reproduce, I uninstalled the Gollum gem, reinstalled it, and then used (most of) the configuration you provided in my own config file: |
|
I would be happy to do a patch release, but I am not confident this will actually resolve the issue for you because I can't reproduce it yet. @svoop I have a couple of questions for you:
|
|
Sorry, took a moment because I had another fire to fight. I use s thin server script which works both locally as well as on my dockerized server, so the two files involved are And the Setting js and css to false doesn't change anything. The bundle is all up-to-date. |
|
Thank you for the info! Will report back. |
|
Not sure if this adds anything. The error ends slightly different but missing the same file. config.rb file: compose.yaml File structure: If set the APP_ENV to As mentioned, my error ends differently. Presumably since I use the given rackup server, not puma. For whatever reason it shows twice with one reload of the Backend.md file, receiving Error 500 when asking for the file: |
|
@SayuShira Thank you, this is helpful. I was able to reproduce the issue. I was also able to verify that recompiling the assets does not resolve the issue. |
|
Now that I read over this whole thread again: it makes sense to me why this works when in production mode and not in development. In development these styles would live within the So in the end, I feel like this is sort of the expected behaviour. But the user experience is unacceptable, clearly! if |
|
One more comment today for anyone else wanting to reproduce: simplest reproduction (imo) is: I don't really understand if we/why we support running Gollum in many |
|
This is related to #1847 |
After upping to gollum-6, in APP_ENV development, the following happens:
It appears to be working in APP_ENV production, but the styling is a little off. Maybe a problem with the bundled assets prior to cutting the release?
The text was updated successfully, but these errors were encountered: