Genie.jl

The highly productive Julia web framework

View the Project on GitHub GenieFramework/Genie.jl

Developing Genie Web Services

Starting up ad-hoc web servers at the REPL and writing small scripts to wrap micro-services works great, but production apps tend to become complex very quickly. They also have more stringent requirements, like managing dependencies, compressing assets, reloading code, logging, environments, or structuring the codebase in a way which promotes efficient workflows when working in teams.

Genie apps provide all these features, from dependency management and versioning (using Julia’s Pkg, since a Genie app is a Julia project), to a powerful asset pipeline (using industry vetted tools like Yarn and Webpack), automatic code reloading in development (provided by Revise.jl), and a clear resource-oriented MVC layout.

Genie enables a modular approach towards app building, allowing to add more components as the need arises. You can start with the web service template (which includes dependencies management, logging, environments, and routing), and grow it by sequentially adding DB persistence (through the SearchLight ORM), high performance HTML view templates with embedded Julia (via Flax), asset pipeline and compilation, and more.

Setting up a Genie Web Service project

Genie packs handy generator features and templates which help bootstrapping and setting up various parts of an application. For bootstrapping a new app we need to invoke one of the functions in the newapp family:

julia> using Genie

julia> Genie.newapp_webservice("MyGenieApp")

If you follow the log messages in the REPL you will see that the command will trigger a flurry of actions in order to set up the new project:


TIP

Check out the inline help for Genie.newapp, Genie.newapp_webservice, Genie.newapp_mvc, and Genie.newapp_fullstack too see what options are available for bootstrapping applications. We’ll go over the different configurations in upcoming sections.


The file structure

Our newly created web service has this file structure:

├── Manifest.toml
├── Project.toml
├── bin
├── bootstrap.jl
├── config
├── genie.jl
├── log
├── public
├── routes.jl
└── src

These are the roles of each of the files and folders:


HEADS UP

After creating a new app you might need to change the file permissions to allow editing/saving the files such as routes.jl.


Adding logic

You can now edit the routes.jl file to add some logic, at the bottom of the file:

route("/hello") do
  "Welcome to Genie!"
end

If you now visit http://127.0.0.1:8000/hello you’ll see a warm greeting.

Growing the app

Genie apps are just plain Julia projects. This means that routes.jl will behave like any other Julia script - you can reference extra packages, you can switch into pkg> mode to manage per project dependencies, include other files, etcetera.

If you have existing Julia code that you want to quickly load into a Genie app, you can add a lib/ folder in the root of the app and place your Julia files there. When available, lib/ and all its subfolders are automatically added to the LOAD_PATH by Genie, recursively.

If you need to add database support, you can always add the SearchLight ORM by using the dedicated generator, running julia> Genie.Generator.db_support() in the app’s REPL.

However, if your app grows in complexity and you develop it from scratch, it is more efficient to take advantage of Genie’s resource-oriented MVC structure.