100 feet through a house is likely going to be outside Bluetooth range, but wifi should work.
For access within your LAN you'll use the same ip address for the RPi but specify a different path. Eg: to see my R'Pints taplist I use
http://192.168.1.200/index.php and to see my BrewPi instances running on the same system I use
http://192.168.1.200/brewpiN/index.php (where N = 1 through 4 corresponding to the four instances).
For access outside your LAN you need to set your gateway or router for "port-forwarding", then use discrete port numbers in the url to get the router to send the requests to the correct system. For the same targets as above, the external URLs would be
http://xx.xxx.xxx.xx:85/index.php and
http://xx.xxx.xxx.xx:85/brewpiN/index.php, respectively...
There are some idiosyncrasies with any BrewPi installation depending on which OS and the connectivity method used. I advise installing BrewPi into its own folders to avoid stepping on any other packages. For instance, RaspberryPints installs into /var/www (or /var/www/html) and if you install BrewPi into the same folder it'll whack a couple of R'Pints files.
There are two file trees for each BrewPi instance, with the default installation putting one rooted under /home/brewpi and the other under /var/www (or /var/www/html). If you intend to run a single BrewPi instance, I would root the latter folder in /var/www/brewpi (or /var/www/html/brewpi).
For multiple BrewPi instances, each needs to be in its own folder. I use /home/brewpi1 .../home/brewpi2, etc, and /var/www/brewpi1, /var/www/brewpi2, etc. You can then use the URL to point to each instance.
You should consider moving this conversation to
the quasi-official BrewPi thread where you'll have a full audience of BrewPi users to draw from...
Cheers!