1
0
mirror of https://github.com/jhillyerd/inbucket.git synced 2025-12-17 09:37:02 +00:00
Files
go-inbucket/ui
James Hillyerd 82ddf2141c Create V2 API for monitor+deletes, revert V1 API (#347)
* Revert socketv1 controller API to maintain V1 contract, introduce
V2 controller for Inbucket UI.

Signed-off-by: James Hillyerd <james@hillyerd.com>

* Introduce MessageID for deletes, instead of recycling header

Signed-off-by: James Hillyerd <james@hillyerd.com>

* Update UI for monitor V2 API

Signed-off-by: James Hillyerd <james@hillyerd.com>

---------

Signed-off-by: James Hillyerd <james@hillyerd.com>
2023-02-17 12:37:17 -08:00
..
2018-11-13 22:06:19 -08:00
2022-04-23 13:35:54 -07:00
2022-04-23 13:35:54 -07:00
2018-11-12 20:38:00 -08:00
2022-04-23 13:35:54 -07:00
2023-02-16 09:59:26 -08:00

Inbucket User Interface

This directory contains the source code for the Inbucket web user interface. It is written in Elm 0.19, a delightful language for reliable webapps.

Development

With $INBUCKET as the root of the git repository.

One time setup (assuming Node.js is already installed):

cd $INBUCKET/ui
yarn install
yarn build

This will the create node_modules, elm-stuff, and dist directories.

Terminal 1: inbucket daemon

cd $INBUCKET
make
etc/dev-start.sh

Inbucket will start, with HTTP listening on port 9000. You may verify the web UI is functional if this is your first time building Inbucket, but your dev/test cycle should favor the development server below.

Terminal 2: parcel development server

cd $INBUCKET/ui
yarn start

yarn will start a development HTTP server listening on port 1234. You should use this server for UI development, as it features hot reload and the Elm debugger.