Eleutheria Pay - Open source donation platform

[marcusquinn]

@atrilahiji No worries, just my POV, noting the above Fast screenshot and similar with Stripe, Paypal and every other checkout form I've ever seen.

[A Former User]

@marcusquinn Something like this?

@murgero @jdaviescoates opinions?

[murgero]

@atrilahiji That looks really good.

[A Former User]

Thanks for the feedback guys. I pushed and deployed a new demo and I think I have the hand of hang of bootstrap breakpoints.

[murgero]

@atrilahiji Ya cert is borked

[A Former User]

@murgero Oh the new demo link is https://eleutheriapaydemo.atrilahiji.dev/

I cant update the OP anymore (dunno why) but its updated on the repo.

[jdaviescoates]

@atrilahiji said in Eleutheria Pay - Open source donation platform:

I cant update the OP anymore (dunno why) but its updated on the repo.

I think when @Staff updated this NodeBB a load of default settings got changed, including making it so we can now no longer edit old posts. I'd like that change to be changed back.

[marcusquinn]

@atrilahiji Thats nice

[marcusquinn]

For the radio-button styles, It might look better to invert, so blue text on white. We always try to make high-contract for visually-impaired accessibility.

[A Former User]

@marcusquinn Done (sort of).

[marcusquinn]

@atrilahiji Very nice! Some other tweaks:

• Perhaps add the Name & Email fields to your form so they are pre-populated when getting to the Stripe page.
• Currencies in alphabetical order.

Are you thinking to have an admin page for configuring the values & defaults? If so:

• Different amounts based on currency selection.
• "Donate" button text configurable (eg: "Subscribe", "Sponsor")
• Social sharing icons & links.

Coming together really nicely though, I can see why you wanted to make an alternative to Fosspay.

Maybe consider changing:

• "Elutheria Pay is a self-hosted FOSS payment system for FOSS developers" to
• "Elutheria Pay is a self-hosted, open-source and private payment system for projects, services and fundraising."

[jdaviescoates]

+1 to everything @marcusquinn said

[A Former User]

@marcusquinn I’ll look into these. So I was trying to make configuration as simple as possible while trying to not need a DB at all. So the things you want configured can be configured in the .end file. Same with the description, but I do agree that is better as a default.

I guess I’m wondering if you guys think it would benefit from using an admin page + db for config instead of a .env file for config

[marcusquinn]

@atrilahiji Same reason for every admin setting UI, broader reach.

[A Former User]

@marcusquinn fair enough. I certainly could try to add support for this

Put it on my board as the next item I will be working on. Using Mongo because I love collection/document style DBs.

[A Former User]

Boy oh boy is this a long process. I mean my previous approach was definitely quicker but this will hopefully be more robust. Building out my own login system. I've never implemented auth myself so this will be fun.

I'll definitely need some help testing it once I get the next release out.

[A Former User]

Update again:

I have login working. I might ask others who are more experienced with writing auth to audit it if that’s ok. I also have a site up now but was too cheap to get my own domain for it so here it is: https://eleutheriapay.atrilahiji.dev/

Please let me know via dm or a reply to this post if you want to try out the new version when it’s ready and maybe even audit the code. I would be really grateful.

[marcusquinn]

@atrilahiji Nicely done!

You made me search for "free domains" and these look interesting:

• http://www.dot.tk
• http://www.freenom.com

[A Former User]

Another update:

I have pushed a seemingly working login system to my dev branch here if anyone is feeling adventurous enough to pull it and test it out:
https://git.lahijiapps.dev/atrilahiji/eleutheriapay/-/tree/dev

I am working on a few features to play off of this here:

But as of now login and config updates now work and it makes use of MongoDB.

I'm really having fun with this one. If anyone has some more ideas (keep in mind im just going to have to queue them because this does take time) definitely let me know. And if anyone wants to contribute also let me know and I can set you up.

[jdaviescoates]

@atrilahiji just out of interest, what board are you using there?

[marcusquinn]

@jdaviescoates Looks like GitLab Issues Boards to me.

