A little confused about how to actually get started

[misleb]

The tutorial on the website leaves out a whole lot of steps and boilerplate to actually get a gofred app up and running.

First, if I just follow the quick start or tutorial I get errors in Cursor from the Go language server saying it can't build a Linux binary. Of course I can run GOOS=js GOARCH=wasm go build -o main.wasm and get a wasm file or edit my settings.json, but there's no HTML wrapper for it. Am I supposed to already have that? Do I just copy it from your website source?

Second, is there's no server side component to gofred? I would expect the wasm component in the browser to be linked to a server side process. Again, looking at your website source it seems server.go is all custom websockets. Am I supposed to write that all from scratch myself?

Or am I misunderstanding the scope of gofred? Maybe there needs to be an optional module for the server process.

[hasanhg]

Hey @misleb and welcome to the community. Sorry to hear that the quick start gives a confusion and this is because that we do not have a command-line tool yet. I started working on this one and when it is ready, today or tomorrow, you will be able to run just something likegofred create test_app and you will have a ready project on your current directory.

Regarding to your question, server/server.go is required for local development right now and it lets you to hot-reload whenever a change is made in the project. Using the server files in web project, when you run go run server/server.go it automatically builds the wasm file whenever needed and also refreshes the web page.

I will give an update here once the tool is ready, and pretty sure it will make the development start process much more easier.

Thanks for giving a heads up!

[hasanhg]

Hey @misleb, you can now refer to the Quick Start section, and check for the gofred-cli docmentation here.