Git Product home page Git Product logo

Comments (4)

bcremer avatar bcremer commented on May 21, 2024

Hi,

thank's for your feedback.

Why would you need to remove the installation dir? The installation via git is not recommended for production usage.
For production usage you can find the release package at http://wiki.shopware.de/Downloads_cat_448.html.

As an alternative you could add the installation dir to the .gitignore file.

A git submodule sounds interesting but adds some complexity to the installation process.

We will revisit your idea when we implement composer for our dependency managment.

from shopware.

terwey avatar terwey commented on May 21, 2024

Hi @bcremer,

Adding it to the .gitignore means my own fork would not have the installation dir included which makes that difficult to maintain again compared to the normal upstream.

As to why run directly from the git? Well you do tag your versions so I can just grab the current one. And I prefer to work in a version controlled environment vs some tarballs that might mess up the whole place and don't have a backup in place ;)

Composer can also sound the problem because the Installation dir can just be moved into a different Repo and can be pulled in the moment you install via Composer.

The other possibility is renaming the install directory in git to something like install.dist and just include .dist in the .gitignore. Then locally you rename it to install and all is well. Just have the scripts check if it's current dir includes the word 'dist' and if so, die() :)

from shopware.

bcremer avatar bcremer commented on May 21, 2024

Hi @terwey,

you can just setup a global .gitignore file:

git config --global core.excludesfile ~/.gitignore_global
echo "/var/www/shopware/install/" > ~/.gitignore_global

So you don't have to mess up your local shopware-git clone.

from shopware.

terwey avatar terwey commented on May 21, 2024

Hi @bcremer,

I totally did not think of that. Good idea until the 'problem' is resolved in a nicer way :) I'll leave the issue open until another solution has been found. But it's up to you I guess.

Off topic: I'm having trouble upgrading from 3.5.6 to 4.0.5 should I post that as an issue here on Github or somewhere else? Not sure how those issues are tracked. I already posted the problem here: http://forum.shopware.de/installation-einstieg-f54/database-upgrade-problems-t11356.html

from shopware.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.