Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

setup script/server #11

Closed
jglovier opened this issue Aug 15, 2014 · 9 comments
Closed

setup script/server #11

jglovier opened this issue Aug 15, 2014 · 9 comments
Labels
help wanted indicates that an issue is open for contributions

Comments

@jglovier
Copy link
Member

@jkleinsc can we setup a script/server command that initiates both Couch and ember serve?

@jkleinsc
Copy link
Member

@jglovier I suppose we could. The couch part would be different depending on OS. We could at the very least have a script that tests to see if couch is up before running ember serve.

@jglovier
Copy link
Member Author

Yeah, even if it just triggered ember serve, it would benefit those familiar with the script/server convention by standardizing the approach. If more things were required, it could also output a warning like Be sure to run Couch.app, etc.

@tangollama tangollama added the help wanted indicates that an issue is open for contributions label Aug 5, 2015
@filipesperandio
Copy link

I like the idea.
I am also very fan of Makefiles and I can open a PR for that if people think it is valuable and are comfortable using make.

@jkleinsc
Copy link
Member

jkleinsc commented Feb 5, 2016

@filipesperandio I don't think we need a Makefile since there aren't any executables for this project that get built. It's an ember web app and the way it gets built is via ember build.

@filipesperandio
Copy link

I understand that. make helped me in the past even on script projects smoothing out dependencies.
for example a target make serve could depend on ember-cli and bower being installed.

@filipesperandio
Copy link

@jglovier script/server OR scripts/server ? (with an s at the end of scripts)

@jkleinsc
Copy link
Member

jkleinsc commented Feb 5, 2016

@filipesperandio gotcha. Thanks for clarifying.

@jglovier
Copy link
Member Author

jglovier commented Feb 5, 2016

@filipesperandio I prefer script/server but probably just because it is a convention we use at GitHub. Also, it mentally makes sense when you are running any one given script at a time. I.e. mentally I think "I'm going to run the server script" so it's semantically consistent from that perspective. But it's probably not that big a deal LOL.

@filipesperandio
Copy link

Cool, I will adjust.
On Feb 5, 2016 7:01 PM, "Joel Glovier" [email protected] wrote:

@filipesperandio https://github.com/filipesperandio I prefer
script/server but probably just because it is a convention we use at
GitHub http://githubengineering.com/scripts-to-rule-them-all/.


Reply to this email directly or view it on GitHub
#11 (comment)
.

matteovivona pushed a commit that referenced this issue Jan 15, 2021
…-run-test

test(hospital-run): convert to RTL
vasanthkumar97 pushed a commit to xcaliber-health/hospitalrun-frontend that referenced this issue Oct 8, 2022
…NTMENT

filtering by type of appointment and integration of get appointment
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted indicates that an issue is open for contributions
Projects
None yet
Development

No branches or pull requests

4 participants