![]() You can see that the Rust artifact “my_app” in the current directory is included and the commands don’t really do much other than print some information. The fields include and commands tell Deta what to do for deployment. You can see that the cargo run command is used for local development (declared in the dev field), but this is ignored for deployment. ![]() It starts by declaring the source directory is the current directory (“.”) and the engine is “custom”. It contains a single Micro called “my-app” that executes the Rust artifact “my_app” to run. I’ll start with the the Spacefile (the configuration for the Deta application) because it is rather simple.įor this use case, the Spacefile doesn’t do much other than declare the Micro and tell Deta to execute the Rust artifact when called to run.įollowing are more details on the configuration file below. So my solution was to compile the application on a GitHub Action (GHA) and push the artifact to Deta.īelow, I provide configuration files for GHA and a Deta application (a “Spacefile”) and some comments on their structure. So I tried to cross compile the app for Linux on my Mac, but ran into issues that I wasn’t able to solve (I’m still very new to the language and processes). ![]() The build process on Deta’s servers (running on AWS) would timeout before the app was compiled. I built a working app but ran into a problem when pushing to Deta. So a developer could build an app and then the user gets their own instance of the application Deta handles the separate sign-in and data storage.Ī Deta Micro (a service in the app like a web interface) can be built with any technology, so I wanted to experiment with building a web app with Rust. ![]() Their unique pitch is that each user has a personal cloud. Deta is a platform for building web apps. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |