You're getting really good at these tutorials! Like a favorite college Professor. I replay these at 1.75x speed, making it like listening to a sports announcers broadcast of an exciting game. 🤓
1.75X, no way dude.. I can only do 1.5.. he is a pretty fast talker, even in presentation mode. How did you get to 1.75 with Brian's pace... I want to know.. I can't break that hard 1.5x. I've tried but I can't. Maybe if I drank some energy drinks or something.
This is a very cool alternative to DocuSign and Adobe Sign. Love the audit log feature as it's important information to show proof of delivery and signatures.
Thanks for this! I have a short term rental house and have started direct booking and have a rental agreement that I need them to sign. Didn't want to have to use a 3rd party ($) solution...this will be perfect! Nice detailed how-to!
Wonderful and thank you so much for sharing the video Mr. Brian McGonagill. I was hardly looking for this tool once again thank you for your timely help.
Good features, very interesting project. I understand they need to make money out of the project. I tried to add roles other than admin and when I saw the views they had empty files meaning there are things that were taken out from the project on purpose. Seems like a strategy to attract people to use it and ending up paying a subscription anyways. In conclusion they open sourced some parts of the project after the creation of the project and it is kind of difficult to add new features when there is no documentation and code holes. What is was interesting to me was that they used shakapacker and they have vue components that are reusables. If you are not a developer then it's something like this: If you don't care about other team mates looking at your signed documents or templates then it's a great tool everyone can see all the templates and signed documents. But if you have documents that other people shouldn't see then you will need to pay for a 20 doll a month for each user.
Strange. I just curled the yml file into my docuseal directory. It is different than yours. I didn't have the SLL line to hash out (I just added it) and I had this in it "- SECRET_KEY_BASE=mysecretkey" which is not in your curled .yml file. Also, mine calls for posgres:13. Yours is 15. In your Postgres environment, the names, passwords are "postgres." Mine are "docuseal." I'm just surprised since this video is dated Jult 4th 2024 and I pulled this .yml file on July 8th 2024. Also, the Caddy section was completely missing. The postgres volume was written like this: "postgres_data:/var/lib/postgresql/data". No relative ./ in the beginning. Not a big deal, I'm changing it to match yours. But as a new student of Docker Desktop....I wish I understood the nuanced differences as a learning opportunity.
That is strange. I just did all of this a week or so before releasing the video. They certainly could have changed things about the file though. You can look at their github repo, and see when the yaml file was last updated. Glad you're getting it all worked out. I like the relative paths in volume mappings, as it keeps everything in one place for a tidy backup as needed.
can i suggest to add some chapters to your videos? you spend quite a lot of time with setting up the container, that some of us are familiar with and are here to see what is actually the app about
I had to go look, I always add chapters to my videos. I see that when I exported the timestamps from my editing software I forgot to make some necessary changes, so they aren't showing up. Thanks for letting me know. I'll try to get it updated.
Great video! Do the signed documents get saved into the volume/postgres database? The reason I ask is because I would like to know how much memory I would need to take into consideration.
I believe they do. They are available after having created and signed them, but they may be getting stored on the drive, and just have a file path reference stored in the Postgres DB.
12:08 you should say the left side is local, right side is inside the container. Not saying that is like ubuntu's stackexchange. Don't be ubuntu's stackexchange, be the arch wiki instead.
This looks like a great alternative. Does this provide tha capabilities to use a smart card for signatures? Also, does this have routing functionality so that once the client signs it, it then routes to the next person so they can be notified and pending their signature. Thx
Soon as I hear Docker, I want click away too, as it is a technology almost exclusive to linux based-oses only. Though docker can be run on FreeBSD via the linuxator, any application that is docker only basically locks out other operating systems that are not linux-based. Docker does have benefits but it is locked in to the linux ecosystem...
I use Docker, and I understand, it's not for everyone my friend, but keep in mind this can be run without docker, and they have instructions on their Github site for running it.
On the topic of documents, do you know of something that could be self hosted that's similar to libreoffice? Not sure if onlyoffice is the one, certainly struggling to set it up.
collabora is Libreoffice on the browser, so maybe that's what you're looking for. A lot of people combine Collabora with NextCloud for syncing, and all, but it's not a requirement.
Follow up question Brian, I wonder if we can store the document and insert a QR code of the url where we stored it(random characters url). The idea is to provide third party with a fast way to validate authenticity of the document. Maybe we should pitch this to the project. Here is my thinking, schools really could use this, yes sure they can put a school seal on the document to prove authenticity, but in today's age, counterfeits are rampant, so with a project like this, teachers could prepare documents(transcript, recommendations, even diplomas) and then the admin staff, principal/secretary can sign and post/upload. SCHOOLS REALLY NEED THIS!!
The signature was small because of the size box I drew. I tried it just now on my testing server, and it was find in size. The idea about storing and QR code is definitely something to pitch to the project. I like it though. Very nice idea.
PDF via email or encrypted direct message has always worked for me. Never received anything I couldn't sign and never had any issues with anyone else signing anything I've sent. Curious to find out what this solution brings that would make it worth hosting. Payment is out of the question for the infrequent use case.
For me, it's about not having to tell someone they need Adobe Acrobat to sign, or some other software to get the signature on the document. It's also about making sure it's easy, and through a web page link, and guided tour, it's easy. Signing papers for a mortgage for instance, or legal matters, etc. Where there are a lot of initials and signatures required, this just makes it an easy walk-through for the person.
Hello - is there any way to use an external mysql database? I typically use an aws mysql database and would like to use aws mysql for this application. Thanks you
I'msure you can. In the compose file you need to setup the mysql connection from the appliction so it points to that AWS db, and comment out teh mysql section in the compose so that container isn't spun up.
@Awesome Open Source. I've checked the area that holds show notes. Usually i see a public email address to contact the specific creator. I wasn't able you find one. Did I miss it or would you happen to have a public email that you wouldn't mind providing? To be perfectly honest I would understand it if you didn't have one due to privacy. But I was really hoping to speak with you about a project if iscat all possible.
I configure mapped volumes, which map a volume on my host machine (a folder) to a folder inside the container virtual machine. This allows the data in that folder to be persisted when I bring down the container (essentially destroy it) and then bring up and updated version of it. Without these mapped volumes, Docker container data is considered volatile, and will be lost between reboots, restarts, up and down states, etc.
I looked at Docuseal as a replacement a while back but decided against it due to the cost. I don't mind paying for software, but with as little as I would use it with the features I'd want, a $20/mo subscription is a bit much. Perhaps $5-$10 would be more of a bargain. Or better yet, since it would be self-hosted, a one-time payout would be more of the way to go. To me, self-hosted should not be a subscription.
I see your point, and I would raise this thought. The software is subscription because it levels the old system of pay a huge amount up front, then some smaller amount every release or year or whatever for the updates, and then eventually get charged a whole new license for some major update 3 years down the road. It's no savings in the end to do subscription, but makes it predictable on cost. As to the actual cost of $20 / usr / month, you can always ask if they offer a few features in bundles that might allow you to pick 3 features a-la-carte for 5 or 10 a month instead.
The subscription model I usually go by for open source is pay for additional features, support and maintenance (upgrades and updates). I should be free to use the software for unlimited number of users and features when self-hosting as I'm already paying for the server and storage. The software should continue to run like normal when my subscription runs out. Just won't get the support, patches or updates for the additional features.
@@Darkk6969 I agree. But you can probably rest assured that they have a "call home" feature that checks to see if your subscription is paid up, if not, it would deactivate the features of the subscription model. This would be done to detour those who would otherwise pay a one-time $20 for all the features, and I would not blame them. And yes, as I said above, paying a subscription for something that is not on their servers is not something I nor anyone else should do, a one-time maybe $50 or $100 would suffice.
The sudo only applies to the curl command not the part after the bash redirection (what is after the >). In this case, your user does not have permission to write the compose file to your current directory
$20/user /month for a whitelable? What a joke. For small businesses or single entity contractors who want pro features, the value is, maybe, $50/yr cheaper with docuseal. My turning test, "do they arbitrarily gatekeep features already on your server behind scammy /usr/mo charges?" Answer: Yes. Examples: Unlimited signature requests Your company logo Connect own email address Personalize email content Automated reminders Zapier and Webhooks User roles and teams Bulk send from spreadsheet SSO / SAML API and Embedding Happy you did the video, but by far the worst value proposition compared to the other software you have featured, in my opinion.
I can't speak to the fee they ask for. I'm not part of the company. I know there are a couple of other comments that don't like the add-on feature for pay model. It' tough for me, because I know that in order to make something even remotely competitive, you have to have money coming in, and it's a hard line to draw to make sure you can invest your time and effort in such projects. That said, I didn't use any of the pay features, and it was perfectly usable to start off. Additionally, if you approach them with your thoughts on their pricing, and offer alternative revenue models, they may actually consider it.
Interesting, but unfortunately not GDPR-compliant and therefore unusable for Germany or the EU. I also think it's a shame that you don't have all the options available with self-hosting as in the paid version
Being that it's self-hosted, I'm sure you could recommend the addition of GDPR compliance features. Help them define what is needed, and even help test them and so on. As for their fee based model I'll post a quote from an earlier comment: "It' tough for me, because I know that in order to make something even remotely competitive, you have to have money coming in, and it's a hard line to draw to make sure you can invest your time and effort in such projects. That said, I didn't use any of the pay features, and it was perfectly usable to start off. Additionally, if you approach them with your thoughts on their pricing, and offer alternative revenue models, they may actually consider it. "
There is no GDPR compliance for software itself, it's what you do with that software. You can go delete a database entry just like you can not delete a database entry. Just because someone can't see it doesn't mean it was deleted either. Like all the big tech, none of them delete anything.
I watch a lot of your videos, and have implemented a few of your open source recommendations. However, I really wish you would exclude these "Pay for Use" software hidden behind an open source wrapper. Open Source is free and Open Source only, not software with hidden pay to use gotchas. There is no in between. I'd be more inclined to support software monetarily that didn't do these type things.
I understand what you're saying, but these folks should be able to generae revenue for the time an effort they put into making great software. the Free in Free software isn't free as in no-cost, that's the problem with English...it's misleading at times. The Free is for Freedom, as in the latin "libre". No one ever said that open source software shouldn't cost money. If I'm going to pay for software at tall, I'd prefer it be for an open source project. That said, I know it's frustrating, but you can also always go say thank you to them, and in the most polite way possible, ask if they'd consider a support model instead, or a tiered model for usage, or any number of other ways to monetize their work and effort. Price isn't always set in stone. If they get enough requests for changes, it may actually happen.
