Start by writing your requirements. The hard part: do NOT include any implementation details in the requirements. Focus on what, not how.
For example, "The database should be hosted on a website somewhere" is not a requirement. It is a way of achieving an unstated requirement; there may be other, even better, ways. Once you've written the requirements, you can look at how you could implement them. From what you've said so far, I'd be looking at a Flask app (or, if you'd prefer to spend nine months learning the platform, Django). But start with the requirements. -- Linux Tips: https://www.tiger-computing.co.uk/category/techtips/ -- Next meeting at *new* venue: Bournemouth, Tuesday, 2018-12-04 20:00 Check if you're replying to the list or the author Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk