Eleutheria Pay - Open source donation platform
-
@atrilahiji fair enough
scratch that itch
-
This post is deleted!
-
Pushed 1.0.0 finally. I think everything is good to go for a major release. Updated the package too.
-
@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.
-
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
-
@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.
-
@atrilahiji Haha, Puke Pay?
-
@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
-
-
-
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.
-
@atrilahiji yeah, I always use GVM to manage diff go versions and modules.
-
@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
-
-
@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 !