Sorry, bit too quick answer on the quick questions: tests are not in the doctrine-install; it is with another package where they are included in the Composer-install. For more information about deployment of Doctrine: please google.
On Monday, 17 March 2014 10:59:05 UTC+1, Herman Peeren wrote: > > The way I do it: > 1) I provide an installation script using the sql. That can be the sql > provided by Doctrine, but can also be based on a database-dump (for > instance if you want to provide some basic data too and limit the use to a > specific database-vendor). My users do not use a command line. They only > install from a GUI. > 2) I leave out all tests and composer.json / composer.lock. I limit direct > access to folders with .htaccess (or an equivalent when under IIS). I > probably could leave out all console-like things, but until now I just left > it there... There is more information about that to be found on the > internet. > > > > On Monday, 17 March 2014 10:17:55 UTC+1, Parsifal wrote: >> >> After finishing mappings, run the shell command to update db schema and >> write an installation script with dbal. My question is that >> 1) my users still need to run schema update command after installation? >> Or this is an implementation job only? >> 2) I believe some doctrine parts are for implementation only and end-user >> don't need them to run my script? So which part of doctrine can be deleted >> to decrease the size of my package as i can't simply provide composer.lock >> and composer.json and I need to obfuscate doctrine alongwith my package due >> to ionCube? >> > -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
