[web-devel] Need a subsite example/tutorial/documentation
michael at snoyman.com
Thu Mar 17 18:33:10 CET 2011
On Thu, Mar 17, 2011 at 7:29 PM, Greg Weber <greg at gregweber.info> wrote:
> On Thu, Mar 17, 2011 at 10:07 AM, <vagif.verdi at gmail.com> wrote:
>> I am trying to build an intranet web app that would need access control
>> (different modules are allowed/denied to different groups of users).
>> I am thinking about putting a handle that checks credentials and then lets
>> routing to continue to match the rest of the route.
>> /app/moudle1 <- Here i check the credentials
>> /app/moudle1/path1 <- If credential are OK, then the handler falls in
>> How do i do that with yesod ? Is it something that needs a subsite ? I
>> appreciate a small example. It would help me a lot.
> You can look at the static subsite or some of the other existing ones. You
> should be able to avoid a subsite by checking the url in the auhorization
> callbacks. The community would find some kind of authorization library
> useful if you manage to generalize your approach.
>> Another question, Is there a way a automatically and transparently for
>> developer encrypt part (or all ) of the url. Like this:
> This seems possible using a custom route piece type and/or url rendering
>> where the encrypted part will be converted to normal route by the rounting
>> handler, and when urls are generated, encrypted back. Of course using a
>> separate key for each user/session.
>> Vagif Verdi
>> web-devel mailing list
>> web-devel at haskell.org
> Greg Weber
> web-devel mailing list
> web-devel at haskell.org
I think Greg is right on both points. I just wanted to add that I also
agree that subsite authoring needs to be documented properly. Now that
my personal life is starting to settle down to normal again I'm hoping
to make a major dent in the advanced section of the Yesod book.
More information about the web-devel