Skip to content

DEV: re-split build vs configure#878

Merged
featheredtoast merged 1 commit intomainfrom
update-build-compile-steps
Aug 1, 2025
Merged

DEV: re-split build vs configure#878
featheredtoast merged 1 commit intomainfrom
update-build-compile-steps

Conversation

@featheredtoast
Copy link
Copy Markdown
Member

@featheredtoast featheredtoast commented Oct 6, 2024

Allow for assets to be precompiled fully in a build image.

The only remaining things for configure is update themes, maxmind download, and css compiling.

Moves ~30 seconds of work from a configure step to a build step, allowing for very quick precompile-on-boot times.

Dev:

  • Update web template test from golang to be a symlink.
  • Ensure restarting of the unicorn service on migrate/precompile failure

@featheredtoast featheredtoast force-pushed the update-build-compile-steps branch from b678c85 to ce87230 Compare October 7, 2024 22:28
@featheredtoast featheredtoast changed the title DEV: re-split build vs compile DEV: re-split build vs configure Oct 11, 2024
@featheredtoast
Copy link
Copy Markdown
Member Author

@tgxworld this one allows for precompiling of most assets without connecting to any DBs, leading to very little downtime or changes in base configure stages.

This means the resulting docker layer is much thinner and those booting up from cold boot (with an image only run with build) will also be online much faster.

featheredtoast added a commit to discourse/launcher that referenced this pull request Nov 15, 2024
No need to pass SKIP_EMBER_CLI_COMPILE=1 if build/compile split calls different
asset:precompile tasks.

Depends on discourse/discourse_docker#878
@featheredtoast featheredtoast force-pushed the update-build-compile-steps branch 2 times, most recently from 37670c0 to 03ceb98 Compare November 15, 2024 22:48
@featheredtoast
Copy link
Copy Markdown
Member Author

The main piece of this work is in the templates. launcher related patches now here: discourse/launcher#4

@featheredtoast featheredtoast force-pushed the update-build-compile-steps branch from 03ceb98 to 56458bd Compare May 17, 2025 07:08
featheredtoast added a commit to discourse/launcher that referenced this pull request Jul 9, 2025
No need to pass SKIP_EMBER_CLI_COMPILE=1 if build/compile split calls different
asset:precompile tasks.

Depends on discourse/discourse_docker#878
featheredtoast added a commit to discourse/launcher that referenced this pull request Jul 10, 2025
No need to pass SKIP_EMBER_CLI_COMPILE=1 if build/compile split calls different
asset:precompile tasks.

Depends on discourse/discourse_docker#878
Comment thread templates/web.template.yml Outdated
Comment thread templates/web.template.yml
Comment thread templates/web.template.yml
@andrewschleifer
Copy link
Copy Markdown
Member

Do you have an easy way to test the template output? I am simulating it in my head and ... my head is not reliable.

@featheredtoast
Copy link
Copy Markdown
Member Author

Test part is unfortunately still rather burdensome, for the most part:

  • run a full launcher build and manually an inspect the resulting image's files.
  • run from that stage alone (with the *_ON_BOOT vars all set to 1), and check for an image booting.
  • run launcher migrate and launcher configure, and check for an image successfully booting.

Allow for assets to be precompiled fully in a build image.

The only remaining things for configure is update themes, maxmind download, and css compiling.
@featheredtoast featheredtoast force-pushed the update-build-compile-steps branch from 56458bd to d682524 Compare July 26, 2025 01:07
@featheredtoast
Copy link
Copy Markdown
Member Author

I've narrowed the scope of this, all of the service file updates are now all being done in #967

@featheredtoast featheredtoast dismissed andrewschleifer’s stale review August 1, 2025 20:13

Changes requested in review re-implemented to #967

@featheredtoast featheredtoast merged commit f859bee into main Aug 1, 2025
5 checks passed
@featheredtoast featheredtoast deleted the update-build-compile-steps branch August 1, 2025 20:13
featheredtoast added a commit that referenced this pull request Aug 1, 2025
featheredtoast added a commit that referenced this pull request Aug 1, 2025
featheredtoast added a commit that referenced this pull request Aug 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants