Periodict deployment of project from oxid_vm to shared server

English forums
1

Hi!
I want to know your opinion:

I have oxid_vm with OXID EE6.0 and one module with old-style(metadata 1.1) and one with metadata 2.0 and composer dependencies. Everything works well on vm.

In the time i made some changes and now - how should looks deployment to the shared server without composer, git, etc…??? (oxid is already installed on shared server before changes version)

  1. I now it is bad :slight_smile: but can i copy/paste all source folder to the shared server and it should work?
  2. How about module with composer dependencies? Should i do something before i will copy it to the sharedserver? (i mean something with vendor/bin or something else?) Maybe should i give up with modules with composer dep. in sharedserver?
  3. Can i copy module with composer dependencies to server with no composer? or should i copy only old-style convention?
  4. If everything is NO how should i do this correct?

Thanks!

2

I think it should work like this:

  • To install oxid on the shared server, copy all files (source and vendor) from local to remote right before you run graphical setup
  • whenever you change something locally, e.g. install a module, copy the changes in source directory only (e.g. module directory) to remote, as you did before v6
  • additionally, whenever you run composer locally, e.g. in order to install a module, copy the whole vendor directory to remote

There is an article about this here: https://docs.oxid-esales.com/developer/en/6.0/getting_started/installation/eshop_installation_without_composer.html

3

additionally, whenever you run composer locally, e.g. in order to install a module, copy the whole vendor directory to remote

Soo you said that it won’t be any problems with symbolic links?

Thanks!

4

In the link i supplied there is a section about how to replace the symbolic links in /vendor/bin with files. You can do this, but i checked and couldn’t find a place where oxid uses those links.

5

In the setup routine, @leofonic. Actually, the symlinks shouldn’t disappear in oxvm at all, as it is ubuntu based.

6

for now i thought that symbolic links are important only for INSTALLATION PROCCESS. Soo when i make composer update (after add new modue) i need to create new symlinks and then copy folder vendor to sharedserver? @marco.steinhaeuser

7

Not that I’m really experienced in updating OXID eShop 6 - but I think, you’re right: symlinks will IMO only be used during the (graphical) setup process.

1 Like
8

Setup and shop both run fine without the symlinks, so i think they are not used at all except when you call them from the commandline yourself.

1 Like