Surge – Static Web Publishing for Front-End Developers

Re:Surge – Static Web Publishing for Front-End Developers by macandcheese on Friday June 10, 2016 @04:02PM (#11879555)

Agree, Middleman + Middleman s3_sync is such an easy set up and deploy... Middleman project doesn't get enough love I think...

[ Parent | on HN ]

Re:Surge – Static Web Publishing for Front-End Developers by cutler on Friday June 10, 2016 @07:44PM (#11881076)

I gave up on Middleman when I couldn't get anyone in various Ruby mailing lists and IRC channels to advise me how to stop Middleman deleting directories which aren't mirrored in the src directory. Jekyll has the keep_files: [] config option.

[ Parent | on HN ]

Re:Surge – Static Web Publishing for Front-End Developers by macandcheese on Friday June 10, 2016 @10:05PM (#11881624)

Definitely looking in the wrong places, based on Middleman's more "lightweight" front-end audience. You'd probably get faster responses on Twitter.

[ Parent | on HN ]

Re:Surge – Static Web Publishing for Front-End Developers by elliotec on Friday June 10, 2016 @08:13PM (#11881216)

I had that same issue. But then I just mirrored them in the src directory and it was fine.

[ Parent | on HN ]

Re:Surge – Static Web Publishing for Front-End Developers by cutler on Saturday June 11, 2016 @03:20PM (#11884885)

That's not practical when you have a massive images directory. A decent framework should have the equivalent of Jekyll's keep_files:

[ Parent | on HN ]