Giter Site home page Giter Site logo

Comments (3)

sruggier avatar sruggier commented on July 23, 2024

Yes, we currently have a limitation that although the applications can be in the submodules, the .platform.app.yaml files have to be in the top-level repository (someone else ran into this issue at around the same time you did). This is a bug that we intend to fix at some point. For now it would make sense for us to mention this in the documentation, which seems to strongly imply that there are no limitations.

from platformsh-docs.

drublic avatar drublic commented on July 23, 2024

Thanks for the feedback.

As this does not work as I expected it too here is a quick outline on what I currently have to do to work around that issue: I had to setup a separate repository which is build by a CI tool which clones all the submodules I need, checks it into a branch and pushes the branch to Platform.sh.
This does not make it easily possible to get different environments.
There are other problems that come up with this behavior.

Do you have any other suggestion to work around this?
Is there a timeframe on when this will be fixed?

from platformsh-docs.

sruggier avatar sruggier commented on July 23, 2024

Yeah, you could also work around this by moving the .platform.app.yaml files into the top-level repository. Then you'd include the submodules in directories alongside the .platform.app.yaml files, and then adjust the document root to point to the submodules' web root relative to each .platform.app.yaml file.

For example, your directory tree could look like this:

.git/
.platform/
    routes.yaml
    services.yaml
app1/
    .platform.app.yaml
    app1-submodule/
        index.php
app2/
    .platform.app.yaml
    app2-submodule/
        index.php

and then in app1's .platform.app.yaml file, you could include:

web:
    document_root: "/app1-submodule"
    # Or /app1-submodule/path/to/webroot if appropriate.
    passthru: "/index.php"

I realize this is a pain in comparison to how it should work, and I'm sorry for that, but it might at least be easier than what you're doing, if it doesn't break your workflow to have the .platform.app.yaml files separated like that.

from platformsh-docs.

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.