New Issue

Documentation improvements #2

Closed

opened by dfeyer · 6 comments

dfeyer commented (Migrated from github.com)

Review the docker-compose setup
Plume require HTTPS connection (see https://github.com/Plume-org/Plume/issues/412)

- [ ] Review the docker-compose setup - [ ] Plume require HTTPS connection (see https://github.com/Plume-org/Plume/issues/412)

👍 1

trinity-1686a commented

Owner

I think instead of providing an half working http (no s) option, we should link to/write something about how to setup a local CA to test things

👍 1

igalic commented (Migrated from github.com)

that is a terrifying thought 😰

elegaanz commented (Migrated from github.com)

(I move this issue to the dedicated repo)

👍 1

DeadSuperHero commented (Migrated from github.com)

Any progress on this? This issue prevents me from actually using Plume for local testing purposes.

elegaanz commented (Migrated from github.com)

I didn't reviewed the docker-compose files, but I updated the development guide with instructions for HTTPS.

I didn't reviewed the docker-compose files, but I updated [the development guide with instructions for HTTPS](https://docs.joinplu.me/development/).

elegaanz commented (Migrated from github.com)

I think the docker-compose files are now OK with the latest commit.

No Label

No Milestone

No Assignees

2 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.

Loading…

There is no content yet.

Labels Milestones