Eleutheria Pay - Open source donation platform

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