masbicudo / letsencrypt-certificate-creator Goto Github PK

This button is important because it shows the base64 text of the certificate, that is used as input in GitLab pages configuration directly, instead of uploading a certificate file.

At this moment renewing is not yet supported. It is imperative that this be supported as soon as possible.

Create some documentation and tutorials for this application.
Maybe a video in YouTube too.

When the auto-button is pressed the action will retry 3 times automatically.
Maybe this behavior should be controlled by another button.
Also the action button could become pressed while waiting for retries, so that unpressing it would cancel the action.

The tool allows the user to automate the whole process of registering up to saving the final certificate file.

This can be extended with support to create many domains, many challenges and many certificates in a single automated operation.

This is even more desirable when creating certificates with multiple subdomains, or when renewing certificates in a row.

.Net has multiple ways to encrypt streams independent of the file system.

This has to do with the dependency project Acme-Sharp, that I have cloned.

Find a way, even if a change to that dependency is necessary.

If done in a reusable and standard way, also make a pull-request to the original repo... Let's encrypt, but also contribute!!! haha

Lets Encrypt support multiple subdomains per certificate.

The UI should allow the user to create a certificate using multiple domains that passed the challenge already.

There are at least two interesting components that can be split into other projects:

• ToolTipManager: used to show customized tool tips, it can show multiple tooltips for a single control at once, also tooltip windows negotiate their positions as not to overlap with themselves, and not to be off-screen or even orphaned in the middle of an overlapping window (e.g. windows from other applications)
• Bindables: value holders that use events to communicate changes. The interesting parts are the extensions to these objects, allowing binding with windows forms controls, binding with lambda expressions, and all sorts of custom bindings.

Each static site generator (SSG) has it's own rules on how to expose files through the generated site.

The application needs to detect the type of SSG being used,
and create or amend the configuration files so that it exposes
the '.well-known' directory required by the challenge.

All steps can be executed automatically when the auto-button is pressed.
The problem is that there are too many of them, so one single button should be able to check or uncheck them all at once.

While a commit is not committed, a new commit is not possible.
The UI should state this to the user, and start the retry counter, or wait until it can commit.

Also, if there are commits not yet pushed to the origin, there should be a visual indication, so that the user knows that all previous commits will be pushed.

If you press multiple action buttons, all of them will fire and start the corresponding action.
Pressing any button should cancel the current operation, if possible, and only then start the new operation requested by the user.