router

My lab runs RStudio on a server. A couple weeks ago, from my cousin's house, I successfully ssh'd into the server and pulled up the server-side RStudio through my local Firefox browser. Now when I try to access the server RStudio from home (via my own router), it doesn't work. I need help troubleshooting, and I'm guessing it's some problem on the router. I'm running Mac OSX 10.6.8. No idea what the university server's running, but I don't think it's a server-side problem. Here's how it worked the first time I did it, at my cousin's house: first, I VPN into the university network; then I call

I just started using the new routing library (@angular/router v3.0.0-alpha.7) but following the official docs leads to error below: browser_adapter.ts:74: EXCEPTION: Error: Uncaught (in promise): Error: Cannot find primary outlet to load 'HomePage' Question is - how do I get rid of the error and make the router behave as expected? Have I missed a setting? (Same error appears when using the alpha.6 version.) app.component.ts import { Component } from '@angular/core'; import { ROUTER_DIRECTIVES } from '@angular/router'; @Component({ selector: 'app', template: ` <p>Angular 2 is running...</p> <!-

This might be a basic question, but in Angular2 is there any way to do conditional routing ? Or, would someone do that outside the router ? I know ui-router had some ability to do this, but I haven't seen anything similar in Angular2s router Günter Zöchbauer update In the new router guards can be used instead https://angular.io/guide/router#milestone-5-route-guards original (for the long gone router) Implement the CanActivate lifecycle hook like shown here Life cycle hooks in Angular2 router and return false if you want to prevent the navigation. See also https://angular.io/docs/ts/latest/api

I tried to fetch the router address this way. - (NSString *) routerIp { NSString *address = @"error"; struct ifaddrs *interfaces = NULL; struct ifaddrs *temp_addr = NULL; int success = 0; // retrieve the current interfaces - returns 0 on success success = getifaddrs(&interfaces); if (success == 0) { // Loop through linked list of interfaces temp_addr = interfaces; while(temp_addr != NULL) { if(temp_addr->ifa_addr->sa_family == AF_INET) { // Check if interface is en0 which is the wifi connection on the iPhone if([[NSString stringWithUTF8String:temp_addr->ifa_name] isEqualToString:@"en0"]) { //

I want to separate Routes from my server.js file. I am following this tutorial on Scotch.io http://scotch.io/tutorials/javascript/build-a-restful-api-using-node-and-express-4 It is working if all lines are on server.js file. But I am failing to separate. How can I make this work? server.js // set up ====================================================================== var express = require('express'); var app = express(); var bodyParser = require('body-parser'); // configuration =============================================================== app.use(bodyParser()); var port = process.env.PORT

What is the differences between these two and what are the use cases for each? The docs aren't exactly helpful: forRoot creates a module that contains all the directives, the given routes, and the router service itself. forChild creates a module that contains all the directives and the given routes, but does not include the router service. My vague guess is that one is for the 'main' module and the other is for any imported modules (since they would already have the service available from the main module), but I can't really think of a use case. Max Koretskyi aka Wizard I strongly suggest