Integrations

Nearest! can be run as stand-alone website or can be integrated into existing websites. We gathered detailed information about pros and cons of every integration in our blog.


iframe

The classical way of integrating external web services is via iframe which loads an external url into a predefined area onto your website. This integration should only be used if SEO isn't important and the host websites cares about all mobile functionality and optimization. Otherwise a seamless user journey cannot be guarenteed.

Code

                  
<iframe src="https://yourapp.nearest.place" height="500" width="100%"
  allow="geolocation"
  style="border:none;"></iframe>
                  
                

Example

https://nearest.place/integrations/demo/iframe


Stand-alone via subdomain

Nearest! can either be operated as a subdomain, for example, locations.mycompany.com or as a domain. For example, www.mylocations.io. All you have to do is add or customize a CNAME or A record in the DNS server.

A-Record

Subdomain

                  
subdomain           IN  A     136.243.94.96             ; IPv4 address for subdomain.example.com
subdomain           IN  AAAA  2a01:4f8:171:6df::2       ; IPv6 address for subdomain.example.com
                  
                

Root-domain

                  
@                   IN  A     136.243.94.96             ; IPv4 address for example.com
@                   IN  AAAA  2a01:4f8:171:6df::2       ; IPv6 address for example.com
www                 IN  A     136.243.94.96             ; IPv4 address for www.example.com
www                 IN  AAAA  2a01:4f8:171:6df::2       ; IPv6 address for www.example.com
                  
                

CNAME-Record (only subdomains)

                  
subdomain          IN  CNAME finder.nearest.place.      ; record for subdomain.example.com
                  
                
Changes to the DNS of your domain can lead to unavailability of the entire domain and should only be performed by system administrators or devops.

Example

https://nearest.place/integrations/demo/subdomain


ProxyPass (comming soon)

If you need to integrated Nearest! into the main navigation of your website (mycompany.com/locations) a ProxyPass connection needs to be added to your web-server configuration. In this case external traffic will be encrypted by your host-systems ssl certificate. Internal traffic will be encrypted with the certificate provided by Nearest!.

Nginx

                  
server {
    listen myhost:80;
    server_name  myhost;
    location /filialen/ {
        root /path/to/myapp/public;
        proxy_set_header X-Forwarded-Host $host:$server_port;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass https://yourapp.nearest.place/;
    }
}
                  
                

Apache

                  
<VirtualHost myhost:80>
  ServerName myhost
  DocumentRoot /path/to/myapp/public
  ProxyPass /filialen/ https://yourapp.nearest.place/
  ProxyPassReverse /filialen/ https://yourapp.nearest.place/
</VirtualHost>
                  
                
Changes to the webserver configuration can lead to unavailability of the entire server and should only be performed by system administrators or devops.

Example

https://nearest.place/integrations/demo/subfolder

Contact

GDPR has stolen our contact form. 😱

Get In Touch

Nearest! RWGL UG (haftungsbeschränkt)

  • Email: info@nearest.place
  • Twitter: @NearestPlace
  • Web: nearest.place