why is codingdojo.org not in https ?

people should easily see how and where the content can be updated

on page list

I guess this is more of a meta-issue, but I don't know where I should take it. I want to submit a couple of PRs, but I want to make sure that I've done things right before submitting them, and I cannot replicate the environment. I've tried it three ways:

1. Following instructions

Cloning works fine. I can also start hugo server -w and go to the start page, but any link I click on that page gives a 404 (for instance "What Is Coding Dojo" leads to http://localhost:1313/WhatIsCodingDojo which only says 404 page not found).

2. Generating the static site

Checking the Dockerfile I learn that the site can be generated statically using hugo --destination=/tmp/www. Running that gives me the following output

$ hugo --destination=/tmp/www

                   | EN   
+------------------+-----+
  Pages            | 217  
  Paginator pages  |   0  
  Non-page files   |   0  
  Static files     |   1  
  Processed images |   0  
  Aliases          |   2  
  Sitemaps         |   1  
  Cleaned          |   0  

Total in 123 ms

but looking in /tmp/www I see a lot less than 217 files:

$ tree /tmp/www
/tmp/www
├── categories
│   ├── index.html
│   └── index.xml
├── css
│   └── codingdojo.css
├── greetings
│   └── index.html
├── home
│   └── index.html
├── index.html
├── index.xml
├── sitemap.xml
└── tags
    ├── index.html
    └── index.xml

5 directories, 10 files

3. Using Docker

Assuming that something is wrong with my hugo installation, I install a modern Docker (I haven't used it for two years) and run it. After many iterations, changing config.toml and nginx_vhost.conf a bit, I have something I can use:

diff --git i/config.toml w/config.toml
index 2262eb9..7f95455 100644
--- i/config.toml
+++ w/config.toml
@@ -3,5 +3,5 @@ baseurl = "http://codingdojo.org/"
 title = "Coding Dojo"
 theme = "template-hugo-codingdojo"
 metadataformat = "yaml"
-canonifyurls = true
+canonifyurls = false
 disablePathToLower = true
diff --git i/nginx_vhost.conf w/nginx_vhost.conf
index 6fb91bb..172c73b 100644
--- i/nginx_vhost.conf
+++ w/nginx_vhost.conf
@@ -1,7 +1,8 @@
 server {
   root /var/www;
   index index.html index.htm;
-  server_name localhost codingdojo.org www.codingdojo.org;
+  listen 1080;
+  server_name local.codingdojo.org localhost codingdojo.org www.codingdojo.org;
 
   if (!-f $request_filename) {
     rewrite ^/cgi-bin/index.pl /$args? permanent;

Building and running the VM:

$ docker build .
Sending build context to Docker daemon   2.16MB
[...]
Step 5/6 : run cd /site && /usr/bin/hugo --destination=/var/www
 ---> Running in 038871fcdd6e
Started building sites ...
Built site for language en:
0 draft content
0 future content
0 expired content
211 regular pages created
16 other pages created
0 non-page files copied
0 paginator pages created
0 tags created
0 categories created
total in 674 ms
Removing intermediate container 038871fcdd6e
 ---> 6b2adb5460e3
Step 6/6 : add nginx_vhost.conf /etc/nginx/conf.d/codingdojo.conf
 ---> 9b83de072f94
Successfully built 9b83de072f94

$ docker run  -p 1080:1080 -rm -d 9b83de072f94
...

After adding 127.0.0.1 local.codingdojo.org to /etc/hosts I can see all the content at port 1080. Yay!

Findings

I think the problem is that hugo has moved on in an incompatible manner. The container runs version 0.26:

# hugo version
Hugo Static Site Generator v0.26 linux/amd64 BuildDate: 2017-11-13T18:45:19Z

but homebrew installed 0.34 on my Mac. The Hugo docs talk about putting all content in folders, but that's not how this repo is laid out.

Again, I'm sorry to use this as a support forum, and I'll be happy to use any knowledge gained to improve the README or start building the wiki.

Ideas

Option 1: I'm thinking of picking up some Docker skills and create another VM that will run hugo server -w rather than using nginx. Hopefully I can do it without touching any of the existing files.
Option 2: Migrating the repo to current Hugo standards (if that is indeed what's wrong). It might mean losing the wiki-like naming/structure (but of course there have to be aliases to maintain all old links).

Has anyone tried this? Does anyone have preferences? And who calls the shots?

Hello,

Do you think it would be possible to have a version of codingdojo.org translated into pt_BR?

My ideia, if ok for you, would be having original in http://codingdojo.org and pt_BR version in http://br.codingdojo.org or http://codingdojo.org/pt-br .

As an example, we just did that in https://phptestfest.org/ and https://phptestfest.org/pt-br (https://github.com/phpcommunity/phptestfest.org/tree/master/docs).

Best

Ça fait plusieurs fois que j'ai des soucis à comprendre l'énoncé du kata Anagram http://codingdojo.org/kata/Anagram/

Je ne sais pas si c'est mon niveau d'anglais qui est un peu naze ou si c'est que ça manque d'exemple.

we need to see somewhere the title of the page we are viewing

Hi, it looks like the website is down, what's happening?

Cool URI don't change, but sometimes it's happen. Use 301 return code, and redirection.

Exemple :
http://www.codingdojo.org/cgi-bin/index.pl?KataRomanNumerals
->
http://codingdojo.org/kata/RomanNumerals/

Every title (and text) that is linked to something is still in Wiki style with all words in Pascal Case.

we should correct at least the titles that appear in the pages.

Sorry, can't understand your instructions at all. Please add our dojo (I just coped and pasted someone else's raw file):

title: "AustinSWCDojo"
draft: false
date: "2018-12-07T11:00:00"
aliases:

• "/AustinSWCDojo"

The Austin Software Craftsmanship Meetup holds a Coding 

Dojo once a quarter (next dojo Jan 2019). We use
[Cyber-Dojo] as a platform in order to support
multiple languages and test frameworks. Join us
on [Meetup] for more info.

Our dojo is run "Glasgow style," with pairs working together
on their own laptops, all on the same kata but not necessarily
all on the same language. Open to all experience levels;
if you're interested in improving your craft, we want you!

It would be nice to have codingdojo.org available via HTTPS. I don't know where the page is hosted, but having Nginx mentioned in the configuration files suggests that https://letsencrypt.org/ could be an option.

on content pages, we should have a breadcrumb on the top to know where we have and what type of content we are viewing

• Be more precise on the "how to start"
• Reorganize content

http://codingdojo.org/ is not responding.

• http://www.isitdownrightnow.com/codingdojo.org.html
• http://downforeveryoneorjustme.com/http://codingdojo.org/