ZF2 project structure

[Ralf Eggert]

Hi,

I have a question to the ZF2 project structure after installing the
skeleton application. Which files can be ignored when uploading to a
productive server?

Detailed questions:

- Can the several composer*.* and the init_autoloader.php file be
  ignored?

- Can the /vendor/composer directory be ignored?

- Which of the subdirectories of /vendor/zendframework/zendframework
  can be ignored?

- How about all the *.md files?

Please advise.

Thanks and best regards,

Ralf


--
Ralf Eggert
Geschäftsführer

Travello GmbH
An der Eiche 15
25421 Pinneberg

Geschäftsführer: Ralf Eggert
Amtsgericht Pinneberg HRB 6112 PI

Tel: [phone]
Fax: [phone]
E-Mail: [hidden email]
Web: http://www.travello.de

--
List: [hidden email]
Info: http://framework.zend.com/archives
Unsubscribe: [hidden email]

[Dennis Winter]

Hi Ralf,

It's possible to ignore files within the vendor/zendframework/zendframework directory! Normally EVERY file not residing in the library folder should be ignorable..

You may choose to ignore the composer files in your production environment, also the vendor/composer folder can be ignored.

The only thing you'll have to overthink is that the autoloading functions are not usable, if you remove the vendor/composer folder! You would have to register your own autoloading mechanism!

The next part you should consider before removing the composer files from production is: Versioning. It's totally awesome that one can control easily which versions of which package are used in the different environments.

As long as it's not a major security break, which it normally shouldn't be, let those composer stuff installed!

The *.md files are just some plaintext files, spiced up with a little bit of Markdown syntax, so they could be removed too!

Best regards
Dennis



Am 05.08.2012 um 11:06 schrieb Ralf Eggert <[hidden email]>:

> Hi,
>
> I have a question to the ZF2 project structure after installing the
> skeleton application. Which files can be ignored when uploading to a
> productive server?
>
> Detailed questions:
>
> - Can the several composer*.* and the init_autoloader.php file be
>  ignored?
>
> - Can the /vendor/composer directory be ignored?
>
> - Which of the subdirectories of /vendor/zendframework/zendframework
>  can be ignored?
>
> - How about all the *.md files?
>
> Please advise.
>
> Thanks and best regards,
>
> Ralf
>
>
> --
> Ralf Eggert
> Geschäftsführer
>
> Travello GmbH
> An der Eiche 15
> 25421 Pinneberg
>
> Geschäftsführer: Ralf Eggert
> Amtsgericht Pinneberg HRB 6112 PI
>
> Tel: [phone]
> Fax: [phone]
> E-Mail: [hidden email]
> Web: http://www.travello.de
>
> --
> List: [hidden email]
> Info: http://framework.zend.com/archives
> Unsubscribe: [hidden email]
>
>

--
List: [hidden email]
Info: http://framework.zend.com/archives
Unsubscribe: [hidden email]

[Marco Pivetta]

I'm curious: why would you even want to delete all those files?

Also, if you use composer, you surely don't want to delete it. That's your
autoloader, keep it in mind! What you probably don't want to be accessible
from web is your `composer.phar`

Marco Pivetta

http://twitter.com/Ocramius

http://marco-pivetta.com



On 5 August 2012 13:41, Dennis Winter <[hidden email]> wrote:

