search

badcamp / badcamp-2019

MIT License
1 stars 1 forks source link

#39: Readme dev-ified to help people get set up #40

Closed torenware closed 5 years ago

torenware commented 5 years ago

Readme expanded with How-To-Get-Started info. Docksal centric, since folks who are strongly opinionated about dev environments most know how to fend for themselves.

By all means check the recipes for correctness, language mistakes, and anything else. Also, might be too long; if we need to reroll this to split it into two files, fine with me too.

torenware commented 5 years ago

@sean-e-dietrich: Is there some reason this has not been merged? If you have a problem with the PR, please state. I'm happy to fix any problems. But it's important that patches and PRs at least get a response. Accept it and merge it, give feed back so it's acceptable, or reject it with an explanation.

torenware commented 5 years ago

RE: initial setup of a local install for docksal: so the first command after pulling the repo is “fin init” rather than “fin site-init”? The commands as written was what I actually did; fin site-init did not do the global yarn install for gulp.

If “fin init” is preferred, I’ll do that instead.

On Apr 30, 2019, at 3:11 PM, Sean Dietrich notifications@github.com wrote:

@sean-e-dietrich commented on this pull request.

In README.md https://github.com/badcamp/badcamp-2019/pull/40#discussion_r279956367:

+ +- cd' into your badcamp-2019 directory, start up your virtual environment, and start installing drupal and other dependencies. + +fin start +fin site-init + +- Docksal now downloads docker images for your install, and runs composer to download the right version of Drupal and initialize it. It will also pull down a current (dev?) database from Pantheon and load it for you. + +- You now have a Drupal environment, but most likely it isn't quite ready. For one thing, the CSS will likely be messed up. In addition, the database's cache is stale enough to keep the site from coming up. Both issues are easy to fix. + +- To fix the CSS issue, you need to set up gulp to compile your CSS. You'll need to make sure gulp is installed in the containers, and you'll need to run gulp periodically to recompile your CSS, as so: + +fin exec npm install -g gulp-cli +cd web/themes/custom/bay_area_camp +fin exec npm install +fin gulp gulp is already installed globally when someone runs fin init and this block can actually be shortened to be fin gulp

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/badcamp/badcamp-2019/pull/40#pullrequestreview-232431582, or mute the thread https://github.com/notifications/unsubscribe-auth/AACOUZJJIVOG5NBQT54GDUTPTC727ANCNFSM4HH7QV4A.