inhost | Deploy your server via web hooks | Continuous Deployment library

Networking is a big topic, but generally speaking

• big networks (like the Internet) are made up of smaller networks (like your local network)
• devices on smaller networks aren't usually accessible from outside of those networks¹
• the IP address you've partly shown starts with 192 and I bet the next octet is 168, which means it's a private network and therefore can't be accessed from the Internet (as an example, there are many machines out there with the address 192.168.1.10—this can exist on any private network)
• if you need to expose something on your local network, for example something with an IP address of 192.168.1.10, you must do some extra work²

Here are some options:

• Host your database in the cloud, e.g. using Heroku's PostgreSQL service
• Host your web service internally so it can connect to your database using its internal 192.168.x.y address
• Host internally as with the previous option and expose your local web application to the Internet so users can access it from outside your network
• Rent a VPS so you can host outside of your network but retain a measure of control about how your data is stored (and accept the administrative overhead and responsibility that comes with that)

I wouldn't suggest leaving the web application outside your network, your database inside your network, and exposing the database to the Internet. There's very little value in doing that, especially since Heroku's IP addresses change regularly so you can't easily lock access down to your application. Best case scenario you'll have a publicly available database only accessible over SSL (exactly what Heroku and other providers can offer) that you'll have to administer yourself.

Outgoing connections are relatively easy, e.g. if you wanted to connect a web service running on your local network to a database in the cloud, but I don't think that helps you.

¹This is a Good Thing™ since it provides a layer of protection against direct attacks on your personal devices. Wouldn't it be awful if your machine got hacked every time you waited a few days to install updates on Windows?

²An example would be to set up port forwarding on your network's public IP address, say 123.123.123.123, such that requests to 123.123.123.123:1234 are routed to a specific IP address and port on your internal network, for example 192.168.1.10:5432.