tmattio/opium-demo
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
Demo of a fullstack application with Opium
1 commit 1 branch 0 tags 53 KiB
  • OCaml 89.7%
  • PLpgSQL 5.7%
  • Makefile 2.9%
  • Dune 1.7%
Find a file
Exact
Thibaut Mattio 8894746eb0 Initial commit
2020-06-02 14:18:32 +02:00
.github/workflows Initial commit 2020-06-02 14:18:32 +02:00
asset Initial commit 2020-06-02 14:18:32 +02:00
bin Initial commit 2020-06-02 14:18:32 +02:00
lib Initial commit 2020-06-02 14:18:32 +02:00
migration Initial commit 2020-06-02 14:18:32 +02:00
test Initial commit 2020-06-02 14:18:32 +02:00
.gitattributes Initial commit 2020-06-02 14:18:32 +02:00
.gitignore Initial commit 2020-06-02 14:18:32 +02:00
.ocamlformat Initial commit 2020-06-02 14:18:32 +02:00
CONTRIBUTING.md Initial commit 2020-06-02 14:18:32 +02:00
dune Initial commit 2020-06-02 14:18:32 +02:00
dune-project Initial commit 2020-06-02 14:18:32 +02:00
Makefile Initial commit 2020-06-02 14:18:32 +02:00
opium-demo.opam Initial commit 2020-06-02 14:18:32 +02:00
README.md Initial commit 2020-06-02 14:18:32 +02:00

README.md

Opium Demo

Actions Status

Demo of a fullstack application with Opium.

It is heavily inspired by Phoenix's project structure and phx_gen_auth generator.

The project structure, tests, and even comments, are taken directly from the links above, so no credit taken. All I did was providing an OCaml implementation using Opium.

The goal is to open a discussion on the following:

  • What is the best project structure for an Opium application?
  • Is there any opportunity to abstract complexity in a fullstack application in order to increase developer productivity?

API

The server serves the following endpoints.

GET /

Returns the string Hello World.

$ curl http://35.224.1.215/
Hello World

Contributing

Take a look at our Contributing Guide.