Source code for the project Classe à 12. This has been bootstraped with elm-kitchen, see after the separator for more information. The project is bundled using create-elm-app.

To install and tinker (we use yarn because depency resolution seems to work better in our case):

$ git clone https://github.com/betagouv/ClasseA12
$ cd ClasseA12
$ yarn install
$ yarn start

Check out https://classe-a-12.beta.gouv.fr

The frontend static files are pushed to a git repository using gh-pages with yarn run deploy

For this second part to work, here's the recipe:

$ cd git
$ git clone --bare https://github.com/betagouv/ClasseA12.git
$ vim ClasseA12/hooks/post-receive

Content of the post-receive hook:

#!/bin/sh
while read oldrev newrev ref
do
    if [ "$ref" = "refs/heads/gh-pages" ];
    then
        echo "Deploying 'gh-pages' branch"
        git --work-tree=/path/to/www/ClasseA12 --git-dir=/path/to/git/ClasseA12.git checkout --force gh-pages
        exit 0
    fi
done

$ git remote add deploy-prod [email protected]:~/git/ClasseA12.git

Then, to deploy, run

$ yarn run deploy-prod

Additionnally you may add a different deploy remote, and use the yarn run deploy command, for example to deploy to a different staging server.

As a SPA, every URL needs to be managed by the index.html file (which has the javascript generated from the elm code). This can be done using a nodejs server like expressjs, or by using some apache configuration like the following in a virtual host:

DocumentRoot "/path/to/www/ClasseA12/"

<Directory /path/to/www/ClasseA12>
    Order allow,deny
    allow from all
    Options -Indexes -Includes -ExecCGI
    Options FollowSymlinks

    # This will make sure all the URLs that don't point to a file on disc will be processed by the
    # main entry point in index.html
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.html$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.html [L]
</Directory>

This is a modest attempt at providing a simplistic yet opinionated Elm SPA application skeleton based on rtfeldman's Elm Example SPA, for Allo-Media's own needs.

Check for yourself

• Elm 0.19 ready
• Multiple pages navigation & routing
• Live development server with hot reloading
• elm-test support
• elm-css support

The application stores Elm source code in the src directory:

$ tree --dirsfirst skeleton/src
src
├── Data
│   └── Session.elm
├── Page
│   ├── Home.elm
│   └── SecondPage.elm
├── Request
│   └── Github.elm
├── Views
│   ├── Page.elm
│   └── Theme.elm
├── Main.elm
└── Route.elm

Richard Feldman explains this organization in a dedicated blog post.

$ yarn install -g elm-kitchen
$ elm-kitchen my-app
$ cd my-app
$ yarn install

To start the development server:

$ yarn start

This will serve and recompile Elm code when source files change. Served application is available at localhost:3000.

$ yarn test

Tests are located in the tests folder and are powered by elm-test.

$ yarn run build

The resulting build is available in the build folder.

A convenient deploy command is provided to publish code on Github Pages.

$ yarn run deploy

MIT