Swagger UI as a separate microservice #2

New Issue

blek · 2023-10-22T05:40:16+02:00

blek commented

2023-10-22 05:40:16 +02:00

I think that adding swaggerUI would be great in terms of reading the docs.

It probably can be deployed to production like this:

Build the HTMLs in the node:20 docker tag
Copy the built files into a static server (apache?idk)
Maybe somehow manage to put those files in the caddy filesystem

I think that adding swaggerUI would be great in terms of reading the docs. It probably can be deployed to production like this: 1. Build the HTMLs in the `node:20` docker tag 2. Copy the built files into a static server (apache?idk) 3. Maybe somehow manage to put those files in the `caddy` filesystem

blek commented

2023-10-22 05:41:50 +02:00

Development deploy is similar to production

Build docs continuously in node:20 using something like gulp's file watch
Mount the build directory to somewhere in caddy filesystem, with no need to deploy a server inside NodeJS

Development deploy is similar to production 1. Build docs continuously in `node:20` using something like `gulp`'s file watch 2. Mount the build directory to somewhere in `caddy` filesystem, with no need to deploy a server inside NodeJS

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blek/bfile#2