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

Add how-to about running the tour offline #55

Open
wilzbach opened this issue Aug 21, 2016 · 5 comments · May be fixed by wilzbach/english#1
Open

Add how-to about running the tour offline #55

wilzbach opened this issue Aug 21, 2016 · 5 comments · May be fixed by wilzbach/english#1

Comments

@wilzbach
Copy link
Member

From @wilzbach on June 13, 2016 17:1

As in the go tour, we could have a short page or subpage in the first pages that explains how to run the tour via dub.

Follow-up to #250

Copied from original issue: dlang-tour/core#260

@wilzbach
Copy link
Member Author

From @stonemaster on June 14, 2016 16:30

Dependency: #137

@wilzbach
Copy link
Member Author

@stonemaster afaict you need to release new git versions once you fixed something - dub will download the latest version automatically, not the latest git version.
There is also dub fetch dlang-tour --version="~master", but I am not sure whether we should recommend this command.

@wilzbach
Copy link
Member Author

Just bumping this. Basically we only need to decide whether we advertise the use of --version="~master" (imho it does make sense because for now it saves us a release process and our latest, greatest content is on "master").

... and then put the commands on the welcome pages:

dub fetch dlang-tour  --version="~master"
dub run dlang-tour

@stonemaster
Copy link

I am definitely for master way because this saves us a lot of process. And basically we have a stable master approach so we should always make sure that master is the latest and greatest and always running.

@wilzbach
Copy link
Member Author

wilzbach commented Jun 5, 2017

This still depends on dlang-tour/core#443

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 a pull request may close this issue.

2 participants