A Rails 8.1 starter on Ruby 3.4 and PostgreSQL for developers who want the Rails 8 authentication generator finished off with the sign-up it leaves out. It covers sign-up, sign-in, sign-out and password reset, a projects example scoped to each user, Propshaft and importmap with no Node.js, a database health check and a Dockerfile that migrates on start and runs Puma.
by Light CloudFull-stack


The usual first edits are app/views/home/index.html.erb, the colour tokens in app/assets/stylesheets/application.css and the projects example, which shows the pattern for your own resources: keep every query on Current.user so people only reach their own records. Production forces https and sends HSTS, which suits Light Cloud's edge, but a plain docker run on your machine with no proxy in front needs FORCE_SSL=false or every request is redirected. Sign-in, sign-up and reset allow 10 attempts per 3 minutes per IP address, counted in each instance's own cache, and behind a proxy that address may be the proxy's rather than the visitor's, so treat it as a rough limit. Without SECRET_KEY_BASE a key is derived from DATABASE_URL, which is stable but only as secret as the database password. Reset links use APP_URL, which Light Cloud sets at each deploy; on other hosts set it yourself, or links use the host of the request. Emails go to the log until SMTP_ADDRESS is set, SMTP delivery has not been tested against a real provider, and the projects list has no pagination yet.
The generator makes sign in, sign out and password reset but no sign up. This starter adds a RegistrationsController with new and create that saves a User with has_secure_password, starts a session with the generator's start_new_session_for and is rate-limited like sign in.
Rails merges DATABASE_URL into the production entry of config/database.yml, and ?sslmode=require makes libpq use TLS without verifying the certificate. Parameters libpq does not know, such as uselibpqcompat and sslaccept in Light Cloud's URL, are dropped before connecting.
No. Propshaft serves the CSS and importmap loads Turbo and Stimulus as ES modules straight from the app, so the Docker image has only Ruby, its gems and libpq.
Production sets force_ssl, because it expects a proxy in front that ends TLS and sends X-Forwarded-Proto. Start the image with FORCE_SSL=false to serve plain http locally; leave it on behind Light Cloud or any other proxy.
Yes. It has no Light Cloud code: build the Dockerfile on any Docker host behind a proxy that ends TLS, with DATABASE_URL and SECRET_KEY_BASE set, or run assets:precompile, db:migrate and bin/rails server with RAILS_ENV=production.


Start a Django 5 app with email sign-in, password reset and the admin on PostgreSQL


Start a Laravel app with sign-up and password reset on PostgreSQL, without a starter kit
Start a Rails 8 CRUD API on PostgreSQL with validation, OpenAPI and Minitest set up