Repository navigation
Write a script to update site.time and add TRAVIS CI #1
Description
Jekyll would usually show old posts(=workshops) and no posts that have a future date. We turned the behavior around with these code lines:
{% assign curDate = site.time | date: '%s' %}
{% for post in site.posts %}
{% assign postStartDate = post.date | date: '%s' %}
{% if postStartDate >= curDate %}
<li>
<span class="post-meta">{{ post.date | date: "%b %-d, %Y" }}</span>
<h2>
<a class="post-link" href="{{ post.url | prepend: site.baseurl }}">{{ post.title }}</a>
</h2>
</li>
{% endif %}
{% endfor %}
This works fine. The only problem is that site.time only gets updated once we deploy. And we might not deploy everyday. (A deploy happens everytime we push to gh-pages branch.)
💡 The idea is to write a script that updates site.time everyday.
Activity
yokolet commentedon Aug 15, 2016
I think Travis CI has a setup to run every day. Through, Travis CI, I guess this process can be automated.
Malwine commentedon Sep 28, 2016
Hi @yokolet I merged your last PR. Thank you for it 💯
Would you like to take this issue over and set up Travis?
yokolet commentedon Oct 28, 2016
https://github.com/jirutka/rake-jekyll is promising. Travis CI hits rake task which hooks up a redeploy.
I'll try this using test website. But, it's nice if someone test and report how to do at this website.
Malwine commentedon Apr 10, 2017
Moving the other issue documentation here: If there is a way to prebuild Jekyll in Travis it would be nice to set it up for future contributors.
[-]Write a script to update site.time[/-][+]Write a script to update site.time and add TRAVIS CI[/+]Malwine commentedon Apr 10, 2017
For doumentation:
but I guess we can move it once the repo is public
Malwine commentedon Apr 11, 2017
Hi @davidchambers, we need to discuss one thing. With the help of my great Travis friend Lisa we set up Travis now 🎉
If we want to use a
cron jobthere, that would run a script and redeploy the website every day to get the current time, then it will do a push a commit every day. That would mean that we have 365 commits per year polluting our git history.What do you think about that?
davidchambers commentedon Apr 11, 2017
I'm not overly bothered by this, actually. Your proposed solution sounds straightforward and (I hope) reliable. Let's not complicate things. :)
Also, go Lisa! 🎉
Malwine commentedon Apr 11, 2017
Todo:
davidchambers commentedon Oct 1, 2018
I have not been able to push commits from Travis CI (see #52 and #58 for my attempts). To get things going I created a script on my computer and told launchd to run it every 12 hours. The first run resulted in 6a1cb91. I'll keep an eye on the script for a few days to determine whether the approach is reliable.
davidchambers commentedon Oct 4, 2018
The script is working. It won't run if my computer is asleep, but I'm happy to put this issue to bed. :)
davidchambers commentedon Mar 20, 2019
My script has stopped working, so we should make another effort to get a Travis cron job to work.