This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
# Login to heroku CLI. | |
heroku login | |
# Create a new app project on heroku. | |
heroku create <appName> --stack cedar --region us --buildpack https://github.com/AdmitHub/meteor-buildpack-horse.git | |
# Add heroku remote to the git config file. | |
heroku git:remote -a meteor-mdc-demo |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Expect input to be a list of file alias. | |
on run {aliasList, parameters} | |
set fileInfoList to {} | |
repeat with aliasItem in aliasList | |
set thePath to POSIX path of aliasItem | |
set theName to name of (info for aliasItem) | |
set end of fileInfoList to {thePath:thePath, theName:theName} | |
end repeat | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/** | |
* This test file should only be run explicitly. When that's the case, the command should look something like: | |
* npm run test ./some/test/folder/test-something.js | |
* which means the process arguments should be something like: | |
* [ "some/path/node", "some/path/mocha", "./some/test/folder/test-something.js" ] | |
* but we can not assume the third argument would always be a file path. | |
* So to evaluate this flag, the function should: | |
* 1. Check if argv[2] is likely a file path pointing at this file. | |
* 2. resolve argv[2] and compare with this file's absolute path. | |
*/ |
OlderNewer