Install Issues

[pedromorgan]

I just updated the project..

And the auth bug still not working..

But also a major restructure and now a makefile..

Can we put a bit more info.. on this make stuff

I was expecting to run
cd ~src/giithub.com... hog..
and then
go run main.go

I dont like makefile.. I want
go run main.go

What I am getting down to is that now its looks like all little projects..
which is good, lets go for it..
But out of the box, we dont want make imho..
This aint gonna run on windows and part of my "sales pitch"
is go.. ie no make.. (am trying to wean old c/c++ and c# coders)

get the drift..
does it make sense..
its a makeFile.. "Wtf is a makefile and how do I use it said le windows coder on her xp ?"
WindowsFileTranslation I replied, and then explain windows.. vs make

anyway...
minor point trying 2 make
only cos its neat and works for me and thanks Ian ;-) and all

[ian-kent]

The refactoring has been done in preparation for supporting #8

The pre-built binaries are still available to download on GitHub, so if you're just using MailHog as a development tool and don't need to make any code changes, the Windows binary is the way to go! (Although, it hasn't got the latest bug fix in, which I think was the auth fix - I'll release an updated binary later today).

The makefile is unavoidable (or at least, some form of "build" tool), since it compiles the UI assets into a go source file to support a single-file deployment. Which works ok for local development, but less so if you wanted to deploy it as a shared service.

One option if building on Windows would be to use Cygwin, Vagrant or Docker. Alternatively there's a Win32 make you could use - http://gnuwin32.sourceforge.net/packages/make.htm

But fair point, I'll some more add more documentation around the build process.

Thanks @pedromorgan

[pedromorgan]

ahh ok I understand now, having digged a little deeper (and a go newbie)..

sorry for the noise