Manifest: A 1-file micro-back end • Hacker News Board

Re: Manifest: A 1-file micro-back end

#21

Post by yakshaving_jgt » Fri, Mar 21, 2025, 2:32 PM UTC

If I need a 1-file backend, I can pretty easily do this in Haskell. I have more trust in this still working next year also.

    {-# LANGUAGE OverloadedStrings #-}
    {-# LANGUAGE QuasiQuotes #-}
    {-# LANGUAGE TemplateHaskell #-}
    {-# LANGUAGE TypeFamilies #-}

    import Yesod

    data App = App

    mkYesod "App" [parseRoutes|
    / HomeR GET
    |]

    instance Yesod App

    getHomeR :: Handler Html
    getHomeR = defaultLayout [whamlet|Look at me. Just one file.|]

    main :: IO ()
    main = warp 3000 App

Re: Manifest: A 1-file micro-back end

#22

Post by Joker_vD » Fri, Mar 21, 2025, 2:34 PM UTC

mananaysiempre wrote: post #13

Joker_vD wrote: post #10

Earlier quoted context omitted.

Um, "snarky"? How do I ask "is this last element optional, and does it have to be an emoji?" without snark? And it's the most egregious (in the "glaring" sense, not "outlandishly awful") things about the example, you don't often see emojis being a part config/programming languages outside of embedded strings, everything else is pretty self-explanatory dialect of YAML. The use of emojis looks quite similar to the way…

> SINGLE_EMOJI_COMMENT Bwahahaha. Sorry, I’ve just imagined the poor sod who has to implement this grammar and has to decide whether presentation selectors or (potentially unknown) ZWJ sequences or (potentially unknown) letter-pairs denoting flags count parts of as single emoji (in theory they do[1], but good luck figuring out what tables you need). > the way parameter/argument labels are introduced in Swift: in the…

Yeah, I also have stopped for a second to consider what "SINGLE" should mean here but then realized I was thinking about Unicode grapheme clusters, and emoji sequences, and I should probably not do that before the dinner (or ever, really).

Re: Manifest: A 1-file micro-back end

#23

Post by pjerem » Fri, Mar 21, 2025, 2:39 PM UTC

I tried to search for "migration" in the docs but found nothing ? What do you do if you want to modify your schema?

Re: Manifest: A 1-file micro-back end

#24

Post by brunaxLorax » Fri, Mar 21, 2025, 2:42 PM UTC

pjerem wrote: post #23

I tried to search for "migration" in the docs but found nothing ? What do you do if you want to modify your schema?

Hello ! Manifest dev here, they are on the way ! There is a DB sync at the moment that does the job but we are going to implement the migrations soon :)

Re: Manifest: A 1-file micro-back end

#25

Post by brunaxLorax » Fri, Mar 21, 2025, 2:42 PM UTC

ludicrousdispla wrote: post #15

For a 1-file micro-backend this sure does have a lot of files and dependencies.

correct :)

Re: Manifest: A 1-file micro-back end

#26

Post by brunaxLorax » Fri, Mar 21, 2025, 2:47 PM UTC

darccio wrote: post #6

The idea is interesting. I wonder what makes it AI-friendly. It isn't explained on the repository or the website, but I can imagine that the YAML-based DSL could be the reason.

Hello, Manifest dev here, most backend-as-a-services rely on an UI and it's harder for AIs. In comparison, Manifest high-level DSL is really understandable by gen AIs. It's also very easy to validate in comparison to bootstrap frameworks that come with a lot of files.

But you are right we should explain it somewhere !

Re: Manifest: A 1-file micro-back end

#27

Post by kevmo314 » Fri, Mar 21, 2025, 2:47 PM UTC

Seems like Prisma + PostgREST but more tightly coupled. Neat idea, certainly seems useful for some small-scale projects.

Re: Manifest: A 1-file micro-back end

#28

Post by pjerem » Fri, Mar 21, 2025, 2:51 PM UTC

brunaxLorax wrote: post #24

pjerem wrote: post #23

I tried to search for "migration" in the docs but found nothing ? What do you do if you want to modify your schema?

Hello ! Manifest dev here, they are on the way ! There is a DB sync at the moment that does the job but we are going to implement the migrations soon :)

Nice. Manifest looks really cool :)

Re: Manifest: A 1-file micro-back end

#29

Post by brunaxLorax » Fri, Mar 21, 2025, 2:52 PM UTC

shagrath wrote: post #12

mubou wrote: post #2

I'd love to see a frontend for this. Most CMSs are either tailored specifically for blogs or are complicated to set up. I've often wanted something like I guess Access or Filemaker Pro (if anyone remembers that) but with a modern UI and database. Not for production use, mind you, just like, say I have a library of books or blu-rays and want to create a catalogue of them (with images, so a spreadsheet is a no-go). Bei…

Looks like there is an admin panel demo, but can't find the login/password

Fixed ! thank you

Re: Manifest: A 1-file micro-back end

#30

Post by treve » Fri, Mar 21, 2025, 3:22 PM UTC

Looks like it doesn't use locking, so running two instances will corrupt your 'database': https://github.com/mnfst/manifest/blob/master/packages/core/...

It feels a bit mean to write this, but whenever someone reinvents a database this is the first thing I look to gain some confidence the authors understood what they were getting into.

Probably best to stick to sqlite instead!