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.

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

Fast-forward master #1

Open
wants to merge 51 commits into
base: master
Choose a base branch
from
Open

Fast-forward master #1

wants to merge 51 commits into from

Conversation

carlevans719
Copy link
Member

@carlevans719 carlevans719 commented Aug 23, 2018

This change is Reviewable

yourcelf and others added 30 commits June 28, 2016 11:28
Since we are installing a requested version now, it shouldn't be
necessary to filter by the release version string when searching for the
node binary.  Meteor has the habit of installing the next patch release
even when you request an older one (e.g. it interprets ?release=1.1.0.3
as ^1.1.0).
Support for Meteor 1.4, faster compilation, caching
yourcelf and others added 21 commits September 26, 2016 11:00
Users can still install mongolab manually -- and that's what the
usage instructions have always advised anyway.  Removing it from
bin/release allows non-mongolab users to use this buildpack without
forking.
Instead of trying to install and maintain a single release of version
only, allow meteor to do what it really wants, which is to have multiple
releases installed at once.  Install the latest from install.meteor.com,
and allow meteor to upgrade/downgrade itself as per the project
.meteor/release target.  Both/all versions of meteor will persist in the
build cache, so subsequent builds with the same release target should
still be speedy.

Identify the version of node/npm to use by asking node itself, using
"meteor node -c 'process.stdout.write(process.execPath)'".  That way, we
get the correct node version even if multiple simultaneous versions
exist.

This ought to address issues #132, #138, #145, #146.
Perform cache clearing after build
Ability to set additional node parameters
Use the published version of the buildpack from the registry.
Fix clear cache flag checking
It not defined -> If not defined
@DemiAHMS DemiAHMS deleted the branch webantic:master April 21, 2021 19:42
@DemiAHMS DemiAHMS deleted the master branch April 21, 2021 19:42
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.

10 participants