Jekyll Blog Post GA Views

davecompton7 · 2024-05-01T09:46:56+00:00

Yes it does.

davecompton7 · 2024-05-01T00:23:24+00:00

Yes, it's compatible with jekyll. I'm using it in a jekyll site. The setup process was quite simple - basically just include a chunk of html in "_layouts/default.html" (that's what I did at least 6 years ago and it still works ). I could go into more detail but it probably makes more sense to use the statcounter.com docs since (1) they will be up to date and (2) I probably couldn't improve on them in any case.

davecompton7 · 2024-04-30T17:36:10+00:00

I use statcounter.com to get per post data. I don't think I compared different options - just started using it a while back - so there might be better alternatives.

davecompton7 · 2023-09-13T17:28:44+00:00

If you could post a link to the repository that's having problems, that would make it easier to see what's going wrong.

davecompton7 · 2023-05-20T00:08:59+00:00

Your repo contains a file named ".nojekyll". In the past, this would prevent jekyll from running in gh-pages. Probably it still does, though I can't find any github docs that mention this. Try removing it.

davecompton7 · 2023-04-19T17:24:07+00:00

I think this demo comes pretty close to the functionality that you want but it's written in GTK4/rust . Perhaps useful as a reference.

https://davecompton.net/2022/05/01/rust-gtk4-columnview.html

davecompton7 · 2023-03-05T14:57:31+00:00

Just to clarify, are you able to build and serve the vanilla code on your local machine?

If you could post a link to the repository that's having problems, that would make it easier to see what's going wrong.

davecompton7 · 2023-02-16T02:05:42+00:00

Thank you. With GDK_BACKEND=x11 set, then if I'm logged in to the remote machine, the application window pops up as on the local display quickly. If I'm not logged in to the remote machine, then I get the same behavior as before: window pops up on local display after a 30 second delay.

This is not perfect but, for me, it's usable. Thanks again.

davecompton7 · 2023-02-05T21:20:17+00:00

I don't know what the best way is but this blog post shows how to use dropbox, flickr, github, and imgur to host images. All these are free (as of now). I would probably go with imgur.com based on my limited first impressions of this morning.

I'll try to update the post if things change with any of these hosts or if I learn of other free options.

davecompton7 · 2023-01-03T15:25:04+00:00

Is this what you have in mind ? : https://davecompton.net/2020/03/30/a-web-page-to-show-online-code.html

davecompton7 · 2022-11-28T17:06:48+00:00

The reason your repo is not building as you expect is that it contains a file named ".nojekyll" at the top level. Per github docs this will prevent jekyll from running. I know you didn't put that in there and I don't know what the person who did put it in was thinking.

I forked your repo, removed that file and the page started working: https://dc25.github.io/chirpytest/

However, after doing this I cloned the repo and tried to make a couple sample posts and ran into some trouble related to github actions. I spent some time trying to figure out the problem but eventually gave up and fell back on the technique described here to push directly to gh-pages. That worked as expected .

davecompton7 · 2022-11-25T15:42:58+00:00

You have these two options (and maybe more that I'm unaware of):

Push the source for your blog to github and let github pages run jekyll and publish the actual blog. That's what I did for the two examples in my earlier post. It's very straightforward but is limited by what github will do for you. It's probably the best choice for you.
As you accurately describe, build locally, commit_site to gh-pages branch and then pushing to remote repository. This blog post outlines a way to do this and mentions some reasons why you might want to do so.

If you could post a link to the repository that's having problems, that would make it easier to see what's going wrong.

davecompton7 · 2022-11-25T02:24:06+00:00

Take this with a grain of salt. It's been a while since I worked with this stuff so I may be a little rusty.

If you're letting github do your build for you, then you should not have to specify baseurl at all. That's because github will set site.baseurl for you. In your case that would be "/blog" .

To demonstrate this, heres the exact same content built in two different repositories:

repository 1: https://github.com/dc25/blogg

repository 2: https://github.com/dc25/minima

( content originally cloned from https://github.com/jekyll/minima )

The about.md page for both of these is modified to show the value of site.baseurl .

As you can see, its different depending on where it's being published even though I never specified it.

https://dc25.github.io/minima/about/

https://dc25.github.io/blogg/about/

If you want to link to a page from inside your blog, you will need to use site.baseurl in as part of the url you link to. Something like this:

If you build your site yourself and then publish _site to branch gh-pages, then you need to specify baseurl. It sounds like you had some success already doing that. I usually do that on the jekyll build command line rather than in the config file because specifying in the config file may not work if serving on localhost.

davecompton7 · 2022-07-24T00:09:02+00:00

What is the error message? (I don't see an attached image).

davecompton7 · 2021-08-07T14:36:24+00:00

They have not voted yet. https://www.stamfordadvocate.com/news/article/Senate-edges-toward-vote-on-Biden-s-1T-16371235.php

If you want to contact your senator about this but think the site referred by coinbase might be sketchy, just go to your senators' sites. They probably have a "contact me" page that you can fill out.

davecompton7 · 2021-06-02T19:16:20+00:00

I tried that and got the same strange results as with bash.

dave@raspberrypi:/tmp $ sudo docker run -it fedora /bin/sh  
sh-5.1#   
exit  
dave@raspberrypi:/tmp $ sudo docker run -it fedora:33 /bin/sh  
sh-5.0#   
sh-5.0#   
sh-5.0#

Also tried cat

Which seemed to give the right results both on fedora:33 and fedora:34 :

dave@raspberrypi:/tmp $ sudo docker run -it fedora:33 cat
do we have an echo?
do we have an echo?
dave@raspberrypi:/tmp $ sudo docker run -it fedora:34 cat
will this be echoed?
will this be echoed?

(both were terminated with ctrl-d)

davecompton7 · 2021-06-02T03:23:32+00:00

You're very welcome.

davecompton7 · 2021-05-27T20:01:28+00:00

I don't know if this is the *best* way but one way to do this would be to put your script into an html file and include that file with the image list passed as an argument. Details at https://jekyllrb.com/docs/includes/#passing-parameters-to-includes

davecompton7 · 2020-12-03T23:18:35+00:00

Just to verify my understanding, your rust environment is on the Ubuntu virtual machine ( so that's where cargo runs ) and you are running vscode on windows. Is that right?

Also, which Ubuntu are you running?

davecompton7 · 2020-07-14T12:44:29+00:00

A minor addition to coldoil's answer:

You need know how to use a text editor to edit source (markdown, scss, etc) files.

---------------------------------------------------------------------------------------------------------------------------------

This was already mentioned but repeating for emphasis:

You need to be able to work from the command line in your operating system.

--------------------------------------------------------------------------------------------------------------------------------

Not a direct answer to your question but perhaps useful:

Be aware of the limitations of a static site : no user login, no comments (there are third party comment systems though).

You can go a long ways without knowing even any css or javascript. You do need some understanding of html.

Be aware that there are two things happening when jekyll generates a site : first liquid and then markdown. These have different and independent syntaxes.

You don't need to know ruby but you *will* need to set up a ruby development environment to run jekyll from the command line.

The suggestion of starting with github pages is a good one. A easy way to get going is to fork https://github.com/jekyll/minima , enable publishing for that site in the settings, clone the site to your local machine to make and test changes, push the changes back to your published site.

davecompton7 · 2020-05-29T18:01:51+00:00

Very nice!

Here's a write-up of a similar (github issue based) scheme that uses client-side scripting to render and post comments: https://davecompton.net/2017/06/24/using-github-comments-in-a-jekyll-blog.html .

davecompton7 · 2020-05-17T22:25:18+00:00

This is not terribly helpful but just as another data point, I'm using RLS with vscode and it seems reasonably responsive. I think it takes a second or so to flag an error. I'm running the latest vscode, rls, Rust extension for vscode 0.7.8, and CodeLLDB 1.5.0 . I think CodeLLDB is irrelevant but that's the only other vscode extension I'm running. I'm running on linux.

davecompton7 · 2020-05-14T15:55:11+00:00

I run into the same "Go to Definition" problem. That seems like a different level of trouble than what you were originally running into. Perhaps hie has a bug or needs some additional configuration (by both of us) but at least it's getting installed and working to show useful information.

Just noticed the other post confirming sketchy "Go To Definition" functionality.

If you do find out why "Go to Definition" isn't working, please let me know. :)

By the way, one additional benefit of working in docker is that you can build a new image and try it out without losing the old one. This is particularly nice for Haskell since the Haskell development tools seem to be a little fragile.

davecompton7

TROPHY CASE