todobackend / todo-backend-site Goto Github PK

View Code? Open in Web Editor NEW

105.0 7.0 129.0 2.22 MB

source for the TodoBackend website

Home Page: http://www.todobackend.com

Ruby 15.96% HTML 36.54% JavaScript 0.69% CoffeeScript 8.60% CSS 25.88% Shell 10.34% Dockerfile 1.98%

todo-backend-site's Introduction

todo-backend-site

Source for www.todobackend.com. This is a middleman-based static website.

built and deployed to S3 via:

Adding a new implementation listing

To add a new Todo-Backend implementation:

edit data/implementations.yaml
add any new tags to data/impl_tags.yaml
and add logos to source/images/logos.

Running a local instance of the site from source

Make sure you have git submodules set up with git submodule update --init --recursive
Install required gems with bundle install
build the site with bundle exec rake build
run a dev server with bundle exec middleman

Running the site via docker

A dockerized version of the site is available on Docker Hub as moredip/todo-backend-site.

Make sure you have git submodules set up with git submodule update --init --recursive

You can run the site within a container while still incorporating local changes:

docker run -p 4567:4567 -v "${PWD}/data:/opt/docker/data" -v "${PWD}/source:/opt/docker/source" moredip/todo-backend-site build serve

If you prefer Docker Compose there's a docker-compose.yml in the root of the source repo, so you can just do:

docker-compose run --service-ports site

and you'll have the site running on port 80 of your Docker host.

todo-backend-site's People

Contributors

Stargazers

Watchers

Forkers

panesofglass kylehodgson joncanning mforman pamo ademar brianstorti kjellkvinge moredip akiellor raboof hythloday jeffweiss jhedev ryanoglesby08 faerbit liamsi whitfieldc shyba capesepias deepredsky tuupola ilya-murzinov daviddenton alexsomai sczyh30 corona10 rfdickerson vithulan jrglee moltar electrotype stevenjob mattinsler aesteve sarbogast jsphyin chiahuang tomwadeson loganwright jesspittman elnaz kixpanganiban darrenhaken selvakn jknack lutsen markheath andreas-schilling greenlaw110 manuelmorales meier-christoph ismagilov tetsu81vn jkingoliver jef-sure gregoirew j-1000 ricsirigu kputh christianalexander sdqali duelinmarkers wendal maxtoroq oblac vladaspasic mabe olberger iamquang95 akrabat adelarsq codifryed xurei arayb nickfun gopinath-langote kentaro0919 mschuwalow mcking2nd yemm saylerb matthewrankin matiangul dennishartrampf johannea sbortz edavidaja itsuki-hayashi tonycheang johanvogelzang sharmavishalvk torrespro bmuskalla mauriciolobo mgroves ormanli gen-failure stimata-debug prestancedesign

todo-backend-site's Issues

implementation using Haskell/Yesod

Deployment fails

Hi,

Just to prevent that the website is not up to date.

The recent implementations that have been recently merged are not present.
The deployment is stuck since the build 23703a8 which dates from February.

Best regards.

implementation using node/restify

https://github.com/restify/node-restify

implementation using Erlang/Cowboy

http://ninenines.eu/

Implementation using OpenResty

Would be really interesting to see an OpenResty implementation

Add dead/bad link detection to CD pipeline

Every now and then we get a PR which has bad URLs. Would be great to detect that in our PR trial builds.

Perhaps we can leverage something like:

Implementation using jooby

See http://jooby.org

(I will provide the implementation)

Implementation using node.js/micro

https://github.com/zeit/micro

Implementation using vert.x

Would love to see a Vert.x implementation.

implementation using Elixir/Phoenix

http://www.phoenixframework.org/

Broken links for f# Freya, WebApi, Frank

The server http://todo-backend-fsharp.azurewebsites.net/ seems to be missing.

implementation using Laravel/PHP

Fix mixed content issues by updating API urls to `https://` or `//`

via email:

Hello Pete
Thank you for the todobackend.com project
Just one issue. With https:// emerging as the default protocol in browsers, all http:// XHRs become "mixed content", so none of the listed apis can pass the test unless you manually switch from https to http in address bar.
You may consider updating listed apis urls to https:// or to //
Thank you

implementation using Spark/Java

http://sparkjava.com/

For someone new to this it is very hard to get how the API should behave by only looking at the tests.
I found it difficult to deduce what should happen if you issue a DELETE request to the API root.
I am still unsure how the order property should be handled. Is it completely optional?

Failed tests also do not give helpful information if you do not know how the API should behave.

Implementation using Jodd

http://jodd.org/

Implementation using Racket

https://racket-lang.org/

Your connection is not private

Both Firefox & Chome complain and block the website access due to some SSL issues.

Deployment fails

Hi,

A few weeks ago you merged my PR (#178) for a Todo Backend implementation -- thank you for that!

However, it still hasn't appeared on the website. Possibly because the Codeship build is failing. Unfortunately I'm not able to log in there to see what's going on, so I can't provide further details.

Thought I'd let you know just in case you missed it.

Error: global leak detected: __VUE_DEVTOOLS_TOAST__
    at Runner.checkGlobals (https://www.todobackend.com/specs/js/lib/mocha.js:4534:21)
    at Runner.<anonymous> (https://www.todobackend.com/specs/js/lib/mocha.js:4408:44)
    at Runner.EventEmitter.emit (https://www.todobackend.com/specs/js/lib/mocha.js:588:20)
    at https://www.todobackend.com/specs/js/lib/mocha.js:4817:14
    at done (https://www.todobackend.com/specs/js/lib/mocha.js:4300:5)
    at https://www.todobackend.com/specs/js/lib/mocha.js:4341:31
    at _fulfilled (https://www.todobackend.com/specs/js/lib/q.js:787:54)
    at https://www.todobackend.com/specs/js/lib/q.js:816:30
    at Promise.promise.promiseDispatch (https://www.todobackend.com/specs/js/lib/q.js:749:13)
    at https://www.todobackend.com/specs/js/lib/q.js:557:44