Aulig
Senior Member
- Jun 15, 2018
- 870
- 545
Thanks a lot for your reply!
A few hours later and I'm pretty fair: I got PyCharm, a project library, an app.py and a template (though some problems as I'm not able to properly integrate it with Flask; but I think that's too programming-specific for a journey thread and we don't want to make the mods mad - so I'll either DM you or lurk around to find a solution to my problem).
Either way, to come back to the Snapchat SaaS example I made: Hypothetically speaking, someone wants to make this SaaS and wants to use any GitHub with a Python API (e.g. https://github.com/mpolden/pysnap) - he builds his app.py and maybe functions.py or whatever his files are called. app.py calls the methods / functions from functions.py and integrates those functionality with the front-end (I could code "bare Python" in functions.py and Python/Flask in the app.py) returning values / output or getting input, right?
To extend my question to SQLite: Do you only store user/mailass in the DB or also, e.g. Snapchat API related stuff or shall someone make a different DB for all the API related data received?
Yea you just code in python to call the api
I only store user and purchase data in the db, for that SQLite is enough for sure. Depending on how much stuff you're storing it might be worth it to pick a bigger or more specialized database that suits your case, Im no expert at that though. I'd suggest you just use whatever is simplest at first and optimize later if needed.
I usually just install dependencies via pip and then I can easily access them, or whats the problem with the integration? Also make sure the github project is still working, as its 3 years old and not maintained