Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 21 21:09
    sweethuman closed #76
  • Feb 04 10:51
    SammyTheHand commented #75
  • Feb 01 13:21
    SammyTheHand commented #75
  • Sep 13 2018 10:29
    elmatou closed #80
  • Sep 13 2018 10:29
    elmatou commented #80
  • Sep 13 2018 10:21
    elmatou opened #80
  • Aug 30 2018 20:44
    cbeauhilton commented #70
  • Aug 08 2018 16:57
    enginpost opened #79
  • Jul 02 2018 16:30
    dmxt opened #78
  • Jun 19 2018 03:24
    cryobry edited #77
  • Jun 19 2018 03:24
    cryobry opened #77
  • May 18 2018 15:15
    sweethuman opened #76
  • May 07 2018 20:53
    dylan-k closed #68
  • Apr 30 2018 18:24
    fyemath commented #66
  • Apr 28 2018 01:51
    fyemath opened #75
  • Apr 02 2018 10:08
    davidmcneal28 commented #74
  • Apr 02 2018 08:07
    davidmcneal28 opened #74
  • Mar 24 2018 13:19
    elijahbal opened #73
  • Mar 17 2018 19:54
    bennettscience closed #72
  • Mar 17 2018 19:23
    bennettscience opened #72
Adam Laycock
@Arcath
Whoops
had left the toolbar specs in
after removing the toolbar...
mcnesium
@mcnesium
I am trying to reach a page from within jekyll. in the frontmatter I added permalink: .well-known/acme-challenge/xxxxxx and then try to go to that page. when running the jekyll server from within atom, it says "not found" while when I run "jekyll serve" from the command line, it works fine. why is this?
(actually I am trying to find out, why this also does not work on the gitlab pages hosted website, which I am trying to get a letsencrypt certificate with)
mcnesium
@mcnesium
okay I found out that it works on both servers if .html is added to the permalink in the frontmatter
now lets see if letsencrypt likes this
Adam Laycock
@Arcath
@mcnesium I normally use lets encrypt with the web server. So instead of having jekyll or what ever app trying to provide the endpoint just add a virtual directory in apache (or what ever server)
mcnesium
@mcnesium
due to some gems dependencies i need to run bundle exec jekyll build on that one project. now jekyll-atom fails the site build, propably because it tries just jekyll build
i tried to change the build command, but that did not change the issue
nor the setting in _config.yml
so how exactly do I need to enter the build path?
Adam Laycock
@Arcath
Atom does some weirdness with $PATH
If you run which bundle
mcnesium
@mcnesium
I tried to enter that setting: /home/ml/.gem/ruby/2.4.0/bin/bundle exec jekyll, build
Adam Laycock
@Arcath
There needed to be a comma between each entry
/home/ml/.gem/ruby/2.4.0/bin/bundle, exec, jekyll, build
I'd recommend doing it in _config.yml if its only for one project
mcnesium
@mcnesium
i see, but it still fails though. can I get some logs from atom?
do I need to restart atom after changing those settings?
mcnesium
@mcnesium
looks like restarting is required. atom then needs two tries to restart xD
Adam Laycock
@Arcath
I will test that for the next release
mcnesium
@mcnesium
also, it then works using just > #
atom:
buildCommand:
    - bundle
    - exec
    - jekyll
    - build
why does this not work with one line using quotes?
Adam Laycock
@Arcath
Nodes child process works with (executable, args)
mcnesium
@mcnesium
ok
Adam Laycock
@Arcath
so I need it as an array where I call (array[0], array[1..array.length])
mcnesium
@mcnesium
well, thanks for helping me out @Arcath
Adam Laycock
@Arcath
If i did a string split on " " it would fail with users having folders or options with spaces in
not a problem