[jdaviescoates]

@marcusquinn you are correct

[marcusquinn]

@jdaviescoates I live in GitLab issues for work

[A Former User]

Reviving this as I have come back to the project after losing motivation for a bit. I really did just want to keep this as a simple donation page that can be easily customized for those who don't want to build out their own. With that in mind, I removed monthly and annual payments from my current version. I still have a branch working on auth and a more complex system but I'll be thinking about how to best move forward with that in the future.

@staff I have a few changes I would like to make still before I have an initial version but I think it would be cool to have this app on the store if you think it makes sense. Of course, it is up to you guys

EDIT: To further explain, I got carried away in suggestions and making them all happen and forgot why I made it in the first place. Not that I don't appreciate feedback of course

[jdaviescoates]

@atrilahiji said in Eleutheria Pay - Open source donation platform:

With that in mind, I removed monthly and annual payments from my current version.

IMHO monthly payments (at least) are often a key feature people look for when creating a "simple donation page"

[A Former User]

@jdaviescoates Normally I'd agree, but my goal here is to keep it lightweight. No DB, no user tracking, nothing. That is something that impossible to do while having recurring payments as you need to provide a way for users to cancel. The idea is tips and not patreon, basically. A branded layer over-top of stripe that also serves its own donation button you can embed anywhere.

I've kind of resolved to doing the work I need to make it fit my needs (as that was my original intent) and allowing contributions and forks from others if there is a need for that. Basically I don't want to put energy into building something I don't ever want to use.

[jdaviescoates]

@atrilahiji fair enough scratch that itch

[girish]

@atrilahiji it's not different to any other project in my mind. If it's something you will continue to work on and is useful to others, I don't see any problem having an app for it in the store.

[A Former User]

@girish I have my 1.0.0-RC2 packaged and updated on the cloudron git with super basic tests. I'm going through testing things on my repo for EP and I'll hopefully have a full 1.0.0 release soon.

[A Former User]

This post is deleted!

[A Former User]

Pushed 1.0.0 finally. I think everything is good to go for a major release. Updated the package too.

[girish]

@atrilahiji w00t , congrats! BTW, did you have a landing page/home page for this? The one you linked earlier is not working anymore. Also, your git seems to have some cert errors it seems.

[A Former User]

@girish Ah lol so I moved some things over to another domain (using lahijiapps.dev for my new business) and switched to Gitea. The link is https://git.atrilahiji.dev/atrilahiji/EleutheriaPay

I had a landing page but wasn't happy with it so I was going to make a new one. Right now in the package im using the repo URL as the homepage.

[marcusquinn]

Great stuff!

Talking of the name, when I read it, I read "Uretha"

Depending on if you want to find a matching domains, naming is very personal, but here's some that sound OK to me:

• Atpay
• Button Pay
• Elpay
• Pay Button
• Paystar

I do like coming up with names - but, like I say, I'm sure very personal. I hereby give away all copyright and claims to any of those if you do like though, so feel free to screenshot and hold me to that

[A Former User]

@marcusquinn Cool, thanks for the suggestions! Yeah the name is the part I am most unsure about rn. And the logo is basic but honestly I care less about the logo and more about the name and usability.

Working at a v2 I want to clean some more things up, write a golang backend, and build it with my CI to make it extremely easy to deploy. JS is cool and all but something about having 3 package.json files floating around in a single project makes me want to puke in my mouth a bit.

[marcusquinn]

@atrilahiji Haha, Puke Pay?

[A Former User]

@marcusquinn An accurate name until I get node out of there. Ideally I want a pre-built frontend + backend executable. Keeping it simple. Right now I have scripts building the frontend and backend node bundles...

Don't get me wrong, Node has its place. But this just seems like too much lol

[girish]

@atrilahiji I really like the Go approach of single binary! There is also this module called rice which compiles assets in a go code which you can compile into your app. Very nice because the resulting single binary is very end user friendly.

[A Former User]

@girish oh wow I’ll check that out! For now it’s definitely node based but I can also just update the package then. Not like the backend is super complex anyways.

