GithubHelp home page GithubHelp logo

Nginx configuration about coreid HOT 6 CLOSED

alexfigtree avatar alexfigtree commented on August 16, 2024
Nginx configuration

from coreid.

Comments (6)

akscanb avatar akscanb commented on August 16, 2024

Can I see the current nginx configuration?

from coreid.

alexfigtree avatar alexfigtree commented on August 16, 2024

This is my current nginx.conf, under /usr/local/etc/nginx:

events {
    worker_connections  1024;
}

http{

server {
    listen 8080;
    server_name localhost;

    location /bitcoind/ {
    proxy_pass http://localhost:8332/;

    }


    location / {
    proxy_pass http://localhost:3000/;
    }
  }
}


from coreid.

akscanb avatar akscanb commented on August 16, 2024

Did you save the original config? Try adding the server config in to the original config. Also, if you have port 8080 occupied by a different app. You will need to change it to a different port. Realize if you do this then you also need to modify where the client connects also.

from coreid.

alexfigtree avatar alexfigtree commented on August 16, 2024

As soon as I posted my nginx configuration I realized all that it was missing. : ) Problem is no longer this nginx configuration (it has been fixed), but all the errors I've encountered after successfully running React instead.

I've noticed many small changes made to the code that have caused errors on my inspector. In particular for this commit, 82eeac7#diff-14b1e33d5bf5649597cdc0e4f684dadd, I noticed many 'imports' were modified, and this has resulting in poor navigation to individual claim and document sections, amongst other pages.

Was there are reason for changing this, and have you (or anyone) encountered navigation problems on your end as a result?

from coreid.

akscanb avatar akscanb commented on August 16, 2024

Interesting, there might have been some artifacts as I was quickly testing some stuff, and a result of me merging in the wrong stuff before pushing. That is my bad. However, I don't think that should cause major navigation problems as long as the routes stayed the same.

from coreid.

alexfigtree avatar alexfigtree commented on August 16, 2024

Some of the routing was modified, but that's ok, I'll revert the changes since I will be working on documentation this weekend. If I have any other questions on your recent commits, I will create a separate issue. Will close this one for now, thanks!

from coreid.

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.