iceberg alternatives and similar shards
Based on the "Web Frameworks" category.
Alternatively, view iceberg alternatives based on common mentions on social networks and blogs.
9.9 0.0 iceberg VS amethystAmethyst is a Rails inspired web-framework for Crystal language
9.9 5.5 iceberg VS amberA Crystal web framework that makes building applications fast, simple, and enjoyable. Get started with quick prototyping, less bugs, and blazing fast performance.
9.9 8.6 iceberg VS luckyA full-featured Crystal web framework that catches bugs for you, runs incredibly fast, and helps you write code that lasts.
9.1 3.5 iceberg VS spider-gazelleA Rails esque web framework with a focus on speed and extensibility for crystal lang
6.7 1.9 iceberg VS runcoboAn api framework with simple, intuitive and consistent DSL, using jbuilder to render json. https://runcobo.github.io/docs/
Do you think we are missing an alternative of iceberg or a related project?
Iceberg is a full-stack web framework in crystal-lang. It aims to serve as a MVC framework for developers to quickly create a functional website or software.
NOTE: It is in its very earlier stage and should not be used in production environment. However, feel free to try it out, request features, or report bugs.
At least Crystal 0.8.0 installed.
1. Create a Crystal project
$ crystal init app project_name
2. Add to
dependencies: iceberg: github: adlerhsieh/iceberg
It creates the necessary config files for you.
My First App
src/controllers/app_controller.cr. There should be an
# This is default. class AppController < Iceberg::Controller def index view :index end end
And the same in
# This is default. class AppIndexView < Iceberg::View def process end html :app, :index end
No need to change anything above for our first app.
Now, go to
src/routes.cr and route root to
Iceberg::Router.draw do # Add this get "/", :app end
And add the following to
./servercommand in root directory.
- Go to
- You will see
Route mapping is in
src/routes.cr file. Available syntax:
Iceberg::Router.draw do get "/", :app #=> route "/" to AppController#index get "/app", "app#index" #=> ditto get "/new_app", "app#new" #=> route "/new_app" to AppController#new action post "/new_app", "app#new" #=> ditto, but with POST request end
Controller receives http request and decides what to process. It is designed to handle only http requests so don't put any business logic here. Leave it to view classes.
The controller passes the action to
View and handles all operations there.
View returns a string of HTML that will respond to the browser.
The syntax is
view :action, where Iceberg looks for a view class name contains both
Controller name and Action name. For example:
class MyController < Iceberg::Controller def index # this action looks for MyIndexView in `views` directory view :index end end
You can either specify another view file.
class MyController < Iceberg::Controller def index # this action looks for MyAppView in `views` directory view :app end end
However, it is recommended to pair the names of a view and controller action together.
View is where your logic is. It uses
ECR library to embed Crystal into HTML text.
The most important part is that it brings instance variables into HTML, like
ERB in Ruby.
Check ECR library usage
in Crystal official repo.
One view class renders one file. This is a little different from Rails in which view is defined
in a controller action. The
process action is necessary since Iceberg takes it as the main function
in this class, like
func main in Golang.
It works like this:
class AppIndexView < Iceberg::View def process @name = "John" end html :app, :index end
And in your
Hello, <%= @name %>
You will see
Hello, John in browser.
In addition, it is recommended to organize your view folder structure like:
src |--views |--app |--index.cr |--html |--index.ecr
app is the name of a controller class, and
index is its action. The
html folder contains all
Everything is still in progress. It will be officially released once it's ready!
- Fork it ( https://github.com/adlerhsieh/iceberg/fork )
- Create your feature branch (git checkout -b my-new-feature)
- Commit your changes (git commit -am 'Add some feature')
- Push to the branch (git push origin my-new-feature)
- Create a new Pull Request