Django decision for tour reservation database

[Tourmaster]

I'm a tour operator scheduling 3 trips a day. Currently I manage my bookings by phone using MS Access and have a reservation service linked to my wordpress site who sends me reports by email. 

I want to put a single database on a server available to the office, outside agents and customers who will reserve a seat, select upgrades, agree to price and deposits and receive an email confirmation.

I've done Python programing before and just installed Django and SQLite on Yosemite for development of a simple stand alone web app duplicating the Access functions then linking to the website after migrating to MySql then dropping my online reservation service 

I'm looking for packages now if anyone can recommend a calendar based scheduler but I'm also reconsidering if Django is the the best framework since I'm not looking at complete site and may not need a full stack. 

Is this a job for a lighter framework?  Also, I may want to go mobile in the future. 

[Billu]

On Sunday, 13 December 2015 20:04:05 UTC+5:30, Tourmaster wrote:

I want to put a single database on a server available to the office, outside agents and customers who will reserve a seat, select upgrades, agree to price and deposits and receive an email confirmation.

Is this a job for a lighter framework?  Also, I may want to go mobile in the future. 

No, that's too much. Better use anything heavier. Even if you think it's light, you already have a wordpress site and you're expanding, think how much expansion you would do to this site in future.

Django is just fine for mobile. It's the templates you have to look after. You can serve pages depending upon user agent. 

SQLite is used because people generally don't have ready data and they don't know what table/columns they would have. Since you already know the table structure & have data (in Access), you might as well start development with MySQL, bugs will be found at the outset.

[graeme]

If in doubt use the full stack framework - you do not have to use features you do not want. On the other hand if you use a micro-framework and later decide you need the features of the full stack framework  you have to port your code.

I suggest using PostgreSQL instead of MySQL - it handles things like migrations better.

[Tyler Kelly]

I was very new to python and its frameworks a couple months ago and ran into a similar roadblock. For my first site I used Django and it was very time consuming and understanding the file structure took me a long time (mostly due to the fact that I was very impatient at the time due to time constraints). Anyway, I made another website a few weeks later and decided to use the Flask framework and it was better suited for my small site.

If I could do it again I would have used Flask for both(although I did learn a lot about Django which is a good skill to have) mainly because they are smaller sites. Django(as I understand from input from multiple professors) is best suited for larger sites and it sounds to me like a lighter frame work such as flask would better suit you. Again both of my sites were/are fairly small(one 8 page site that does some data querying with a postgresql db(Django), and the other about 15 pages that did logins and data manipulation and file uploads(Flask)) and I don't plan on expanding on those in a great way anytime soon.

Let me know if you have any questions.