You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Description
A clear and concise description of what the bug is and how to reproduce it.
Steps to reproduce for using ruby:
1.clone the template (from github)
2. Update gem file of sass library into saasc
3. execute this cmd : Gem install bunder
4. execute this cmd : bundle installed
5. execute this cmd : bundle exec middleman build
6. screen.css.scss file are showing some error when build , so remove this: // and add /* */ only inside the css class
7. after fixes of scss file again build it and then
8. execute this cmd : bundle exec middleman build
once server started , the ui look like collapsed screen shot were attached below
Using docker
the following issue were if use docker option to build it in windows machine.
I followed the instructions as per the Docker integration and found I was not able to publish a version of my Slate documentation as there were line endings issues, "/usr/bin/env: ‘bash\r’: No such file or directory" when tried with a slightly different methodology there were issues about Gemfiles and bundle not existing, which I understand to be Ruby specific. Is there a way to publish without downloading Ruby
Always docker steps:
Screenshots
If applicable, add screenshots to help explain your problem.
If using ruby to do we are getting build issue and UI looks like collapsed.
Browser (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Last upstream Slate commit (run git log --author="\(Robert Lord\)\|\(Matthew Peveler\)\|\(Mike Ralphson\)" | head -n 1):
Put the commit hash here
The text was updated successfully, but these errors were encountered:
These two gems are not fully API compatible, so not surprised that this breaks the CSS. I cannot offer advice on how to get it working as I'm not familiar enough with ruby or the sass ecosystems to understand what the solution might be to upgrade.
For the docker issue, it sounds like you're running into the same issue as #1654. If you edited this line of the Dockerfile:
I'd like to focus on getting the Docker container working for you as that'll be easier for me to help you with, as I don't have a Windows machine available to give you advice on what might be going wrong.
Bug Description
A clear and concise description of what the bug is and how to reproduce it.
Steps to reproduce for using ruby:
1.clone the template (from github)
2. Update gem file of sass library into saasc
3. execute this cmd : Gem install bunder
4. execute this cmd : bundle installed
5. execute this cmd : bundle exec middleman build
6. screen.css.scss file are showing some error when build , so remove this: // and add /* */ only inside the css class
7. after fixes of scss file again build it and then
8. execute this cmd : bundle exec middleman build
once server started , the ui look like collapsed screen shot were attached below
![image](https://user-images.githubusercontent.com/108329588/186689083-e1ce98a0-c2e3-48e8-b571-be153e861368.png)
Using docker
the following issue were if use docker option to build it in windows machine.
I followed the instructions as per the Docker integration and found I was not able to publish a version of my Slate documentation as there were line endings issues, "/usr/bin/env: ‘bash\r’: No such file or directory" when tried with a slightly different methodology there were issues about Gemfiles and bundle not existing, which I understand to be Ruby specific. Is there a way to publish without downloading Ruby
Always docker steps:
Screenshots
If applicable, add screenshots to help explain your problem.
If using ruby to do we are getting build issue and UI looks like collapsed.
Browser (please complete the following information):
Last upstream Slate commit (run
git log --author="\(Robert Lord\)\|\(Matthew Peveler\)\|\(Mike Ralphson\)" | head -n 1
):Put the commit hash here
The text was updated successfully, but these errors were encountered: