Skip to content

improve README structure and installation instructions#6988

Open
yharroch wants to merge 8 commits intoLibreSign:mainfrom
yharroch:yharroch-patch-1
Open

improve README structure and installation instructions#6988
yharroch wants to merge 8 commits intoLibreSign:mainfrom
yharroch:yharroch-patch-1

Conversation

@yharroch
Copy link

  • Add Quick Links and improve section structure
  • Document occ libresign:install and libresign:configure:* usage
  • Clarify standalone dependencies in appdata directory
  • Improve license and security references

- Add Quick Links and improve section structure
- Document occ libresign:install and libresign:configure:* usage
- Clarify standalone dependencies in appdata directory
- Improve license and security references

Signed-off-by: yharroch <82467465+yharroch@users.noreply.github.com>
@github-project-automation github-project-automation bot moved this to 0. Needs triage in Roadmap Feb 21, 2026
Copy link
Member

@vitormattos vitormattos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great! The README needed some love. Thanks for taking the initiative.

I feel that some parts read more like full documentation than a README, and a bit too detailed for this level. Maybe we can keep it more focused on what LibreSign is and its core principles, and move deeper explanations to the documentation repository.

I’ve added a few suggestions in the PR to start the review and show the direction I’m thinking about. Happy to iterate together.

Comment on lines +176 to 183
## Screenshots

<p align="center">
<img src="img/LibreSign.png" alt="LibreSign interface screenshot" width="900"/>
</p>

---

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-project-automation github-project-automation bot moved this from 0. Needs triage to 1. to do in Roadmap Feb 21, 2026
@yharroch
Copy link
Author

Thanks for your feedback. I’m happy to help and iterate further.
Please don’t hesitate to be direct — I’m new to GitHub, and I don’t mind if some of my suggestions don’t fit.
I tried to include as much information as possible, even if some of it ends up being moved to another section or discarded.

Co-authored-by: Vitor Mattos <vitor@php.rio>
Signed-off-by: yharroch <82467465+yharroch@users.noreply.github.com>
@vitormattos
Copy link
Member

@yharroch, you can ask about any doubts in the comments regarding what I discussed that you didn’t understand.

yharroch and others added 6 commits February 26, 2026 14:18
deletion of useless technical information

Co-authored-by: Vitor Mattos <vitor@php.rio>
Signed-off-by: yharroch <82467465+yharroch@users.noreply.github.com>
update link's title for contribution

Co-authored-by: Vitor Mattos <vitor@php.rio>
Signed-off-by: yharroch <82467465+yharroch@users.noreply.github.com>
Deletion of useless license's section

Co-authored-by: Vitor Mattos <vitor@php.rio>
Signed-off-by: yharroch <82467465+yharroch@users.noreply.github.com>
deletion of useless line

Co-authored-by: Vitor Mattos <vitor@php.rio>
Signed-off-by: yharroch <82467465+yharroch@users.noreply.github.com>
Adding application's descriptions about some features

Co-authored-by: Vitor Mattos <vitor@php.rio>
Signed-off-by: yharroch <82467465+yharroch@users.noreply.github.com>
fixing link

Co-authored-by: Vitor Mattos <vitor@php.rio>
Signed-off-by: yharroch <82467465+yharroch@users.noreply.github.com>
@yharroch
Copy link
Author

Hi @vitormattos
I tried to resolve and merge your suggestions but i'm stuck at what's next.
Do I commit again ?
Do I need to do something specific ?

I'll tried to work again on the documentation in the right repository during next weeks

@vitormattos
Copy link
Member

Hi, I will review again the newest version.

Copy link
Member

@vitormattos vitormattos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made some more comments after last changes. Could you join into a new turn and check again? What do you think about the direction that we are going now with last changes?

Comment on lines +46 to +50
- 🔧 Administrators (installation, configuration, certificates)
- 👥 Users (how to request and sign documents)
- 🧪 Developers (architecture and API)

👉 https://github.com/LibreSign/documentation
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The follow suggestion will reduce a bit more:

Suggested change
- 🔧 Administrators (installation, configuration, certificates)
- 👥 Users (how to request and sign documents)
- 🧪 Developers (architecture and API)
👉 https://github.com/LibreSign/documentation
- [🔧 Administrators](https://docs.libresign.coop/admin_manual/): installation, configuration, certificates
- [👥 Users](https://docs.libresign.coop/user_manual/): how to request and sign documents
- [🧪 Developers](https://docs.libresign.coop/developer_manual/): architecture, how to contribute and API

Comment on lines +60 to +90
### 1️⃣ Install dependencies
Run the following command as your web server user:
`occ libresign:install --java --pdftk --jsignpdf`

This will install:
- Java (standalone JRE)
- PDFtk
- JSignPdf

All binaries are installed inside the Nextcloud `data/appdata_*/libresign` directory.
No system-wide installation is required.

### 2️⃣ Verify installation
`sudo -u www-data php /path/to/nextcloud/occ libresign:configure:check`

This command verifies:
- Java availability
- PDFtk setup
- JSignPdf setup
- OpenSSL configuration
- Certificate environment

### 3️⃣ Configure root certificate
You can generate a certificate using OpenSSL or CFSSL.

Example using OpenSSL:
`sudo -u www-data php /path/to/nextcloud/occ libresign:configure:openssl --cn="Your Organization - Digital Signature" --o="Your Organization" --c="FR" --st="Region" --l="City"`

Certificates are generated and stored inside the Nextcloud data directory: `nextcloud_data_dir/appdata_*/libresign`

No additional server-level configuration is required.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest to remove from here and move those steps to https://docs.libresign.coop/admin_manual/, too long to stay here at README. At the docs page would be good to split between automatic (using interface) and handmade setup (with commands).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 1. to do

Development

Successfully merging this pull request may close these issues.

2 participants