[TYPO3-dev] Something like rake db::migrate_plugins

Popy popy.dev at gmail.com
Sat May 7 21:34:51 CEST 2011


2011/5/7 Christian Opitz <christian.opitz at netzelf.de>
>
> I'm quite new to RoR, had some troubles too but didn't have nightmares
> about that yet (Or did I? Hmm...) - what do you fear?

I believe that programming in a langage by thinking like another langage is
something dangerous. For instance, more and more php framework want to look
like java. On the other side, some java projects want to reach the
simplicity of php...
I think it's a kind of snake-eating-its-own-tail story.

Oh, you are right - forgot about those projects where no CLI-access is
> possible but IMO that's a general problem which could be solved by a
> wrapper-script called via http with http-auth (already did that a few
> times for database dumps).
>
So you have a public script (protected only by a near never used password
wich is not crypted when sent) which perform some critical database
operations. I dislike that idea :D

One more time, it's just my opinion. I would prefer to put some (non
executable outside from typo3, like ext_localconf files) scripts somewhere
(in the "migrate" extension for instance), which will be executed (and
archived) by some process executed each time a Backend admin log in.
By doing this, you deploy your new files AND your "migration scripts", then
log into backend (or any other operation protected by backend login, better
that http auth)


> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>




More information about the TYPO3-dev mailing list