> Hi Ralf,
>
> It's possible to ignore files within the
> vendor/zendframework/zendframework directory! Normally EVERY file not
> residing in the library folder should be ignorable..
>
> You may choose to ignore the composer files in your production
> environment, also the vendor/composer folder can be ignored.
>
> The only thing you'll have to overthink is that the autoloading functions
> are not usable, if you remove the vendor/composer folder! You would have to
> register your own autoloading mechanism!
>
> The next part you should consider before removing the composer files from
> production is: Versioning. It's totally awesome that one can control easily
> which versions of which package are used in the different environments.
>
> As long as it's not a major security break, which it normally shouldn't
> be, let those composer stuff installed!
>
> The *.md files are just some plaintext files, spiced up with a little bit
> of Markdown syntax, so they could be removed too!
>
> Best regards
> Dennis
>
>
>
> Am 05.08.2012 um 11:06 schrieb Ralf Eggert <[hidden email]>:
>
> > Hi,
> >
> > I have a question to the ZF2 project structure after installing the
> > skeleton application. Which files can be ignored when uploading to a
> > productive server?
> >
> > Detailed questions:
> >
> > - Can the several composer*.* and the init_autoloader.php file be
> >  ignored?
> >
> > - Can the /vendor/composer directory be ignored?
> >
> > - Which of the subdirectories of /vendor/zendframework/zendframework
> >  can be ignored?
> >
> > - How about all the *.md files?
> >
> > Please advise.
> >
> > Thanks and best regards,
> >
> > Ralf
> >
> >
> > --
> > Ralf Eggert
> > Geschäftsführer
> >
> > Travello GmbH
> > An der Eiche 15
> > 25421 Pinneberg
> >
> > Geschäftsführer: Ralf Eggert
> > Amtsgericht Pinneberg HRB 6112 PI
> >
> > Tel: [phone]
> > Fax: [phone]
> > E-Mail: [hidden email]
> > Web: http://www.travello.de
> >
> > --
> > List: [hidden email]
> > Info: http://framework.zend.com/archives
> > Unsubscribe: [hidden email]
> >
> >
>
> --
> List: [hidden email]
> Info: http://framework.zend.com/archives
> Unsubscribe: [hidden email]
>
>
>

[Ralf Eggert]

Hi Dennis and Marco,

thanks for your comments. I never thought about the upgrading part.
Though I will always first upgrade on the development server and later
on on the production server. Upgrading on the production server with the
composer seems interesting, but I am not sure if I really want that.

Best regards,

Ralf

--
List: [hidden email]
Info: http://framework.zend.com/archives
Unsubscribe: [hidden email]

[Dennis Winter]

For me it's a great point, that I don't need to upload every single library via FTP! Server to server communication is normally somewhat faster and so to me composer wins the race!

Of course I'm working with a release branch with the exact versions as I would like to install to production.



Am 05.08.2012 um 17:10 schrieb Ralf Eggert <[hidden email]>:

> Hi Dennis and Marco,
>
> thanks for your comments. I never thought about the upgrading part.
> Though I will always first upgrade on the development server and later
> on on the production server. Upgrading on the production server with the
> composer seems interesting, but I am not sure if I really want that.
>
> Best regards,
>
> Ralf
>
> --
> List: [hidden email]
> Info: http://framework.zend.com/archives
> Unsubscribe: [hidden email]
>
>

--
List: [hidden email]
Info: http://framework.zend.com/archives
Unsubscribe: [hidden email]

[Marco Pivetta]

@Ralf: well, there's "composer.lock" for that. You don't run the upgrade on
the production server (that is dangerous exactly like upgrading a linux
distro without verifying that things won't break!), you just run an
"install" with the updated "composer.lock" once it has been updated (and
tested) in your dev environment. That updates dependencies to the state
defined in "composer.lock", which is quite amazing in terms of spared time.

Marco Pivetta

http://twitter.com/Ocramius

http://marco-pivetta.com



On 5 August 2012 17:10, Ralf Eggert <[hidden email]> wrote:

> Hi Dennis and Marco,
>
> thanks for your comments. I never thought about the upgrading part.
> Though I will always first upgrade on the development server and later
> on on the production server. Upgrading on the production server with the
> composer seems interesting, but I am not sure if I really want that.
>
> Best regards,
>
> Ralf
>
> --
> List: [hidden email]
> Info: http://framework.zend.com/archives
> Unsubscribe: [hidden email]
>
>
>