Fosspay — Donation collection for FOSS groups and individuals
-
@atrilahiji said in Fosspay — Donation collection for FOSS groups and individuals:
Oct 13 16:46:16 from fosspay.app import app
Maybe the directory should be fosspay.app instead of fosspay ?
This post is deleted! -
Apparently not so easy to package. Just dropping a link here to Ko-Fi recommended by @atrilahiji and some alternatives that need research:
https://alternativeto.net/software/ko-fi/?license=opensource
Web Design https://www.evergreen.je
Development https://brandlight.org
Life https://marcusquinn.com -
Apparently not so easy to package. Just dropping a link here to Ko-Fi recommended by @atrilahiji and some alternatives that need research:
https://alternativeto.net/software/ko-fi/?license=opensource
@marcusquinn said in Fosspay — Donation collection for FOSS groups and individuals:
Apparently not so easy to package.
No? What can be done to advance the process?
-
@marcusquinn said in Fosspay — Donation collection for FOSS groups and individuals:
Apparently not so easy to package.
No? What can be done to advance the process?
@yusf Not sure @atrilahiji is researching it - but sometimes you get a sense of an app, and if it doesn't appear to be well coded then its best to rethink before getting to embedded.
-
Apparently not so easy to package. Just dropping a link here to Ko-Fi recommended by @atrilahiji and some alternatives that need research:
https://alternativeto.net/software/ko-fi/?license=opensource
-
@murgero woop woop
-
Pushed a new change. Now to figure out why im getting this error:
File "/app/code/fosspay/app.py", line 2, in <module>
Oct 13 16:46:16 from fosspay.app import app@atrilahiji said in Fosspay — Donation collection for FOSS groups and individuals:
File "/app/code/fosspay/app.py", line 2, in <module>
Oct 13 16:46:16 from fosspay.app import appI ended up removing alot of the work you put into build.sh and start.sh - on this error specifically, you were in /app/code/fosspay/fosspay which is the wrong app.py weirdly enough. There were also a lot of missing deps in requirements.txt (not your own fault, this is an upstream issue).
I have working code, so if @girish doesn't mind - I'll post my repo to gitlab and we will package that instead.
-
@atrilahiji said in Fosspay — Donation collection for FOSS groups and individuals:
File "/app/code/fosspay/app.py", line 2, in <module>
Oct 13 16:46:16 from fosspay.app import appI ended up removing alot of the work you put into build.sh and start.sh - on this error specifically, you were in /app/code/fosspay/fosspay which is the wrong app.py weirdly enough. There were also a lot of missing deps in requirements.txt (not your own fault, this is an upstream issue).
I have working code, so if @girish doesn't mind - I'll post my repo to gitlab and we will package that instead.
@murgero Ah. I thought I was in the correct one but I guess not. And yeah I noticed they had some dependency errors so I forked the project to add them back in. Thanks for looking at it. I gave it a couple of days and pretty much dropped it in frustration
Another issue I have with it is there are no tags in the source repo (and they seem to use sourcehut?) so it just pulls from master every deploy. Ideally we would have releases we can evaluate and update to. I's say either someone forks it and puts together releases or we live on the edge and have an always unstable app that pulls new code every time someone installs it.
Also also, I don't see the point in using an account (and therefore a db) to manage things in this app when the most important config is stored in a config file anyways. This app is just one big head scratcher.
-
@murgero Ah. I thought I was in the correct one but I guess not. And yeah I noticed they had some dependency errors so I forked the project to add them back in. Thanks for looking at it. I gave it a couple of days and pretty much dropped it in frustration
Another issue I have with it is there are no tags in the source repo (and they seem to use sourcehut?) so it just pulls from master every deploy. Ideally we would have releases we can evaluate and update to. I's say either someone forks it and puts together releases or we live on the edge and have an always unstable app that pulls new code every time someone installs it.
Also also, I don't see the point in using an account (and therefore a db) to manage things in this app when the most important config is stored in a config file anyways. This app is just one big head scratcher.
@atrilahiji said in Fosspay — Donation collection for FOSS groups and individuals:
so it just pulls from master every deploy
It only pulls the source when it's being built, at least that's how I have it setup. It will not pull on each install.
-
@atrilahiji said in Fosspay — Donation collection for FOSS groups and individuals:
so it just pulls from master every deploy
It only pulls the source when it's being built, at least that's how I have it setup. It will not pull on each install.
-
@murgero Oh right. I guess what I mean is when it is being released, its frustratingly difficult to keep track of releases. I guess at least stores on the cloudron store are pre-built.
-
@atrilahiji In this case I would track the date the last commit was Example Version Number that can be used here is:
e6ba79c8 - 2020-04-22That is<commit_hash> - <commit_date>@murgero True. Not that is isn't possible. Just more frustrating than specific versions. But because the Cloudron app store has pre-built images we at least dont need to worry about a broken version getting pushed to users.
-
Thanks for looking into this. I basically rage quit this one and went off into a corner to write my own Nuxt.js based version so I'm glad you swooped in.
@atrilahiji said in Fosspay — Donation collection for FOSS groups and individuals:
write my own Nuxt.js based version
You did what?! 🤩
-
If you could continue to make one in NodeJS that would be fantastic! We need more than just the one option for sure.
-
@yusf I tried it but was incredibly confused with the admin user and managing things. I didn't give it that much time though. It doesn't fit me needs in any case.
I'll ping @murgero as he worked on it last.
Technically my Node one works, but its very basic right now. It requires making fixed donation amounts on Stripe and tying those to the front-end. It also makes use of Stripe's checkout redirect system so I don't have to worry about that.
The repo is here if you want to see it: https://git.lahijiapps.dev/atrilahiji/eleutheriapay
And when I say its basic I do really mean BASIC lol
