design - First approach to build a multi-place booking system -


i need first approach build booking system works multiples places. objetive system used many places.

at beginning have decide use wheel invented, there many scripts built sell code. problem of them designed 1 place only. have 2 options.

  1. modify code create multi-place system (a lot of modifications think).

  2. make 1 installation place , manage script (create installation, create db, ...). think make administration panel manage installation , on.

the project web application powered php.

the customers apply public form make de booking, each restaurant has got own administration panel bookings.

what form choose?

i go 2nd form. because can started faster (it seems per comments first require many changes). if can started faster know whether works or not. faster feedback better.

the problems might face form payments, registrations users going use public form make booking assuming there no registration or payments involved.

you wouldn't want user register every place separately, you? not want customers experience that. similar concerns payments.

sit down , think things require dependency among various installations per business. things need shared various installations operation wise. need because having idea of tell whether can automate or not. installation, database initial values can automated if operating system require many other common things become concern.


Comments

Popular posts from this blog

routing - AngularJS State management ->load multiple states in one page -

python - GRASS parser() error -

Swift game error message -