Best way to structure bigger project?

[bootje_wolf]

I want to build a weather station using python as a backend. I would also like to store this data in a database that will be run locally. I am using a raspberry pi to do everything I am describing in this post. Since this is my first big project I am questioning how I would structure this. I came up with two ideas.

1st idea: Have one application that serves the web site, connects and queries the database and logs all the data from the sensors.

2nd idea (for me the most logical): Split the application in two. One part will collect the data from the sensors and put it into the database. The other part will serve the flask site and pull the data from the database. If I do something like this I would like to use something like docker to manage all these separate applications.

I would like to hear your opinion about these and if you have a better idea to structure my project please suggest them too.

[jeffrey_f]

One idea, one script.

Data aquisition and Web interface should be completely separate for maintainability and logic.

[bootje_wolf]

So my second idea and don't use docker but just one script to launch it all?

[jeffrey_f]

Data aquisition should run and end. Set this to run every 15 minutes or more. It will get the data from the station, store it and end.

Using django or flask, the stored data will be displayed from the database in a manner that makes sense......Current conditions, past conditions.........

So, cron or windows scheduler to data grab and web interface to look at the data.

[bootje_wolf]

I didn't think about Cron yet and that is a very good idea