After creating a new Saturn project, let's take a deeper look into what files are created.
At this level most of it is basic configuration files to help with running Saturn. From looking at the
paket.lock folders and files, you can see that by default Saturn uses paket to handle package management. You won't be working with these files directly but rather through the command line tools instead.
Saturn also uses FAKE to build the project. You can see how it is set up by looking at the
.fake folder and
Saturn also provides a
.gitignore file that prevents some folders from being tracked by git when they don't need to.
Lastly, there is the
SaturnSample.sln solution file so you can open the project in an IDE like Visual Sudio and a
global.json file to configure the solution file.
Most of the work you will do in this project however, will be in
src/SaturnSample, which looks like the following when expanded:
obj folders store the compiled version of the program after you build the project.
The convention for Saturn is that the model and everything associated with it are inside one folder. Everything is also named with the plural form of the model so "Books" instead of "Book".
Your static files like css, js, and images should be inside the
Config.fs contains a
Config record that stores settings that you can use inside your application. By default, the record only contains the
Database.fs contains functions to execute SQL queries within the program through Dapper.
If you did not run
dotnet saturn migration as in the how to start guide, you might not see
database.sqlite, but that is the database file that your Saturn project is using to store data.
paket.references shows the packages that your project is using.
Program.fs handles intializing the program and loading up various settings.
Router.fs is where you will set the route of the site and what page to load.
SaturnSample.fsproj is the project file itself.