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

Project Scaffolding #2

Merged
merged 6 commits into from
Aug 13, 2018
Merged

Project Scaffolding #2

merged 6 commits into from
Aug 13, 2018

Conversation

virkt25
Copy link
Contributor

@virkt25 virkt25 commented Aug 9, 2018

This creates the scaffolding for this example. The app was generated using lb4 shopping. Subsequent changes to the application are documented based on commits (should also make review easier).

COMMITS

  • feat: project scaffolding using lb4 app
  • chore: add license, license headers for code files
  • style: add markdown and commit message linting
  • chore: update .gitignore
  • docs: update README.md
  • ci: add appveyor and travis config

@virkt25 virkt25 requested review from raymondfeng and a team August 9, 2018 04:23
@virkt25 virkt25 self-assigned this Aug 9, 2018
package.json Outdated
@@ -0,0 +1,81 @@
{
"name": "shopping",
Copy link
Contributor

Choose a reason for hiding this comment

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

@loopback/example-shopping?

@raymondfeng
Copy link
Contributor

I'm curious why this example is not added to loopback-next/examples.

@virkt25
Copy link
Contributor Author

virkt25 commented Aug 9, 2018

Well, this repository will be connected to a database (MongoDB most likely) for testing on Travis which could significantly slow down the builds for loopback-next.

@bajtos comment from loopbackio/loopback-next#1476 (comment)

With that said, there is still a question whether this example should live in our main loopback-next monorepo, or in its own GitHub repo. Considering the cost of setting up a Redis instance, a database server, etc. I think we should keep this example out of our main monorepo. I don't want to start a Docker container with Redis every time I test a change in loopback-next!

@raymondfeng
Copy link
Contributor

That's fair.

Copy link
Contributor

@jannyHou jannyHou left a comment

Choose a reason for hiding this comment

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

👍 LGTM!

const server = await this.getServer(RestServer);
const port = await server.get(RestBindings.PORT);
console.log(`Server is running at http://127.0.0.1:${port}`);
console.log(`Try http://127.0.0.1:${port}/ping`);
Copy link
Member

Choose a reason for hiding this comment

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

IIRC, this template has been updated recently to use this.restServer.url, see loopbackio/loopback-next#1572. Could you please update the implementation of start method accordingly? Feel free to do so in a follow-up pull request, I think it will be easier to review.

@virkt25 virkt25 force-pushed the init branch 2 times, most recently from 86fa90e to e09e2b7 Compare August 13, 2018 23:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants