Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation improvements #2

Closed
2 tasks
dfeyer opened this issue Jan 7, 2019 · 6 comments
Closed
2 tasks

Documentation improvements #2

dfeyer opened this issue Jan 7, 2019 · 6 comments
Labels
enhancement New feature or request

Comments

@dfeyer
Copy link

dfeyer commented Jan 7, 2019

@trinity-1686a
Copy link
Contributor

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

@igalic
Copy link
Contributor

igalic commented Jan 7, 2019

that is a terrifying thought 😰

@elegaanz
Copy link
Member

elegaanz commented Jan 7, 2019

(I move this issue to the dedicated repo)

@elegaanz elegaanz transferred this issue from Plume-org/Plume Jan 7, 2019
@elegaanz elegaanz added the enhancement New feature or request label Jan 7, 2019
@DeadSuperHero
Copy link

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

@elegaanz
Copy link
Member

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

@elegaanz
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants