In Cloudfoundry the URL of an application is












0















In Cloudfoundry what is the URL of an application?



Is it of the type Domain.subdomain or subdomain.domain?










share|improve this question























  • Or is it just Domain or just subdomain

    – Sam
    Nov 15 '18 at 8:59











  • mostly app-name.domain-name and to be technically correct, it is host-name.domain-name

    – Arun
    Nov 15 '18 at 9:01













  • So each application needs to have a unique host-name or a unique domain-name?

    – Sam
    Nov 15 '18 at 9:05











  • unique host-name is fine. The host-name.domain-name combination is unique and will not be used for another App

    – Arun
    Nov 15 '18 at 9:06
















0















In Cloudfoundry what is the URL of an application?



Is it of the type Domain.subdomain or subdomain.domain?










share|improve this question























  • Or is it just Domain or just subdomain

    – Sam
    Nov 15 '18 at 8:59











  • mostly app-name.domain-name and to be technically correct, it is host-name.domain-name

    – Arun
    Nov 15 '18 at 9:01













  • So each application needs to have a unique host-name or a unique domain-name?

    – Sam
    Nov 15 '18 at 9:05











  • unique host-name is fine. The host-name.domain-name combination is unique and will not be used for another App

    – Arun
    Nov 15 '18 at 9:06














0












0








0








In Cloudfoundry what is the URL of an application?



Is it of the type Domain.subdomain or subdomain.domain?










share|improve this question














In Cloudfoundry what is the URL of an application?



Is it of the type Domain.subdomain or subdomain.domain?







cloudfoundry






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 15 '18 at 8:19









SamSam

152




152













  • Or is it just Domain or just subdomain

    – Sam
    Nov 15 '18 at 8:59











  • mostly app-name.domain-name and to be technically correct, it is host-name.domain-name

    – Arun
    Nov 15 '18 at 9:01













  • So each application needs to have a unique host-name or a unique domain-name?

    – Sam
    Nov 15 '18 at 9:05











  • unique host-name is fine. The host-name.domain-name combination is unique and will not be used for another App

    – Arun
    Nov 15 '18 at 9:06



















  • Or is it just Domain or just subdomain

    – Sam
    Nov 15 '18 at 8:59











  • mostly app-name.domain-name and to be technically correct, it is host-name.domain-name

    – Arun
    Nov 15 '18 at 9:01













  • So each application needs to have a unique host-name or a unique domain-name?

    – Sam
    Nov 15 '18 at 9:05











  • unique host-name is fine. The host-name.domain-name combination is unique and will not be used for another App

    – Arun
    Nov 15 '18 at 9:06

















Or is it just Domain or just subdomain

– Sam
Nov 15 '18 at 8:59





Or is it just Domain or just subdomain

– Sam
Nov 15 '18 at 8:59













mostly app-name.domain-name and to be technically correct, it is host-name.domain-name

– Arun
Nov 15 '18 at 9:01







mostly app-name.domain-name and to be technically correct, it is host-name.domain-name

– Arun
Nov 15 '18 at 9:01















So each application needs to have a unique host-name or a unique domain-name?

– Sam
Nov 15 '18 at 9:05





So each application needs to have a unique host-name or a unique domain-name?

– Sam
Nov 15 '18 at 9:05













unique host-name is fine. The host-name.domain-name combination is unique and will not be used for another App

– Arun
Nov 15 '18 at 9:06





unique host-name is fine. The host-name.domain-name combination is unique and will not be used for another App

– Arun
Nov 15 '18 at 9:06












1 Answer
1






active

oldest

votes


















0














It depends a lot. When you push your application, you can do nothing and rely on the defaults. The default will be for a route to be mapped to your app that is app-name.default-domain. You as a developer will set the app name and your platform operator will pick the default domain. There may be other domains available, but there's always at least one which is the default domain for apps.



Beyond that, you can control what routes are mapped to your app. If you include a manifest.yml file, you can include a routes: block, which lets you add one or more routes to your app.



Ex:



- routes:
- route: www.example.com
- route: www.example-other.com


https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#routes



You could also cf push --no-start your app, then run cf map-route to add routes and finally run cf start. That would be if you're not using a manifest.yml file.



Other interesting things you can do:





  • cf push --no-route which doesn't assign any route. This is useful for non-web apps.


  • cf push --random-route which generates a random host name instead of using your app's name.


  • cf push --route-path which allows you to map not only a domain, but also a path. Ex: www.example.com/api/v2 would send only requests to /api/v2 to the given app.


Historically, you could set domain, domains, host and hosts in your manifest.yml file and you'd get various combinations of routes mapped to your app. These options have been deprecated though and shouldn't be used going forward.