Idk you think it’s worth waiting?

[girish]

@atrilahiji As long as the config file is compatible between releases, I think it's fine. After all, end user doesn't care what language it's written in.

[A Former User]

@girish I don't plan on changing it anytime soon but just in-case I will put out a minor release with a .env merge script we can run from start.sh in the package. This is a good point, thanks for bringing that up. Better safe than sorry.

[A Former User]

Man golang is fun. Had some frustrations with module management. Maybe I should look at plain ol C or Rust for good ol downloading and relative linking of dependencies but otherwise golang is fun. That being said I found what you were talking about @girish and I’ve it all in one binary. Only thing now is I need to expose the CSS config in the .env file. Makes it easier so releases are just a .env and an executable. Simple and elegant.

[robi]

@atrilahiji yeah, I always use GVM to manage diff go versions and modules.

[A Former User]

@robi Oh wow thanks!

That helps quite a bit! I find the whole central location for modules frustrating. I guess I'm used to just dropping a library or some code I wrote into the same directory as my main app and linking to it via its relative path.

I don't want to change langs again but now part of me is curious about just writing a C server lol. A fun challenge but not for this particular project

[A Former User]

[A Former User]

@atrilahiji Finished EL for now (as in I believe it is ready for use). And the package merges the configs. Its a single .env and binary now

Thanks for that suggestion @girish !

[girish]

@atrilahiji Oh wow, you ended up rewriting it in Go? That was pretty quick, I must say. Where is the Cloudron package btw? Or is that not done yet?

[A Former User]

@girish one quick update before I think it’s ready (had to re-enable asset customization)

Yeah thankfully the backend for EleutheriaPay is very simple so rewriting it in go was pretty quick. I did have to pull out an assets folder from the executable so it can be customized. But it still means the frontend build is already done when it is downloaded.

I’ll link it here in a moment

[girish]

@atrilahiji if it can be a separate repo like other app packages, that will be great! You can put it in git.cloudron.io

[A Former User]

@girish Its been over here: https://git.cloudron.io/AtriLahiji/eleutheriapay-app

I just updated it and fixed asset linking. Should be ready now. I've lost count of the number of times I've said it should be ready but my ADD brain does seem to miss things I need to fix. This time for real though.

[privsec]

I am really interested in this, I’ll be looking this over to see if I can help develop it.

[A Former User]

@privsec Develop it? I mean I am open to contributions if thats what you mean.

[privsec]

@atrilahiji yes, sorry.

Contribute to it in any way. I love the idea of this.

[A Former User]

@privsec Ah I see. Yeah its on my self hosted gitea but I can always make accounts for those who want to contribute or try to merge in contributions with credit from forks on GitHub or something. I haven't figured out the whole contribution model for self hosted yet. This is why we need activitypub gitea

I'm glad you like it!

[A Former User]

haHAHAHAHA one more fix in. Had the wrong mime type for the Badge endpoint so it wasn't showing up when embedded. I got mad that it was just that so I re-tagged 1.1.4.

My instance using the new package. I need to make sure the assets update correctly so I'll push that to the package soon.

[A Former User]

@girish Done.

[A Former User]

I've pushed a new update. Version 1.1.5 of EL. The package should be ready as well. Let me know if you have any questions about it @girish and a reminder that if you want it, "smash that upvote button" on my original post.

[A Former User]

Is there a possibility of this being on the store? I have a few things I want to add in the near future but nothing should be breaking. It should be stable and good to go now

Guess I should probably tag @girish here eh?
Also bump!

[girish]

@atrilahiji It's on my list, haven't forgotten this This week was supposed to be our "app month" but it has instead turned out into a "6.2 month"! We have ended up with 7 patch releases now but atleast we are finally done. The roll out will take the rest of this week, so we will get on track to focusing on getting the most voted apps and already packaged ones out.

[A Former User]

FYI I’m working on integration with Owncast

The developer of Owncast reached out via an issue on my repo suggesting this and I’m exploring possibilities now.