Problem at startup laravel9 system after git clone

By -

After I made a git clone with my project, composer install and everything and php artisan serve I'm just getting three lines of footers like this: 2022 © Webshooter LM AB | Du använder version 4.1.9 | Laravel 9.12.2 screendump: https://imgur.com/Lyt5IhS If I change http://localhost:8000/app/ to http://localhost:8000/auth/login I come to the login page. How to prevent that and to come to the information page directly as here: https://imgur.com/eNJzxWW Then address field is: http://localhost:8000 After that there is no problem, it only happens after a git clone.

Here some more information.

The clone:

git clone https://github.com/WebshooterLM/Webshooter_web_Laravel9.git

This is how it looks in my terminal just after the cloning:

Ralphs-MacBook:Webshooter_web_Laravel9 ralph$ pwd
/Users/ralph/laravel9-final/Webshooter_web_Laravel9
Ralphs-MacBook:Webshooter_web_Laravel9 ralph$ 

Ralphs-MacBook:Webshooter_web_Laravel9 ralph$ git status
On branch master
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean

Then I do php artisan serve

When I put localhost:8000 in adress-field the three footer-lines is all I see.

This is in the address field: http://localhost:8000/app/ It should only show http://localhost:8000

Here is the app.blade it gets stuck in:

@include('layouts.header')
<script>
    (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
                (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
            m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
    })(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
</script>


    <base href="/">
    <div ui-view="navigation" class="hidden-print"></div>

    <div class="row hidden-print" ng-show="loadingState">
         <div class="col-sm-2 col-sm-offset-5 text-center text-muted padding-top-30 padding-bottom-30">
             <div class='uil-default-css'>
                 <div style='top:60px;left:96px;width:8px;height:80px;background:#00ABAA;-webkit-transform:rotate(0deg) translate(0,-60px);transform:rotate(0deg) translate(0,-60px);border-radius:0px;position:absolute;'></div>
                 <div style='top:60px;left:96px;width:8px;height:80px;background:#00ABAA;-webkit-transform:rotate(90deg) translate(0,-60px);transform:rotate(90deg) translate(0,-60px);border-radius:0px;position:absolute;'></div>
                 <div style='top:60px;left:96px;width:8px;height:80px;background:#00ABAA;-webkit-transform:rotate(180deg) translate(0,-60px);transform:rotate(180deg) translate(0,-60px);border-radius:0px;position:absolute;'></div>
                 <div style='top:60px;left:96px;width:8px;height:80px;background:#00ABAA;-webkit-transform:rotate(270deg) translate(0,-60px);transform:rotate(270deg) translate(0,-60px);border-radius:0px;position:absolute;'></div>
             </div>
         </div>
    </div>

    <div class="container-fluid" ng-hide="loadingState">
        <div class="row">
            <div class="col-sm-12">
                @include('alerts.factorymessages')
                <div ui-view="content"></div>
            </div>
        </div>
    </div>

@include('layouts.footer')

When I refresh it shows the big green crosses a short time. After that the three footer-lines only shows. The crosses are rotating normally when it takes a while to load a page.

If I write http://localhost:8000/auth/login the login page comes up and after that all is working normal. The problem occurs only direct after a fresh clone.

What could be the problem?



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more