Fosspay — Donation collection for FOSS groups and individuals
-
Very interesting - didn't know this sort of thing existed but I can see the value and it getting used by many here.
Adding to my Wishlist:
-
Anyone up for packaging this with some sponsoring? Can pay you via your own instance for the first test!
-
-
I can give it a shot.
@atrilahiji Cool!! Will DM
-
https://git.cloudron.io/AtriLahiji/fosspay-app
Started here. Confusing AF so far but I'll see what I can do.
-
https://git.cloudron.io/AtriLahiji/fosspay-app
Started here. Confusing AF so far but I'll see what I can do.
@atrilahiji Since it's a Python app - Just expose the apps port to Cloudron and tell cloudron the HTTP port is the app port. Cloudron's built in reverse proxy, in theory, should take care of most of the rest. (App may still need the domain it's hosted on and so forth)
Looking at the code you have so far, I do not believe nginx is required to be built into the app - unless you need something specific from it?
-
@atrilahiji Since it's a Python app - Just expose the apps port to Cloudron and tell cloudron the HTTP port is the app port. Cloudron's built in reverse proxy, in theory, should take care of most of the rest. (App may still need the domain it's hosted on and so forth)
Looking at the code you have so far, I do not believe nginx is required to be built into the app - unless you need something specific from it?
@murgero I'm likely confusing myself working with the taiga app as an example of packaging a python app for Cloudron.
-
@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.
