Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bullet Train Update: 1.7.10 #31

Merged
merged 5 commits into from
May 30, 2024
Merged

Bullet Train Update: 1.7.10 #31

merged 5 commits into from
May 30, 2024

Commits on May 30, 2024

  1. Split up bin/configure into a series of smaller scripts (#1478) 

    * Getting started on splitting up bin/configure

* a little polish

* checks for postgres and redis

* more splitting of bin/configure

* a little more progress

* Commit changes after updating configs

* Add some scripts for adding 'deploy to __' buttons, also some clean up

* Should add the deploy buttons after we've set up a repo

* A little more polish

* some polish

* Fix the heroku button text

* dang linter

* robustify postgres detection

* Make it more clear wich subscript we're currently running

* handle the case where redis-cli isn't installed

* dang linter

* A little polish

* Replace the old script with the new one

* Fix some comments
    @jagthedrummer
    jagthedrummer authored May 30, 2024
    Configuration menu
    Copy the full SHA
    21704ad View commit details
    Browse the repository at this point in the history

  2. Fix Heroku deploys for yarn 4 (#1498) 

    * Fix Heroku deploys for yarn 4

Heroku recommends having the `heroku/nodejs` buildpack before
`heroku/ruby`. So I updated `app.json` to to that.

But the `heroku/nodejs` buildpack tries to run `yarn build`
automatically. But our build steps shell out to bundler, and since
`heroku/ruby` comes after `heroku/nodjs` bundler isn't yet available.

Adding a `heroku-postbuild` script makes it so that Heroku runs _that_
script instead of running the normal `build` script. Which prevents the
lack of ruby/bundler from being a problem during the setup phase for the
`heroku/nodejs` buildpack.

Then to ensure that `yarn build` is run, I've added that to the end of
the `release` phase in `Procfile`.

* Don't need to manually call 'yarn build'

* Update the message about heroku-postbuild
    @jagthedrummer
    jagthedrummer authored May 30, 2024
    Configuration menu
    Copy the full SHA
    5d7fe47 View commit details
    Browse the repository at this point in the history

  3. Update Node.js to version 20.14.0 (#1497) 

    Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>
    @depfu
    depfu[bot] authored May 30, 2024
    Configuration menu
    Copy the full SHA
    12b3475 View commit details
    Browse the repository at this point in the history

  4. BT-Core version bump: - 1.7.10 (#1499) 

    Co-authored-by: jagthedrummer <[email protected]>
    @jagthedrummer
    jagthedrummer and jagthedrummer authored May 30, 2024
    Configuration menu
    Copy the full SHA
    25b483f View commit details
    Browse the repository at this point in the history

  5. Merge tag 'v1.7.10' 

    # Conflicts:
#	Gemfile.lock
    @jagthedrummer
    jagthedrummer committed May 30, 2024
    Configuration menu
    Copy the full SHA
    26ae189 View commit details
    Browse the repository at this point in the history