Skip to content

This is a DocuSeal fork intended for security and privacy upgrades. Consider upstream DocuSeal first.

License

Notifications You must be signed in to change notification settings

meonkeys/docuseal

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

A DocuSeal Fork

This is a DocuSeal fork intended for security and privacy upgrades. Consider upstream DocuSeal first.

See:

There are a couple ways to show how this differs from upstream. Locally: first clone this repository, then add the upstream repository as an additional remote. Assuming they are called origin and upstream respectively, run git log -p --stat origin/master..master. At the time of writing I have added only two significant commits: remove github stars badge and remove link in email footer, with a total of 1 changed and 3 deleted lines of code. You can also visualize changes from upstream by clicking x commits ahead of on my fork's home page at GitHub.

My convention for releases is to create an a tag building on top of an official release. For example, 1.6.4 is theirs, and 1.6.4a is their 1.6.4 release plus my changes.

I'll keep an eye upstream and upgrade periodically, but I really hope this isn't a long-lived fork.

It might not be too much work to keep it going (it's such a tiny fork) but I want to be realistic. I'm not committing to support this like they are.

If you decide to use this and I miss an important change upstream (especially a security update), feel free to create a PR and I'll take a look. Probably the best approach would be for us all to thumbs-up docusealco#302 . They should understand that users don't want mandatory tracking (and if it somehow isn't acutally tracking, I guess they can clarify).

Related: I'd love to come up with a generic solution for controlling outbound traffic from containers. Looks like most people use iptables to do this? I see there's a DOCKER_USER chain built for customizations. I need to finally figure out iptables or find an easier way to do this.

https://docs.docker.com/network/packet-filtering-firewalls/

https://serverfault.com/questions/704643/steps-for-limiting-outside-connections-to-docker-container-with-iptables

Docker releases Follow @docusealco

DocuSeal is an open source platform that provides secure and efficient digital document signing and processing. Create PDF forms to have them filled and signed online on any device with an easy-to-use, mobile-optimized web tool.

Features

  • PDF form fields builder (WYSIWYG)
  • 12 field types available (Signature, Date, File, Checkbox etc.)
  • Multiple submitters per document
  • Automated emails via SMTP
  • Files storage on disk or AWS S3, Google Storage, Azure Cloud
  • Automatic PDF eSignature
  • PDF signature verification
  • Users management
  • Mobile-optimized
  • 6 UI languages with signing available in 13 languages
  • API and Webhooks for integrations
  • Easy to deploy in minutes

Pro Features

  • Company logo and white-label
  • User roles
  • Automated reminders
  • Invitation and identify verification via SMS
  • Conditional fields and formulas
  • Bulk send with CSV, XLSX spreadsheet import
  • SSO / SAML
  • Template creation with HTML API (Guide)
  • Template creation with PDF or DOCX and field tags API (Guide)
  • Embedded signing form (React, Vue, Angular or JavaScript)
  • Embedded document form builder (React, Vue, Angular or JavaScript)
  • Learn more

Deploy

Heroku Railway
Deploy on Heroku Deploy on Railway
DigitalOcean Render
Deploy on DigitalOcean Deploy to Render

Docker

docker run --name docuseal -p 3000:3000 -v.:/data docuseal/docuseal

By default DocuSeal docker container uses an SQLite database to store data and configurations. Alternatively, it is possible use PostgreSQL or MySQL databases by specifying the DATABASE_URL env variable.

Docker Compose

Download docker-compose.yml into your private server:

curl https://raw.githubusercontent.com/docusealco/docuseal/master/docker-compose.yml > docker-compose.yml

Run the app under a custom domain over https using docker compose (make sure your DNS points to the server to automatically issue ssl certs with Caddy):

sudo HOST=your-domain-name.com docker compose up

For Businesses

Integrate seamless document signing into your web or mobile apps with DocuSeal

At DocuSeal we have expertise and technologies to make documents creation, filling, signing and processing seamlessly integrated with your product. We specialize in working with various industries, including Banking, Healthcare, Transport, Real Estate, eCommerce, KYC, CRM, and other software products that require bulk document signing. By leveraging DocuSeal, we can assist in reducing the overall cost of developing and processing electronic documents while ensuring security and compliance with local electronic document laws.

Book a Meeting

License

Distributed under the AGPLv3 License. See LICENSE for more information. Unless otherwise noted, all files © 2023 DocuSeal LLC.

Tools

About

This is a DocuSeal fork intended for security and privacy upgrades. Consider upstream DocuSeal first.

Resources

License

Security policy

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Ruby 40.9%
  • HTML 24.9%
  • Vue 24.0%
  • JavaScript 9.8%
  • Dockerfile 0.2%
  • SCSS 0.2%