https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#route-attribute






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53315060%2fin-cloudfoundry-the-url-of-an-application-is%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    It depends a lot. When you push your application, you can do nothing and rely on the defaults. The default will be for a route to be mapped to your app that is app-name.default-domain. You as a developer will set the app name and your platform operator will pick the default domain. There may be other domains available, but there's always at least one which is the default domain for apps.



    Beyond that, you can control what routes are mapped to your app. If you include a manifest.yml file, you can include a routes: block, which lets you add one or more routes to your app.



    Ex:



    - routes:
    - route: www.example.com
    - route: www.example-other.com


    https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#routes



    You could also cf push --no-start your app, then run cf map-route to add routes and finally run cf start. That would be if you're not using a manifest.yml file.



    Other interesting things you can do:





    • cf push --no-route which doesn't assign any route. This is useful for non-web apps.


    • cf push --random-route which generates a random host name instead of using your app's name.


    • cf push --route-path which allows you to map not only a domain, but also a path. Ex: www.example.com/api/v2 would send only requests to /api/v2 to the given app.


    Historically, you could set domain, domains, host and hosts in your manifest.yml file and you'd get various combinations of routes mapped to your app. These options have been deprecated though and shouldn't be used going forward.



    https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#route-attribute






    share|improve this answer




























      0














      It depends a lot. When you push your application, you can do nothing and rely on the defaults. The default will be for a route to be mapped to your app that is app-name.default-domain. You as a developer will set the app name and your platform operator will pick the default domain. There may be other domains available, but there's always at least one which is the default domain for apps.



      Beyond that, you can control what routes are mapped to your app. If you include a manifest.yml file, you can include a routes: block, which lets you add one or more routes to your app.



      Ex:



      - routes:
      - route: www.example.com
      - route: www.example-other.com


      https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#routes



      You could also cf push --no-start your app, then run cf map-route to add routes and finally run cf start. That would be if you're not using a manifest.yml file.



      Other interesting things you can do:





      • cf push --no-route which doesn't assign any route. This is useful for non-web apps.


      • cf push --random-route which generates a random host name instead of using your app's name.


      • cf push --route-path which allows you to map not only a domain, but also a path. Ex: www.example.com/api/v2 would send only requests to /api/v2 to the given app.


      Historically, you could set domain, domains, host and hosts in your manifest.yml file and you'd get various combinations of routes mapped to your app. These options have been deprecated though and shouldn't be used going forward.



      https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#route-attribute






      share|improve this answer


























        0












        0








        0







        It depends a lot. When you push your application, you can do nothing and rely on the defaults. The default will be for a route to be mapped to your app that is app-name.default-domain. You as a developer will set the app name and your platform operator will pick the default domain. There may be other domains available, but there's always at least one which is the default domain for apps.



        Beyond that, you can control what routes are mapped to your app. If you include a manifest.yml file, you can include a routes: block, which lets you add one or more routes to your app.



        Ex:



        - routes:
        - route: www.example.com
        - route: www.example-other.com


        https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#routes



        You could also cf push --no-start your app, then run cf map-route to add routes and finally run cf start. That would be if you're not using a manifest.yml file.



        Other interesting things you can do:





        • cf push --no-route which doesn't assign any route. This is useful for non-web apps.


        • cf push --random-route which generates a random host name instead of using your app's name.


        • cf push --route-path which allows you to map not only a domain, but also a path. Ex: www.example.com/api/v2 would send only requests to /api/v2 to the given app.


        Historically, you could set domain, domains, host and hosts in your manifest.yml file and you'd get various combinations of routes mapped to your app. These options have been deprecated though and shouldn't be used going forward.



        https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#route-attribute






        share|improve this answer













        It depends a lot. When you push your application, you can do nothing and rely on the defaults. The default will be for a route to be mapped to your app that is app-name.default-domain. You as a developer will set the app name and your platform operator will pick the default domain. There may be other domains available, but there's always at least one which is the default domain for apps.



        Beyond that, you can control what routes are mapped to your app. If you include a manifest.yml file, you can include a routes: block, which lets you add one or more routes to your app.



        Ex:



        - routes:
        - route: www.example.com
        - route: www.example-other.com


        https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#routes



        You could also cf push --no-start your app, then run cf map-route to add routes and finally run cf start. That would be if you're not using a manifest.yml file.



        Other interesting things you can do:





        • cf push --no-route which doesn't assign any route. This is useful for non-web apps.


        • cf push --random-route which generates a random host name instead of using your app's name.


        • cf push --route-path which allows you to map not only a domain, but also a path. Ex: www.example.com/api/v2 would send only requests to /api/v2 to the given app.


        Historically, you could set domain, domains, host and hosts in your manifest.yml file and you'd get various combinations of routes mapped to your app. These options have been deprecated though and shouldn't be used going forward.



        https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#route-attribute







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 28 '18 at 13:50









        Daniel MikusaDaniel Mikusa

        6,02011015




        6,02011015
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53315060%2fin-cloudfoundry-the-url-of-an-application-is%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Bressuire

            Vorschmack

            Quarantine