siegerts / drip Goto Github PK

The v1+ of plumber have numerous breaking changes that limit the current functionality of drip. Mainly, the application structure that utilizes and entrypoint.R file.

The run function needs to be refactored to account for the new ways of instantiating the API itself.

#2

I tried using drip in a container (see https://github.com/mskyttner/drip/blob/master/README-container.md) and have some questions/issues (which are hopefully possible to replicate using https://github.com/mskyttner/drip/blob/master/README-container.md#issues--questions).

The use case was to set up an container environment allowing live reload, by default using the plumber api example with an entrypoint that is bundled in the plumber R package.

I think I got it to run, but strangely the counter does not increment.

Any idea why?

The initial version does not currently parse for mounted routes and static file paths. https://www.rplumber.io/docs/programmatic-usage.html#mount-static

Occasionally, using drip, saving a plumber file and triggering a reload in drip will fail with plumber reporting "execution halted", with drip still running ok.

It seems to be some port clash when this happens:

server_1  | Running plumber API at http://0.0.0.0:8000
server_1  | Running swagger Docs at http://127.0.0.1:8000/__docs__/
server_1  | createTcpServer: address already in use
server_1  | Error in initialize(...) : Failed to create server
server_1  | Calls: <Anonymous> ... <Anonymous> -> startServer -> <Anonymous> -> initialize
server_1  | Execution halted
server_1  | 
server_1  | 
server_1  | Execution halted

It seems to help just to resave the file a couple of times (with no changes to the content) and it will start to work again, at least that is what I see when testing this with this file

Any advice on how to either a) automatically trap such a state so that the dripping can continue or b) write an entrypoint.R file that doesn't trigger "address already in use"?