Eleutheria Pay - Open source donation platform

[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.