[Haskell-beginners] Install on "foreign" server problems

[Michael Snoyman]

On Mon, May 30, 2011 at 11:53 PM, Lawrence Bottorff
<galaxybeingplan9 at gmail.com> wrote:
>> Hi Lawrence
>>
>> I think a lot of us are finding that the easiest solution is to
>> compile the binaries locally and upload to the server. In my case,
>> I've tried having the compiler on a VPS, but compiling is very
>> memory-intensive, and it can be a real pain whenever you need to
>> upgrade libraries.
>>
>> My newest deployment is simply an EC2 micro instance running Ubuntu
>> 32-bit, just like I have on my local system. I compile the app, copy
>> the binary and the static files, and deployment is done. I'll likely
>> be adding some notes about this to the Yesod book, and perhaps even
>> put together some scripts to automate the process more.
>>
>> Michael
>
> So I would do an "in situ/in-place" binary install on a home machine and
> simply move that whole installation directory onto the foreign machine.
> Hmmm.... What about dependent libraries? If it can't find libc (or the
> GL-mesa libraries) won't it break? I'm guessing from the instructions that I
> would do a
> # ./configure --prefix=/home/me/haskell/
> then a
> # make in-place
> Is this right? Then move that /haskell directory onto the foreign box?
> Lb
>

What I meant was not to have GHC on the server at all. Build your web
apps locally, and then upload the binaries to the server. You can even
install a virtual machine locally with the same OS as what your server
is using.

Michael