HAppS Demo

Several people requested that I post a link to a running instance of the HAppS code that I developed here over several posts. One person was nice enough to actually offer me the use of a server. So the demo is now up and running. It's not at all meant to be user friendly, since it's just a demo of the basic HAppS capabilities. So here are a list of links that are useful. Hopefully this will be useful.

Comments

Unknown said…
I've noticed that if you reboot the app, when it comes back up whoever was logged back in before it went down stays logged in. Not sure if this is a feature or a bug.

Apropos, thanks for your directions on how to get a happs app to start automatically on reboot. Snipping from your private communications...

cp /etc/init.d/ssh /etc/init.d/happs-app

edit that to do the right thing with Main.exe executable.

install it into the linux init with

sudo update-rc.d happs-app multiuser

this is all following the docu at

http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.3

(Works at least for deb/ubuntu.)

(For what it's worth: I'm the guy that donated my server for the demo, so both mightybyte and I are running on the same box.)
March 3, 2008 at 12:56 PM
mightybyte said…
Yes, that session persistence is a feature. Two things cause that. First, because Session is in HAppS state, it is persisted across server restarts. Second, this app creates a cookie that does not expire. If either the recorded session, or the session cookie went away, it would be the same as logging out.
March 3, 2008 at 1:01 PM
Unknown said…
Ok, two feature requests.

1) logout
2) actual email authentication (happs sends you an email with a link, you click on it, your email is authenticated.)

ps

3) profit :)
March 3, 2008 at 1:08 PM
Unknown said…
with your permission, I put your happs sample app into my google project hosting account at

happs tutorial

where I hope to work on it further, perhaps in collaboration with you or others who would like to flesh out the skeleton.
March 5, 2008 at 2:09 AM
Unknown said…
Well the links initially posted no longer work -- I think my server ip changed or something changed, can't remember.


However the ideas were incorporated into a demo that can be viewed at happs tutorial. Much of the code there is based on what I found here, though by now extensively tweaked.

This demo is also installable via cabal as is explained in one of the early pages of the tutorial
August 28, 2008 at 7:15 AM
Post a Comment

Popular posts from this blog

A Hopefully Fair and Useful Comparison of Haskell Web Frameworks

Recently there has been a lot of discussion and questions about the differences between the big three Haskell web frameworks: Happstack, Yesod, and Snap. Different pieces of the answer have been discussed in a number of places. In this post, I'd like to try to give a more complete comparison. Hopefully it will be relatively unbiased, but without being so watered down that it is useless. I've succeeded if you can't tell which framework I'm a major contributor to based solely on the text of this post. Happstack First, up is Happstack , the oldest of the three with original commit history as early as February, 2005. Happstack used to be called HAppS . It was primarily composed of a web server based on lazy IO, a fairly radical (for the time) in-memory persistence approach for storing and versioning native Haskell data types, and a library called IxSet for making it easier to use this state system with relational data access patterns. I've heard a number of pe
Read more

Setting Up A Private Nix Cache

I recently went through the process of setting up a private Nix binary cache. It was not obvious to me how to go about it at first, so I thought I would document what I did here. There are a few different ways of going about this that might be appropriate in one situation or another, but I’ll just describe the one I ended up using. I need to serve a cache for proprietary code, so I ended up using a cache served via SSH. Setting up the server For my cache server I’m using an Amazon EC2 instance with NixOS. It’s pretty easy to create these using the public NixOS 18.03 AMI. I ended up using a t2.medium with 1 TB of storage, but the jury is still out on the ideal tradeoff of specs and cost for our purposes. YMMV. The NixOS AMI puts the SSH credentials in the root user, so log in like this: ssh -i /path/to/your/key.pem root@nixcache.example.com To get your new NixOS machine working as an SSH binary cache there are two things you need to do: generate a signing key and turn on cache serv
Read more

Dependent Types are a Runtime Maybe

Awhile back I was discussing dependent types with someone and we ended up concluding that dependent types can always be replaced by a runtime Maybe.  This seemed to me then (and still does today) as a fairly surprising and provocative conclusion.  So I thought I'd put the idea out there and see what people think. Let's look at a few examples that are commonly used to illustrate dependent types: Vectors of length N Matrices of size m x n Sorted lists Height-balanced trees (trees where the height of subtrees differ by at most one) The argument is roughly as follows.  All of these examples ultimately boil down to enforcing some kind of constraint on some data types.  The more powerful your dependent type system, the more rich and expressive will be the constraints that you can enforce.  If we take this thought experiment to its logical conclusion, we end up with a dependent type system that allows us to enforce any constraint that can be computed. The important realization here is
Read more