Skip to content
New issue

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

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

Already on GitHub? # to your account

fn: improve UX and publish/deploy command #359

Merged
merged 6 commits into from
Dec 1, 2016
Merged

fn: improve UX and publish/deploy command #359

merged 6 commits into from
Dec 1, 2016

Conversation

ucirello
Copy link
Contributor

@ucirello ucirello commented Nov 29, 2016

Fixes #352
Partially addresses #364

@ucirello ucirello changed the title fn: improve UX and publish/deploy command [WIP] fn: improve UX and publish/deploy command Nov 29, 2016
@ucirello ucirello changed the title [WIP] fn: improve UX and publish/deploy command fn: improve UX and publish/deploy command Nov 30, 2016
@ucirello
Copy link
Contributor Author

@ucirello ucirello force-pushed the fn-publish branch 3 times, most recently from 9bf4ce9 to 093873e Compare November 30, 2016 17:37
@ucirello
Copy link
Contributor Author

@treeder @pedronasser @seiflotfy I have extensively checked and updated the documentation on this change.

Please review, critique and merge if OK.

# Create a route to this function on IronFunctions
fn routes create myapp /hello
fn deploy myapp
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought we were discussing that deploy would be more of a bulk operation only, for when you setup an entire app structure? What path would be used here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right. fixing it.

@ucirello ucirello merged commit 9ac2539 into master Dec 1, 2016
@ucirello ucirello deleted the fn-publish branch December 1, 2016 17:11
Copy link
Contributor

@treeder treeder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

deploy should only be used to deploy an entire app structure (recursively). And I think we were still discussing what the command name should be to avoid confusion. Something that says that it's a bulk deploy or a full app deploy.

# Create a route to this function on IronFunctions
fn routes create myapp /hello
fn deploy myapp
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should still be push and routes create, not deploy.

# Create a route to this function on IronFunctions
fn routes create slackbot /guppy
fn deploy slackbot
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same

ucirello added a commit that referenced this pull request Dec 1, 2016
@ucirello ucirello mentioned this pull request Dec 1, 2016
ucirello pushed a commit that referenced this pull request Dec 3, 2016
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants