Sergei Poljanski
9bf40690e5
The admin was one shared HTTP Basic login: no way to give someone partial access, revoke one person, or tell who changed what. Add a users table and a session login form. Passwords are scrypt hashes from Ruby's OpenSSL, so no native gem is needed. Sessions carry a per-user version that is bumped on password change, which logs that user out everywhere. ADMIN_USER/ADMIN_PASSWORD now bootstrap the first superuser on an empty table and afterwards only work while no active superuser exists, as a recovery path that re-creates one. Until per-area permissions land, non-superusers only reach the dashboard and their own password page. Assisted-by: Claude:opus-5
15 lines
906 B
Text
15 lines
906 B
Text
<div class="header">
|
|
<h1>Admin</h1>
|
|
<p class="tagline">asxp.io</p>
|
|
</div>
|
|
|
|
<section class="section">
|
|
<% if @error %><div class="form-error-base"><div><%= @error %></div></div><% end %>
|
|
<form class="invoice-form auth-form" method="post" action="/admin/login">
|
|
<input type="hidden" name="authenticity_token" value="<%= csrf_token %>" />
|
|
<input type="hidden" name="next" value="<%= @next %>" />
|
|
<div class="field"><label for="username">Username</label><input type="text" id="username" name="username" value="<%= params[:username] %>" autocomplete="username" autocapitalize="none" required autofocus /></div>
|
|
<div class="field"><label for="password">Password</label><input type="password" id="password" name="password" autocomplete="current-password" required /></div>
|
|
<button type="submit" class="download-button">Log in</button>
|
|
</form>
|
|
</section>
|