<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Might also be worth looking at Slimmer, built by GDS <a href="https://github.com/alphagov/slimmer">https://github.com/alphagov/slimmer</a></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">It’s a bit of Rack middleware that allows you to apply a standard header and footer, served from a different host. For example, the header and footer for <a href="http://theodi.org/">http://theodi.org/</a> is served via <a href="http://static.theodi.org/templates/www.html.erb">http://static.theodi.org/templates/www.html.erb</a> - we probably don’t use it to the best of its ability, but it sounds like it would suit your needs perfectly. Our static app is a rails app, but it could just as easily be a simple sinatra app, or even just static HTML.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><a href="https://github.com/alphagov/slimmer"><br></a></div> <div id="bloop_sign_1432027040868616192" class="bloop_sign"><span style="font-family:helvetica,arial;font-size:13px"></span>-- <br>Stuart Harrison<br><span>Sent with Airmail</span></div> <br><p style="color:#000;">On 19 May 2015 at 10:11:26, Alejandro Andres (<a href="mailto:alej@redradix.com">alej@redradix.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>
<title></title>
<div dir="ltr">I've done something similar, sepparating the apps by
subdomain, using the same rails app. That way you have a
'namespace' for each app (the subdomain). For shared data I had an
api subdomain (but beware because then you'll have to use CORS)
<div><br></div>
<div>Hope it helps :)</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature">
<div dir="ltr">
<div>-</div>
Alejandro Andrés
<div>Partner at <span style="background-color:rgb(255,255,255)"><a href="http://redradix.com/" target="_blank"><font>redradix.com</font></a></span></div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Tue, May 19, 2015 at 11:08 AM, Kerry
Buckley <span dir="ltr"><<a href="mailto:kerryjbuckley@gmail.com" target="_blank">kerryjbuckley@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi LRUG,
<div><br></div>
<div>I have a small Rails app used by a closed set of internal
users, and am about to create another, for the same users (or at
least an overlapping group). They've asked that the two apps (and
potentially more over time) are presented as one integrated front
end, rather than users having to visit multiple URLs, log in
separately etc.</div>
<div><br></div>
<div>I'm wondering what the best approach to this is. I don't want
to go to the extreme of a JS front end with the Rails apps just
presenting JSON APIs, so the main options seem to be:</div>
<div><br></div>
<div>* Separate apps with matching layouts, and headers, with some
kind of single sign-on</div>
<div>* One big app with namespaced routes, controllers etc to try
and keep things vaguely separated</div>
<div>* Separate apps into Rails engines, mounted in a master app
that manages sessions etc</div>
<div><br></div>
<div>I'm kind of leaning towards the third option, but I've never
used Rails engines before, and I'm not 100% sure how that approach
would work out. My main concern is acceptance/integration tests –
it seems to me like they'd have to live in the wrapper app as most
of them would rely on users, sessions etc.</div>
<div><br></div>
<div>Has anyone had experience of this kind of thing, and if so,
which of the above approaches would you recommend (or discourage)?
Is there a better solution I've missed? I'm about to start spiking
something with engines to see how things fall together, but some
opinions from someone who's done it in anger would be great!</div>
<div><br></div>
<div>Thanks,</div>
<div><br></div>
<div>Kerry</div>
</div>
<br>
_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">http://lists.lrug.org/pipermail/chat-lrug.org</a><br>
Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/options.cgi/chat-lrug.org</a><br>
List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<br></blockquote>
</div>
<br></div>
_______________________________________________
<br>Chat mailing list
<br>Chat@lists.lrug.org
<br>Archives: http://lists.lrug.org/pipermail/chat-lrug.org
<br>Manage your subscription: http://lists.lrug.org/options.cgi/chat-lrug.org
<br>List info: http://lists.lrug.org/listinfo.cgi/chat-lrug.org
<br></div></div></span></blockquote></body></html>