Hi. I get the following error when running ./installer rebuild web_only on the latest releases of discoures. fs.js:114 throw err; ^ Error: ENOENT: no such file or directory, open 'root='/assets',url='/assets/vendor-4681e47c140b5a5bea2bfb1fec89365858288a8ea0c21979c0167ad9b570ee3d.js.map'' …

We saw this before somewhere else. Can you try ./launcher cleanup git pull ./launcher rebuild app If that does not work try removing all the containers on the machine and all images.

Thanks for the quick response @sam . I will try that. Quick question. The “git pull” I am assuming pulls the latest version of discourse-docker right? In general, is it necessary to upgrade discourse-docker and discourse at the same time? Currently, I don’t have discourse-docker controlled by git…

[Bild] russellwstanley: I think I’m swimming against the tide here with discourse Very true words you have entered a 100% unsupportable state with this hackery :flushed_face: Recommend you pull latest from git asap Old docker images of discourse base are incompatible with current discourse,…

Thanks @sam . I’ve done that and I am able to build the new version now. Fortunately, this was all on beta so no harm done :slight_smile: I’m not sure it is “hackery” to want a repeatable build though :thinking: The thing I am trying to get here is the ability to roll back to a known good version. S…

If you want repeatable builds you got to pin your discourse version to a specific sha via your container config, and every plugin That means you stop getting fixes to discourse, security fixes to docker image and so on, but the build will be pretty repeatable You may need to amend templates as wel…

Ok, I already pin the version of discourse to a specific commit and I can also do this for plugins. But if I don’t also pin discourse-docker, won’t this result in a situation where discourse-base gets updated on every build but discourse does not. Won’t that just result in a similar incompatibility …

I am confused, how did this error show up if you have discourse pinned to something old? If NGINX has a critical vulnerability do you want that fixed?

The error showed up when I moved the pinned version of discourse forward from 2.4.0.beta2 to 2.4.0beta8 Yes of course I would like to have critical vulnerabilities in dependent software systems fixed when I run a new build! Sounds Fantastic! However, I would also like to be able to roll back in t…

yeah, you got to rethink your process here. Our db migrations are not reversible. If you want to test out an upgrade without committing you need to operate in a staging sandbox

Yea, I understand that it is difficult to roll back a db migration. Discourse is obviously not built with my kind of release and deployment management strategy in mind. I should stop swimming against the tide here. I have a staging environment. So I’ll just abandon any ideas of repeatable build and…

Fehler beim Erstellen der neuesten Version

Unterstützung Installation

russellwstanley (Russell Stanley) 12. Dezember 2019 um 09:50 5

Danke, @sam. Ich habe das erledigt und kann jetzt die neue Version erstellen. Zum Glück war das alles noch im Beta-Stadium, also ist nichts passiert Ich bin mir jedoch nicht sicher, ob es „Häckelei

Thema		Antworten	Aufrufe
Failing to rebuild app on Discourse since May 7 Self-hosting	13	2359	14. Mai 2019
Rebuild failed - FAILED TO BOOTSTRAP Self-hosting	20	2316	28. Dezember 2023
Bug With Rebuilding version: v2.4.0.beta1 Self-hosting	8	1316	5. Mai 2020
Urgent, rebuild failed from old version Self-hosting	5	555	8. Mai 2023
Launcher rebuild app Failure Self-hosting	6	879	6. Februar 2024

Fehler beim Erstellen der neuesten Version

Verwandte Themen